The direct answer
Identity governance is the part of Microsoft 365 governance that decides who gets access to which resources, keeps that access current as people join, change roles and leave, and produces the evidence an auditor asks for. In a Microsoft 365 tenant it runs on Microsoft Entra ID Governance, which Microsoft describes as making sure the right people have the right access to the right resources through process automation, delegation to business groups and visibility.
The three areas and their features
| Area | What it governs | Microsoft Entra features | License (per Microsoft Learn) |
|---|---|---|---|
| Identity lifecycle | Accounts created when people join, changed when they move, removed when they leave | HR-driven provisioning, lifecycle workflows | HR provisioning: P1 and above; lifecycle workflows: Entra ID Governance |
| Access lifecycle | Which groups, Teams, apps and SharePoint sites each person can use, and for how long | Entitlement management (access packages), access reviews | Core capabilities: P2; advanced capabilities: Entra ID Governance |
| Privileged access | Administrator roles, granted just in time and reviewed | Privileged Identity Management (PIM) | Entra ID P2 or Entra ID Governance |
How EPC Group sets it up
- Map current licenses to the features needed, so nothing is bought twice or missing.
- Automate joiners, movers and leavers from the HR system, starting with removal of access when people leave.
- Put guests and privileged roles under recurring access reviews.
- Move access requests into access packages with approvals and expiry.
- Hand over reporting for auditors: who has access, who approved it, and when it was last reviewed.
Identity governance is one pillar of a wider Microsoft 365 governance program; see the Microsoft 365 governance framework and Microsoft Entra ID services.
Primary sources
- Microsoft Entra ID Governance — Microsoft Learn, accessed 2026-10-27
- Microsoft Entra ID Governance licensing fundamentals — Microsoft Learn, accessed 2026-10-27
Frequently Asked Questions
Is Microsoft Entra ID P2 enough for identity governance?
EPC Group checks the feature list before buying. Microsoft Entra ID P2 includes Privileged Identity Management and the access reviews and entitlement management capabilities that were previously in P2, but lifecycle workflows require Microsoft Entra ID Governance, and Microsoft states no new identity governance features will be added to the P2 SKU (Microsoft Learn, accessed 2026-10-27).
Which Microsoft 365 plans include Entra ID P1 or P2?
EPC Group maps licenses first: Microsoft documents that Entra ID P1 is included with Microsoft 365 E3, E5 or E7 and Microsoft 365 Business Premium, and Entra ID P2 with Microsoft 365 E5 or E7. Microsoft Entra ID Governance is an add-on that requires P1 or P2 in the tenant (Microsoft Learn, accessed 2026-10-27).
Do guests count for Entra ID Governance licensing?
EPC Group plans guest governance separately. Microsoft licenses governance for guest users on a monthly active user basis, which requires an Azure subscription to be selected for guest billing, unlike the per-user licensing for employees (Microsoft Learn, accessed 2026-10-27).
Where should an organization start with identity governance?
EPC Group usually starts with the joiner-mover-leaver process, because access that is never removed is the most common audit finding: automate account creation and removal from the HR system, then add access reviews for guests and privileged roles, then move access requests into access packages.
Talk to a senior architect
A one-hour scoping call with a senior EPC Group architect covers your licenses, your joiner-mover-leaver process and which access needs review first. Email contact@epcgroup.net or call 888-381-9725.
Documented and anonymized engagements
Named engagements come first; anonymized summaries follow under the anonymized-engagement rule — the client is not named and every statement is EPC-reported. Documents behind named engagements are in the Evidence Center.
- Superior Court of California, County of Amador — Exchange 2019 on-premises to Exchange Online (2026)Superior Court of California, County of Amador · 2026 · Delivered — payment-corroborated (client payment records published)
- Superior Court of California, County of Amador — Exchange 2013 to Exchange 2019 migration, AD Connect resolution, domain-controller migration (2024)Superior Court of California, County of Amador · 2024 · Contracted
- Office of the Texas State Chemist (Texas A&M AgriLife Research) — Exchange Server 2013 to Exchange Server 2019 migration (2021)Office of the Texas State Chemist (Texas A&M AgriLife Research) · 2021 · Contracted — countersigned
- Tarleton State University: Office 365 cross-tenant migration engagement (2021)Tarleton State University (Texas A&M University System) · 2021 · Contracted — countersigned
- GCC High Tenant Consolidation: Defense Technology (2026)Anonymized engagement summary · Defense technology company · 2026
- Exchange 2019 Hybrid Migration: Community Bank (2025)Anonymized engagement summary · Community bank · 2025
- Exchange 2010 to 2019 Migration: Municipal Government (2023)Anonymized engagement summary · Municipal government · 2023
- Exchange Online Migration: Transportation Agency (2023)Anonymized engagement summary · Traffic management center of a state transportation agency · 2023
More engagements: Prairie View A&M University (Texas A&M University System) — Gmail to Exchange Online migration services (2020) · Georgia Institute of Technology (Georgia Tech Professional Education) — Microsoft Teams and SharePoint consulting services (2019) · Haskell (The Haskell Company) — Office 365 Phase 0 implementation-strategy initiative (2017) · Google Workspace and Microsoft 365 into One Tenant (2023) · Office 365 Tenant Consolidation: Four into One (2023) · Cross-Tenant Migration After an Acquisition: Life Sciences
