Study guide

4.4 Identity Governance, Entitlement Management, and Lifecycle Governance

Azure SC-900 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map

1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map

2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC

2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation

3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication

3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities

4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection

4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk

5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault

5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets

6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score

6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans

7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks

7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks

8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence

8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence

9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score

9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager

10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit

10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management

11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps

11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop

12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path

12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900

4.4 Identity Governance, Entitlement Management, and Lifecycle Governance

Key Takeaways Explain This Topic AI

Microsoft Entra ID Governance answers four questions: which users have access, what they can do with it, whether the access is appropriate, and whether controls are effective.

Entitlement management uses access packages that bundle resources (groups, apps, SharePoint sites) into requestable items with approval and expiration policies.

Lifecycle workflows automate the joiner, mover, and leaver stages so access is provisioned on day one and revoked at offboarding.

Entra ID Governance is a paid add-on (P1/P2 plus the Governance SKU) and complements, rather than replaces, Conditional Access.

Governance is about keeping access appropriate over time, not just granting it once.

Last updated: June 2026

Governance: the right access over time

Microsoft Entra ID Governance is the identity governance and administration (IGA) layer of Entra. Microsoft frames it around four questions an organization should always be able to answer:

Which users have access to which resources?

What are those users doing with that access?

Is there effective organizational control over that access?

Can auditors verify the controls are working?

Initial access assignment is only the beginning. People change roles, projects end, partners come and go, and privileged access drifts. Governance is the discipline of making sure access stays appropriate across the entire identity lifecycle , not just at the first grant.

Governance is a paid add-on : the Entra ID Governance SKU sits on top of P1 or P2. Its four pillars are entitlement management , access reviews , lifecycle workflows , and Privileged Identity Management . (Access reviews and PIM get their own treatment in Section 4.5.)

Entitlement management and access packages

Entitlement management lets organizations manage access at scale by automating access requests, assignments, reviews, and expiration. Its central object is the access package — a bundle of resources (security/Microsoft 365 groups, enterprise applications, and SharePoint Online sites) packaged together so a user can request the whole set with one request instead of an admin hand-adding them to groups.

An access package is governed by policies that define:

  • Policy element Purpose
  • Who can request Internal users, specific groups, or external/guest users
  • Approval workflow Single or multi-stage approvals; or auto-approve
  • Lifecycle/expiration When access expires and whether it can be extended
  • Access review Periodic recertification of the assignment

This is especially powerful for external collaboration : a partner can request an access package through a portal, get approved, receive a bundle of resources, and have that access automatically expire — all without IT manually managing the guest. Catalogs group related packages and resources for delegated administration.

Lifecycle workflows: joiner, mover, leaver

Lifecycle workflows automate the tasks tied to the three identity-lifecycle events:

Joiner — a new employee automatically receives the right groups, licenses, and a welcome experience on day one (often triggered before their start date).

Mover — a role or department change triggers access recertification and adjusts entitlements.

Leaver — termination automatically removes access, disables the account, and revokes tokens at offboarding.

Workflows run on a schedule and can be triggered by attribute changes (for example, the employee's hire date or employeeLeaveDateTime ). They execute built-in tasks such as generating a temporary access pass, adding/removing group memberships, sending notifications, and disabling accounts. The exam point is that lifecycle workflows make provisioning and deprovisioning automatic and consistent — closing the common gap where ex-employees keep access for weeks.

Joiner = automated onboarding/provisioning.

Mover = recertify and adjust on role change.

Leaver = automated offboarding/deprovisioning.

Governance versus point-in-time access control

Conditional Access decides access in the moment of a sign-in. Governance asks whether the access should still exist over time and automates that lifecycle. That distinction is the heart of SC-900's governance questions.

Wording in the scenario Capability

"Users request a bundle of resources for a project, with approval and auto-expiry" Entitlement management / access packages

  • "Provision access on hire and remove it on termination automatically" Lifecycle workflows
  • "Periodically confirm users still need their access" Access reviews
  • "Limit standing admin rights with just-in-time activation" Privileged Identity Management
  • "Require MFA from untrusted networks" Conditional Access (not governance)

If the scenario is less about one sign-in and more about access hygiene over time — onboarding, offboarding, recertification, expiration — you are in Entra ID Governance.

Why governance exists and how the pieces fit together

Cloud access grows quickly and silently. Without governance, users accumulate permissions long after they need them — a problem called privilege creep or access sprawl . A salesperson who moves to marketing keeps the old CRM access; a contractor whose project ended still belongs to ten Teams; a guest invited for one document never leaves. Each lingering grant widens the attack surface and breaks least privilege. Microsoft Entra ID Governance exists to keep access aligned with current need automatically, at a scale humans cannot manage by hand.

The four pillars work as a system. Entitlement management controls how access is requested and granted through self-service access packages with approvals, so the right people get the right bundle without an admin manually managing groups. Lifecycle workflows keep access aligned with employment events — joiner, mover, leaver — so provisioning and deprovisioning are automatic and timely. Access reviews periodically recertify that existing access is still warranted and remove what is not. Privileged Identity Management governs the highest-risk privileged roles with just-in-time activation.

Together they cover the full arc: request, provision, recertify, and elevate.

For answer selection, listen for the verbs and nouns. Request a bundle / access package / approval / expiry points to entitlement management. On hire / on termination / automate onboarding / role change points to lifecycle workflows. Periodically confirm / recertify / still needed points to access reviews. Elevate / activate / standing admin points to PIM. And crucially, governance is licensed separately — the Entra ID Governance add-on on top of P1/P2 — which the exam may use to distinguish it from base Conditional Access.

Privilege creep is the core problem governance solves.

Entitlement management = how access is requested/granted.

Lifecycle workflows = access tied to employment events.

Access reviews = recurring recertification.

PIM = privileged-role governance.