Content reviewed: 12 October 2026
Start with the control: require MFA, respond to risky sign-ins, activate privileged roles temporarily, or automate joining and leaving. These requirements have different licensing answers. Connect purchased product names to service plans, policy configuration and affected identities.
P1, P2 and Governance are different layers
| Requirement | Assess | Boundary |
|---|---|---|
| Ordinary Conditional Access | Entra ID P1 or suitable included entitlement | Risk policies add another requirement |
| User or sign-in risk policies | P2 / suitable ID Protection rights | General access control is insufficient |
| Privileged Identity Management | P2 or ID Governance | Count eligible users and other participants |
| Previously available basic reviews and access packages | Specific P2 capability | Newer Governance features are not automatically in P2 |
| Lifecycle Workflows and advanced governance | ID Governance or qualifying Entra Suite | Check prerequisites and actual scope |
The Entra licensing overview and Governance matrix support feature selection. P1 is included in Microsoft 365 E3 and Business Premium; P2 in Microsoft 365 E5. Check actual available and assigned service plans before adding standalone subscriptions.
Conditional Access is not Identity Protection
Conditional Access requires P1 for ordinary policies. Sign-in-risk and user-risk policies are Identity Protection features requiring P2. Compliant-device or app-protection controls can also depend on other products with separate licensing. One Entra licence does not automatically cover the entire protection design.
Requiring MFA alone does not necessarily mean buying P1. Microsoft also provides free Security defaults, which use a different model from granular Conditional Access policies. Choose according to actual condition and targeting requirements.
Verify changes in a pilot reflecting the planned deployment. Record the actual target population and policy dependencies. A visible portal option, or continued operation after licence expiry, does not prove lasting use rights.
Do not count PIM licences by recent activations
PIM is available with P2 or ID Governance. Current requirements cover eligible or time-bound assignees, equivalent PIM for Groups membership or ownership, activation approvers and review participants. Someone eligible to activate a role does not lose the coverage requirement simply because they did not activate this month.
A hypothetical design has ten eligible users, two approvers and two reviewers. One approver and one reviewer are already among the ten; the remaining approver and reviewer are two different additional people. Their union contains 12 people, not 14. Existing entitlements then determine how many new licences are missing.
Count actual participants rather than roles as separate billing units. One person with three responsibilities is not counted three times. An administrator who only configures PIM is not automatically an additional eligible role holder; assess actual activities against Microsoft’s examples.
Governance extends some P2 rights
P2 already includes PIM and some access-review and entitlement-management capabilities. Governance adds features such as Lifecycle Workflows, advanced reviews and managers requesting access on behalf of employees. Compare actual rows in the current matrix rather than the general statement “we need governance”.
Standalone Governance and P2 Step Up have different prerequisites. The guide requires a suitable active base subscription in the tenant; P2 Step Up needs a base containing the P2 plan. Entra Suite includes Governance plus other products. Governance alone does not prove rights to every other P2 feature, such as Identity Protection risk policies.
Reviews and requests need their own population count
| Scenario | Include | Underestimate |
|---|---|---|
| 100 employees can request an access package; 5 requested | The eligible request population for the scenario | Only 5 actual requests |
| Review of 50 members and 2 reviewers, one already a member | 51 different people with suitable coverage | Only the reviewers |
| Joining or leaving workflow | Affected members and relevant administrator under the rules | Only the workflow author |
| PIM assignments and approval | Union of licensed participant categories | Only successful activations |
These are hypothetical work examples, not a universal price list. Microsoft counts eligible populations for access packages, reviewed people and reviewers for reviews, and relevant users for lifecycle workflows. Also check whether you use an existing P2 capability or a newer Governance feature.
Guests use a different model
Guest Governance licensing uses an MAU model for qualifying governance actions. Count neither every sign-in nor every invited account. Current guidance separates Governance-exclusive actions from P2 actions; P2 actions are not charged under this model. Without an active governance action in the month, the rule does not automatically add another billed month.
The guide lists audit properties TargetId, TargetUserType and GovernanceLicenseFeatureUsed to evidence billing. Check the target guest, event type and Azure subscription linked for billed features. Employee licences or aggregate sign-in totals do not replace those records.
Assess service identities separately
The Workload ID FAQ distinguishes ordinary workload identities from eligible premium scenarios. Advanced controls for supported service principals can need Workload ID Premium. Reviewing service principals can also require suitable human-reviewer rights. Employee P2 counts do not prove licensing for all applications and automation.
The Workload ID FAQ also says licences do not need individual identity assignment and one licence can technically unlock tenant features. It does not cover an unlimited premium-identity population. Evidence entitlements through eligible identity inventories and actual feature use, rather than portal availability alone.
Keep separate inventories for employees, guests, privileged accounts, service principals and agent identities. Use current agent-specific guidance for new agent scenarios; a similar purpose to user PIM does not guarantee the same product or prerequisites.
Procurement and review workflow
- 01
Name the feature
Policy, review, access package, PIM or lifecycle workflow
- 02
Map affected identities
Targets, eligibility, approvers, reviewers and overlaps
- 03
Check included rights and prerequisites
Active products, actual service plans and correct add-on variant
- 04
Separate other models
Guest governance actions, workload identities and agent features
- 05
Reconcile deployment and records
Pilot, licence assignments and reassessment when policies expand
Frequently asked questions
Is P1 enough for risk-based Conditional Access?
No. Microsoft identifies sign-in-risk and user-risk policies as ID Protection features requiring P2.
Must I buy Governance for PIM?
No. PIM is also available with P2. Additional advanced scenarios can require Governance.
Does P2 include all Lifecycle Workflows?
No. The current matrix places them in Governance and qualifying Entra Suite. Check the actual scenario.
Do recent activation or request counts determine licences?
Not automatically. Requirements can follow eligibility, policy scope and participants rather than completed actions alone.








