Content reviewed: 12 October 2026

One administrator licence does not cover everyone targeted by Conditional Access. Start with the internal users and the feature they will use. Basic policies require Entra ID P1; user-risk or sign-in-risk policies require the relevant P2 entitlement. MFA can also be provided through security defaults without custom Conditional Access policies.

Licensing checks by requirement
RequirementEntitlement and related check
MFA, location and ordinary access conditionsEntra ID P1 for targeted internal users
User or sign-in riskEntra ID P2 / ID Protection for that population
Compliant managed deviceEntra and appropriate Intune licensing
Service principal accessSeparate Workload ID Premium and supported identity type
External partnerCheck the External ID model; do not automatically use employee counting

The Conditional Access overview confirms P1 for ordinary functionality and P2 for risk-based policies. Related Intune, Purview and other features have their own requirements. The Entra licensing guide lists P1 in Microsoft 365 E3 and Business Premium, and P2 in Microsoft 365 E5. Check the complete product, not an “E3” abbreviation in a procurement sheet.

Our example: 60 people, ten Premium licences

A hypothetical company has 60 internal users: ten with Business Premium and 50 with Business Standard. It wants custom Conditional Access MFA for all 60. Ten already have P1 in their bundle; the remaining 50 need another appropriate entitlement. If they have none, the gap is 50. The company does not automatically need 60 new P1 licences or just a licence for the policy author.

The Entra Product Terms list P1/P2 as User SLs; the universal online-service terms govern user-licence assignment. Document the relevant entitlement for each targeted internal account. Saving a policy or observing technical enforcement does not prove the entire group was licensed.

If risk-based policies are needed only for eight administrators, assess P2 for those eight accounts and P1 for other users targeted by ordinary policies. Check existing entitlements first. P2 for administrators does not cover equivalent risk-based policies for the other 52 users. Assess each additional administrative account as a separate targeted account, not an invisible exception.

Do not count every policy as another licence

A user can be targeted by MFA, location and managed-device policies simultaneously. At the same required licence level, count the targeted user rather than three copies of their name. Conversely, exclusion from one policy does not exclude them from every policy. Maintain an account-level view across targeting and update it when roles change.

Distinguish an actual exclusion, a non-enforced test policy and feature entitlement. Report-only does not turn a paid feature into a free one; check licensing while preparing the test. Emergency accounts need their own protection, monitoring and restricted use rather than becoming unchecked everyday accounts.

Security key attached to work laptop

Overlapping policies: why MFA was insufficient

Under the evaluation rules, a sign-in must satisfy every applicable policy. If one requires MFA and another a compliant device, successful MFA does not replace the device requirement. A block policy can stop access even after the MFA policy succeeds.

Within one policy, selected grant controls can require all controls or one of them. That differs from several policies applying together. Record both levels: which policies applied, and whether a particular policy combines its grant controls with AND or OR.

Report-only has specific limits

The report-only guide explains evaluation without enforcement and the exception for the User Actions scope. Review results in the sign-in detail. This mode does not provide the new policy’s protection and cannot test every policy type universally.

Interpreting report-only results
ResultWhat it tells you
SuccessRequirements would be met; another policy can still block the sign-in
FailureThe applicable policy would block access or fail a non-interactive requirement
User action requiredAn action would be needed; a new MFA challenge, for example, is not performed without enforcement
Not appliedApplicability conditions were not met; this is not successful protection

A compliant-device policy in report-only can still prompt for a certificate on macOS, iOS and Android. Account for this documented side effect when planning the pilot. “User action required” also does not demonstrate that the user will successfully complete a new authentication challenge.

Moving from security defaults

Security defaults are available without a premium licence but do not provide custom targeting and exclusions. They must be disabled when replaced by Conditional Access. Prepare the new policies and an immediate protection handover; do not plan a gap with the old mechanism disabled and its replacement still only in report-only.

The handover checklist should cover existing MFA, legacy-authentication blocking and required work scenarios. Check devices or applications depending on device code flow: current security defaults block that flow. Judge the change through actual applications rather than the mere presence of a policy in the portal.

Pilot deployment and blocked sign-ins

  1. 01

    Document targeting

    Record internal users, resource, conditions, exclusions and licence entitlement for each policy.

  2. 02

    Select work scenarios

    Test laptops, phones, web access and required business clients. One pilot administrator does not represent every role.

  3. 03

    Evaluate report-only

    Compare all applicable policies with the expected outcome. Prepare users for interactive authentication.

  4. 04

    Enforce for the pilot

    Verify the real sign-in and work task, not just a successful configuration status.

  5. 05

    Expand and monitor

    Keep a rollback procedure, emergency-access monitoring and exclusion reviews.

For an incident, collect the time, account, application, device and specific sign-in event. Identify the failed policy and requirement. New group membership can change targeting when a new token is issued; a valid older token does not prove the new policy will never apply. Create an exception only for a confirmed cause and with a review date.

Applications are not human accounts

Conditional Access for workload identities has separate Workload ID Premium licensing. A policy assigned to a group containing a service principal is not enforced for that principal; target it directly. This model does not cover managed identities or arbitrary Microsoft and third-party multitenant applications. A service principal cannot complete user MFA either.

What happens when licences expire

The current overview says policies are not automatically deleted or disabled when required licences expire. They can still be viewed and deleted, but not modified. Continued technical protection is not a permanent free entitlement; plan a properly licensed and operational target state when changing subscriptions.

Frequently asked questions

Is one P1 licence enough for the tenant?

No. Document appropriate entitlements for internal users targeted by paid functionality. Portal access is not an organisation-wide licence.

Does everyone need Business Premium?

No. P1 can be included in another suite or acquired separately. Choose the product for the full work role.

Does all MFA require P1?

No. Security defaults provide baseline protection without a premium licence. Custom Conditional Access and risk-based policies have different requirements.

Is report-only invisible to users?

It does not enforce the new policy, but compliance checks can trigger certificate prompts on some platforms. Check supported scope and the actual scenario.

Why did sign-in fail after successful MFA?

Another applicable policy may have failed, such as a compliant-device requirement. Review the complete sign-in event.