AZ-305 ยท Governance and compliance design
Access reviews and entitlement management
Access reviews for groups, apps and roles, entitlement management access packages and catalogs, lifecycle workflows for joiner/mover/leaver.
Key points
- Access reviews: recertify groups, apps, Entra and Azure resource roles (created in PIM), packages; weekly to annual.
- Reviewers: users, group owners, managers, self.
- Access packages: groups, Teams, enterprise apps, SharePoint Online sites; policies: requester (also connected organizations), approval, expiry.
- Catalogs: unit of delegation.
- Lifecycle workflows: joiner, mover, leaver, e.g. employeeHireDate.
Source: https://learn.microsoft.com/en-us/entra/id-governance/entitlement-management-overview
Practice questions
In entitlement management, which container holds access packages and resources and is used to delegate management to non-administrators?
- Catalog
- Connected organization
- Initiative
- Management group
Show answer
Answer: A. Catalog
A catalog contains related resources and access packages, and catalog owners can create packages without being tenant administrators. A connected organization is an external directory, while initiatives and management groups belong to Azure governance, not entitlement management.
Which resources can you include in an entitlement management access package?
- Membership of a Microsoft Entra security group
- Assignment to an enterprise application
- Membership of a SharePoint Online site
- An Azure Policy initiative assignment
- A resource lock on a resource group
Show answer
Answer: A. Membership of a Microsoft Entra security group, B. Assignment to an enterprise application, C. Membership of a SharePoint Online site
Access packages can grant membership of Microsoft Entra security groups, assignment to enterprise applications and membership of SharePoint Online sites (as well as Microsoft 365 Groups and Teams). Azure Policy initiatives and resource locks are not access package resources.
Lifecycle workflows only handle onboarding new hires; leaver scenarios such as disabling accounts need a separate tool.
Show answer
Answer: False
False. Lifecycle workflows cover joiner, mover and leaver phases, and automating the disabling and removal of departing users' accounts is one of their core uses.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
