Skip to content
Okta vs Entra

Reviewed 10 November 2026

Conditional Access

Reviewed 2026-11-10

Microsoft Entra ID's policy engine: if-then rules that combine signals about the user or agent, location, device, application and risk, then block access or require steps such as MFA. It needs Entra ID P1. Keep identity, access policy and resource permission separate. Check the source before choosing a control for your applications.

How it works

Microsoft Entra ID's policy engine: if-then rules that combine signals about the user or agent, location, device, application and risk, then block access or require steps such as MFA. It needs Entra ID P1.

Identify the actor, the resource and the decision this term describes. Record which system makes that decision and which system enforces it.

A sign-in event, a policy decision and an application permission are not interchangeable. Test the relevant boundary rather than relying on a product label.

What Okta and Entra ID call it

Microsoft Entra ID's policy engine: if-then rules that combine signals about the user or agent, location, device, application and risk, then block access or require steps such as MFA. It needs Entra ID P1.

Use the linked comparison to locate the relevant product scope. Do not infer a vendor capability from a similar name alone.

Example

Consider an application access review as an illustrative exercise, not a customer story. Identify the person or service involved, the resource requested and the evidence needed.

Locate where conditional access affects that decision. Ask what would change if the identity, device or permission changed.

Write down the expected result before testing. Keep the observation separate from a vendor's description of the feature.