Migrating off Okta to Entra ID: the documented steps, in order
Reviewed 2026-11-10 · Editorial assessment by the editors
Microsoft documents an Okta to Entra ID migration in five parts: inventory your Okta apps, move SAML and OIDC apps, move Microsoft 365 federation with a staged rollout, move sync provisioning, and rebuild sign-on policies as Conditional Access. Pilot groups let you move users in waves. This guide orders those steps and links each to Microsoft's tutorial.
What do you need before you start?
- A Microsoft 365 tenant currently federated to Okta for SSO.
- A Microsoft Entra Connect server or Entra cloud provisioning agents.
- An admin with the Application Administrator, Cloud Application Administrator or Hybrid Identity Administrator role.
- Entra ID P1 if you will rebuild Okta sign-on policies as Conditional Access (included in Microsoft 365 E3 and Business Premium).
Source: Migrate Okta federation to Entra ID (read 2026-11-03), Entra Conditional Access overview (read 2026-11-03)
What are the steps?
01Inventory your Okta applications.
List every app in Okta with its protocol (SAML, OIDC, OAuth, password-based), its owner and its assignment groups. Microsoft's app migration tutorial starts here.
Source: Migrate applications from Okta to Entra ID (read 2026-11-03)
02Move SAML applications.
Recreate each SAML app in Entra ID and point it at Entra ID instead of Okta, following Microsoft's tutorial.
Source: Migrate applications from Okta to Entra ID (read 2026-11-03)
03Move OpenID Connect and OAuth 2.0 applications, then any custom authorization server.
Move each OIDC and OAuth 2.0 app, and any custom Okta authorization server, as Microsoft's tutorial describes.
Source: Migrate applications from Okta to Entra ID (read 2026-11-03)
04Prepare Microsoft 365 for cloud authentication.
Enable password hash synchronization or pass-through authentication, plus desktop single sign-on for domain-joined machines, on Entra Connect.
Source: Migrate Okta federation to Entra ID (read 2026-11-03)
05Pilot with staged rollout.
In the Entra admin center, enable staged rollout for managed user sign-in and add pilot groups. After about 30 minutes, pilot users sign in to Microsoft 365 without being redirected to Okta.
Source: Migrate Okta federation to Entra ID (read 2026-11-03)
06Convert the domain from federated to managed.
When pilots are clean, convert the Microsoft 365 domain with Microsoft Graph PowerShell (Update-MgDomain with AuthenticationType Managed).
Connect-MgGraph -Scopes "Domain.ReadWrite.All", "Directory.AccessAsUser.All" Update-MgDomain -DomainId contoso.com -AuthenticationType "Managed" Get-MgDomain -DomainId contoso.comFrom Microsoft's tutorial. contoso.com is Microsoft's example domain. Source: Migrate Okta federation to Entra ID (read 2026-11-03)
07Move sync provisioning.
Replace Okta's directory sync with Entra Connect-based synchronization, following Microsoft's sync provisioning tutorial.
Source: Migrate Okta sync provisioning · Reviewed 2026-11-10
08Rebuild sign-on policies as Conditional Access.
Map each Okta sign-on policy to a Conditional Access policy, following Microsoft's tutorial, and test before you retire the Okta policy.
Source: Migrate Okta sign-on policies to Conditional Access · Reviewed 2026-11-10
How long does it take?
Neither Microsoft nor Okta publishes a typical duration. The count of applications and sign-on policies in step 1 is the best predictor you have, and staged rollout lets you spread the user move over as many waves as you need.
What about moving from Entra ID to Okta?
The reverse usually adds Okta rather than removing Entra ID. Okta's Microsoft Office 365 integration federates the Microsoft 365 domain over WS-Federation or SAML and provisions users and groups; Okta's AD agent imports users and groups from Active Directory; apps then move to Okta one at a time. See the migration comparison.
Source: Okta Microsoft Office 365 integration (read 2026-11-03), Okta AD agent (help)
Frequently asked questions
Can I test the move with a few users first?
Yes. Staged rollout lets you add pilot groups whose users sign in to Microsoft 365 with cloud authentication instead of being redirected to Okta, before you convert the domain.
Do I need P1 to migrate from Okta?
P1 is needed to recreate Okta sign-on policies as Conditional Access policies. Microsoft 365 E3 and Business Premium include it.