Skip to content
Okta vs Entra

Reviewed 10 November 2026

Federated and managed domains: how Microsoft 365 sign-in moves between providers

Reviewed 2026-11-10 · Editorial assessment by the editors

By the editors · 2 min read

A Microsoft 365 domain is either federated, sending users to an outside identity provider such as Okta, or managed, signing them in with Entra ID. Moving sign-in between providers means changing that setting. Microsoft documents doing it in stages: pilot groups first with staged rollout, then the whole domain.

What is the difference between federated and managed?

Every Microsoft 365 tenant has one or more verified domains, such as example.com. For a managed domain, Entra ID authenticates users itself, with a password, passkey or other method it controls. For a federated domain, Entra ID redirects users to another identity provider and accepts the signed token that comes back. When Okta fronts Microsoft 365, the domain is federated to Okta, over WS-Federation or SAML.

Which direction are you moving?

Into a federated setup, you configure the outside provider and federate the domain to it; Okta's Microsoft Office 365 integration covers that direction. Out of one, you prepare Entra ID to authenticate users itself and then convert the domain back to managed. Microsoft publishes a step-by-step tutorial for the second direction when the current provider is Okta.

What are the documented steps off Okta?

  1. Confirm the prerequisites: Microsoft 365 federated to Okta, and Entra Connect or cloud provisioning agents syncing users.
  2. Choose how Entra ID will check passwords: password hash synchronization or pass-through authentication.
  3. Turn on staged rollout and add pilot groups, whose members now sign in with cloud authentication instead of being redirected to Okta.
  4. Widen the pilot group by group.
  5. Convert the domain from federated to managed with the Update-MgDomain command.

Sign-on policies and app connections move separately, and Microsoft publishes tutorials for each. The migrating off Okta guide lists them in order.

How do you keep a way back?

Because staged rollout works by group membership, taking a user out of the pilot group is the natural rollback before the domain is converted. After conversion, going back means federating the domain again. That is why the documented order puts the domain change last.

Can you stop halfway?

Yes, for as long as you need. Okta can keep federating Microsoft 365 while apps move one at a time, and staged rollout lets part of the organisation use cloud authentication in the meantime. The migration comparison calls this row a tie: neither vendor forces a single cutover.

Back to the glossary