Skip to content
Okta vs Entra

Reviewed 10 November 2026

Federated and managed domains

Reviewed 2026-11-10

In Microsoft 365, a federated domain sends users to an outside identity provider, such as Okta, to sign in; a managed domain signs them in with Entra ID itself. Moving off Okta ends with converting the domain from federated to managed.

How it works

In Microsoft 365, a federated domain sends users to an outside identity provider, such as Okta, to sign in; a managed domain signs them in with Entra ID itself. Moving off Okta ends with converting the domain from federated to managed.

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

In Microsoft 365, a federated domain sends users to an outside identity provider, such as Okta, to sign in; a managed domain signs them in with Entra ID itself. Moving off Okta ends with converting the domain from federated to managed.

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 federated and managed domains 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.