Modernize identity governance with Microsoft Entra ID Governance

Pillar name: Protect identities and secrets

Practice name: Modernize Entitlement Governance with Cloud-Native Controls

Many organizations still rely on legacy identity governance systems that were built for earlier operating models. These systems are now difficult to manage, customize, and scale. As identity becomes a primary security boundary, these systems can introduce unnecessary complexity, increase operational overhead, and make it harder to enforce consistent access controls. Microsoft addressed this challenge by shifting entitlement governance to Microsoft Entra ID Governance. By using cloud-native lifecycle controls, you can simplify access management, strengthen visibility, and reduce dependence on legacy infrastructure.

Context and problem

Many organizations have an inconsistent approach to identity governance or rely on legacy identity governance systems. Legacy identity governance platforms, particularly on-premises or heavily customized third-party solutions, introduce significant operational, security, and cost challenges at scale. These systems often rely on bespoke workflows, hybrid dependencies, and manual interventions that slow response times, complicate audits, and increase the risk of misconfiguration.

At Microsoft scale, our previous third-party identity governance solution managed tens of thousands of entitlement objects across hundreds of thousands of users. While functionally comprehensive, the platform required customization and integration effort to meet Microsoft security and compliance requirements. It added complexity across hybrid environments and incurred high recurring costs. These characteristics conflicted with Secure Future Initiative (SFI) goals to reduce the attack surface, simplify identity infrastructure, and move toward cloud-native, policy-driven controls.

Organizations that rely on legacy identity governance systems encounter the same core problem: identity governance systems that are expensive to operate, difficult to evolve, and misaligned with modern Zero Trust and cloud-first security models.

Solution

To address these challenges, Microsoft migrated identity governance workloads to Microsoft Entra ID Governance, complemented by a secondary in‑house hybrid identity solution for workloads that couldn't immediately transition to cloud‑only management.

The solution focused on:

  • Cloud‑first entitlement governance using Microsoft Entra Entitlement Management (EM) and Entra ID Security Groups.

  • Explicit classification of entitlements into cloud-only versus on‑premises‑dependent categories.

  • Lifecycle‑driven access management, replacing static entitlement assignments with access packages, approvals, and time‑bound policies.

  • Intentional non‑lift‑and‑shift migration, recreating access structures in the cloud to avoid propagating legacy misconfigurations.

  • Accelerated deprecation timelines to reduce exposure and eliminate dependency on legacy platforms.

By aligning identity governance with Microsoft Entra ID’s native lifecycle, approval, and auditing capabilities, Microsoft reduced operational friction, improved access visibility, and strengthened compliance posture while eliminating a costly and complex third‑party dependency.

Guidance

Organizations can adopt this pattern by using the following actionable practices:

Use case Recommended action Resources
Entitlement discovery and classification Inventory all entitlements, groups, roles, and workflows before migration.

Classify each object as cloud-only, hybrid, or on-premises-only based on actual usage patterns rather than design assumptions.

Use historical access and provisioning data to identify hidden dependencies.

Scope migration realistically to avoid failures caused by undocumented relationships.
Microsoft Entra ID Governance documentation

Entitlement management documentation

Access reviews documentation
Cloud-first governance design Design governance around identity governance primitives rather than recreating legacy workflow logic.

Model access using access packages as the primary entitlement construct.

Centralize approvals, expirations, and just-in-time access through policy-driven controls.

Use security groups strictly as enforcement mechanisms rather than governance logic.
Microsoft Entra entitlement management overview

Microsoft Entra ID documentation

Configure access package policies
Intentional re-creation, not direct migration Avoid directly migrating legacy group structures into the cloud.

Create new cloud-native security groups with consistent naming conventions.

Require entitlement owners to re-establish permissions intentionally.

Reconstruct membership programmatically only after governance structures are validated.
Owner engagement at scale Treat entitlement owners as active migration participants.

Communicate expectations, timelines, and decision points early.

Require owners to validate access structures and approve migration choices.

Allow alternative solutions only where justified and time-bound.
Identity governance lifecycle workflows documentation
Phased cloud adoption with clear exit criteria Use hybrid identity solutions only as temporary off-ramps for workloads that can't yet move to cloud-only governance.

Define explicit exit criteria.

Track exceptions and review them regularly.

Align teams around the benefits of cloud-native governance.
Hybrid identity documentation

Identity modernization planning guidance
Governance validation and continuous assurance Validate governance outcomes, not just technical migration completion.

Monitor provisioning, deprovisioning, and access review activity.

Test joiner, mover, and leaver workflows against business expectations.

Use audit evidence and review results as continuous assurance mechanisms.
Access reviews in Microsoft Entra ID

Audit logs in Microsoft Entra ID

Outcomes

Benefits

  • Reduced exposure to cyberattack by eliminating legacy governance infrastructure.

  • Improved visibility into who has access to what, where, and why.

  • Faster entitlement changes through automated workflows.

  • Lower operational and licensing costs.

  • Stronger alignment with Zero Trust and cloud‑native security principles.

Trade‑offs

  • Significant upfront effort for entitlement discovery and cleanup.

  • Temporary user friction during access re‑assignment.

  • Hybrid exceptions require governance discipline to avoid long‑term sprawl.

Key success factors

  • Executive sponsorship to enforce deprecation timelines.

  • Clear entitlement ownership and accountability.

  • Automation for migration, validation, and reporting.

  • Early customer education on cloud governance benefits.

  • Defined service limits and success criteria aligned to Microsoft Entra ID Governance capabilities.

Summary

Migrating from legacy identity governance solutions to Microsoft Entra ID Governance enables organizations to simplify entitlement management, reduce operational complexity, and strengthen security. Organizations should adopt a cloud-first, lifecycle-driven model centered on access packages, policy-based controls, and continuous validation. By adopting this model, organizations eliminate legacy dependencies, improve visibility into access, and better align with Zero Trust principles.