Skip to content

That's just a taste — their profile full of gems!

Visit profile
User avatar
Gabriel Chavez
November 18127

Entra ID Governance and the JML Problem

I spend a lot of time with companies that think they have onboarding and offboarding under control.

Then I look closer.

What they usually have is a mix of HR emails, IT tickets, spreadsheets, tribal knowledge, and a manager who vaguely remembers what happened the last time someone joined or left six months ago. It works right up until it doesn’t.

And when it fails, it fails in the places that matter:

  • accounts enabled too early or too late
  • access granted inconsistently
  • old group memberships hanging around after role changes
  • SaaS access never removed after termination
  • no reliable proof that the process actually happened

That’s why identity lifecycle automation matters more than most organizations think.

What stood out to me is that the real problem isn’t “creating a user.” The real problem is the full joiner / mover / leaver cycle.

A new hire needs the right access at the right time.
A role change needs access adjusted without carrying old privileges forward.
A departing employee needs more than a disabled AD account — they need to be removed from groups, Teams, apps, and anything else the business forgot it connected over the last few years.

That last part is where I see real risk every week.

A lot of offboarding processes still assume disabling the main identity is enough. In practice, users are often still present in downstream SaaS platforms, old distribution groups, collaboration spaces, external tools, and line-of-business systems. That’s not just messy administration. It’s unnecessary exposure.

What I like about Entra ID Governance is that it gives organizations a structured way to automate the repetitive identity work they keep handling manually.

Not just “create account, send password.”

I’m talking about practical workflow steps like:

  • triggering actions based on hire date or leave date
  • scoping workflows by department or user attributes
  • enabling accounts when they should become active
  • adding users to the right groups or Teams
  • assigning access packages
  • removing access during offboarding
  • extending workflows into non-Microsoft systems through custom tasks and Logic Apps

That last piece matters. Most environments I walk into are hybrid by default, even if they don’t call themselves that. Identity starts in HR or Entra, but access sprawls across multiple SaaS platforms. If your automation stops at Microsoft 365, you’ve only solved part of the problem.

From a security standpoint, the biggest win is consistency.

Manual processes create drift. Drift creates exceptions. Exceptions become standing access, orphaned accounts, and audit findings. If I can reduce the number of humans who need to remember every step in every handoff, I reduce the chance of a preventable miss.

There’s also an operational truth here that security teams understand and finance teams often overlook: manual identity processes are expensive. Not just in licensing terms, but in payroll hours, ticket queues, follow-ups, escalations, and rework.

If HR, IT, managers, and security all have to coordinate by email every time someone joins, moves, or leaves, that cost adds up fast.

That said, I wouldn’t oversell this as “turn it on and you’re done.”

The hard part is not the feature. The hard part is the process design.

Before anyone automates onboarding/offboarding, I usually tell them to answer a few plain questions:

What should happen on day -7, day 1, day 3, and day 30?
Which access is role-based, and which is manager-approved?
What systems fall outside M365 but still need lifecycle actions?
What gets disabled, what gets removed, and what gets retained for legal/compliance reasons?
Who owns each exception path?

If you don’t answer those first, automation just makes a bad process run faster.

The other point worth calling out is licensing. A lot of teams get excited about governance features and then discover they’re not included where they assumed they were. That’s not a reason to dismiss it, but it is a reason to build the business case properly. In many environments, the people-cost of manual JML work is already higher than the technology cost to streamline it.

My practical takeaway:

Identity lifecycle management is one of the highest-value low-drama improvements most organizations can make.

It improves security.
It improves user experience.
It improves auditability.
And it reduces the dependence on memory, heroics, and checklists no one really trusts.

If your onboarding and offboarding process still depends on someone chasing a spreadsheet and sending reminder emails, you don’t have a process. You have a vulnerability with good intentions.

#cybersecurity#infosec#compliance#iam#zerotrust#identitygovernance#itoperations#entraid#saassecurity
Like
Dislike

8

1

Add a comment...