Entra licensing
Observed content change
1 edited passage (4 words changed), 7 removed passages (about 570 words). The changed wording mentions prerequisites, permissions, settings and controls, licensing. Review the source to confirm the effect.
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant; check your licensing.
… licensing requirements for Microsoft Entra ID Governance features for member users. Microsoft Entra Suite includes all features of Microsoft Entra ID Governance. Microsoft 365 E7 also includes all ID Governance features through the Entra Suite and Agent 365. Licensing information[removed: and example license scenarios]for Entitlement management, Access reviews, and Lifecycle Workflows are provided following the table.
[removed: Here are some example license scenarios to help you determine the number of licenses you must have.]
[removed: Scenario Calculation Number of licenses An Identity Governance Administrator at Woodgrove Bank creates initial catalogs. One of the policies specifies that All employees (2,000 employees) can request a specific set of access packages. 150 employees request the access packages. 2,000 employees who can request the access packages 2,000 An Identity Governance Administrator at Woodgrove Bank creates initial catalogs. They create an auto-assignment policy that grants All members of the Sales department (350 employees) access to a specific set of access packages. 350 employees are auto-assigned to the access packages. 350 employees need licenses. 351]
[removed: Scenario Calculation Number of licenses An administrator creates an access review of Group A with 75 member users and 1 group owner, and assigns the group owner as the reviewer. 1 license for the group owner as reviewer, and 75 licenses for the 75 users. 76 An administrator creates an access review of Group B with 500 member users and 3 group owners, and assigns the 3 group owners as reviewers. 500 licenses for users, and 3 licenses for each group owner as reviewers. 503 An administrator creates an access review of Group B with 500 member users. Makes it a self-review. 500 licenses for each user as self-reviewers 500 An administrator creates an access review of Group C with 50 member users. Makes it a self-review. 50 licenses for each user as self-reviewers. 50 An administrator creates an access review of Group D with 6 member users. Makes it a self-review. 6 licenses for each user as self-reviewers. No additional licenses are required. 6]
[removed: Scenario Calculation Number of licenses A Lifecycle Workflows Administrator creates a workflow to add new hires in the Marketing department to the Marketing teams group. 250 new hire member users are assigned to the Marketing teams group via this workflow once. Other 150 new hire member users are assigned to the Marketing teams group via this workflow later the same year. 1 license for the Lifecycle Workflows Administrator, and 400 licenses for the users. 401 A Lifecycle Workflows Administrator creates a workflow to pre-offboard a group of employees before their last day of employment. The scope of users who will be pre-offboarded are 40 users once. We offboard 40 licensed users. Now, we can re-assign these 40 licenses and assign 10 more licenses later in the year to pre-offboard 50 more users. 50 licenses for users, and 1 license for the Lifecycle Workflows Administrator. 51]
[removed: Scenario Calculation Number of licenses Woodgrove Bank has 10 administrators for different departments and 2 Privileged Role Administrators that configure and manage PIM. They make five administrators eligible. Five licenses for the administrators who are eligible 5 Graphic Design Institute has 25 administrators of which 14 are managed through PIM. Role activation requires approval and there are three different users in the organization who can approve activations. 14 licenses for the eligible roles + three approvers 17 Contoso has 50 administrators of which 42 are managed through PIM. Role activation requires approval and there are five different users in the organization who can approve activations. Contoso also does monthly reviews of users assigned to administrator roles and reviewers are the users' managers of which six aren't in administrator roles managed by PIM. 42 licenses for the eligible roles + five approvers + six reviewers 53]
Microsoft's wording from Microsoft source, © Microsoft Corporation, under MIT. ChangeIntel marks removed and added words, drops formatting and shortens long unchanged stretches.
Read the current Microsoft source · Link to this observation · Compare any two versions
Sections to inspect
Up to 12 section headings from retained before/after evidence. The current source may have changed again.
Why this was flagged
The changed words, with a few words around them, matched these rule categories: prerequisites, permissions, settings and controls, licensing. These matches identify subjects to assess; they do not establish a policy change or applicability.
Observation details · observed 18 Oct 23:50 UTC
- Observed by ChangeIntel
- 18 Oct 23:50 UTC
- Source update metadata
- 28 Jul 07:37 UTC
- First observed on this installation
- 8 Oct 23:13 UTC
- Last successful check
- 18 Oct 23:50 UTC
- Next check due
- today 23:50 UTC
Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment.
Watch this page to review its changes in My radar.
Timeline
From the capture of 18 Oct 23:50 UTC- 18 undated sections
- 35 with conditions
Requirements, exceptions and scope
Microsoft Entra Suite: The suite combines Microsoft Entra products to secure access for your employees. It allows administrators to provide secure access from anywhere to…
Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.
Observed history and review priority
Captured 18 Oct 23:50 UTC; extracted 18 Oct 23:51 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c.
Review priority. Extracted assertions require review · Applicability or exceptions require review
0 date changes and 0 condition changes across 1 compared revisions. Suggested check interval: 24 hours.
Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.
Retained observations · 3
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 18 Oct 23:50 UTC · 53 candidates
- 12 Oct 23:53 UTC · 53 candidates
- 8 Oct 23:13 UTC · 45 candidates
Microsoft's edits
History on GitHubCommits to the page's source in MicrosoftDocs/entra-docs, with Microsoft's own messages. Commit dates can be hours or days before Learn publishes the change. ChangeIntel keeps a copy of each diff, so an edit stays readable here if GitHub stops serving it. Read 18 Oct 23:34 UTC.
Related public evidence
No related evidence found in this installation's recent collection. This does not establish that no announcement exists.
Retained observations
- 18 Oct 23:50 UTC · shown above
- 12 Oct 23:53 UTC
8 removed passages (about 50 words). The changed wording mentions prerequisites. Review the source to confirm the effect.
- 8 Oct 23:13 UTC
Baseline for retained history; no earlier retained text to compare.
What changed
First observed 18 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.