Skip to content
Okta vs Entra

Reviewed 10 November 2026

Device assurance

Reviewed 2026-11-10

Okta's device-security checks use configured assurance attributes in app sign-in policy rules. The policy must be incorporated into a rule before it applies. Define the expected result for enrolled, unmanaged and unknown devices rather than assuming device information is always complete.

How it works

Okta's device-security checks use configured assurance attributes in app sign-in policy rules. The policy must be incorporated into a rule before it applies. Define the expected result for enrolled, unmanaged and unknown devices rather than assuming device information is always complete.

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

Okta's device-security checks use configured assurance attributes in app sign-in policy rules.

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 device assurance 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.