Tutorial: Migrate Okta sign-on policies to Microsoft Entra Conditional Access

In this tutorial, learn to migrate an organization from global or application-level sign-on policies in Okta Conditional Access in Microsoft Entra ID. Conditional Access policies secure user access in Microsoft Entra ID and connected applications.

Learn more: What is Conditional Access?

This tutorial assumes you have:

  • Office 365 tenant federated to Okta for sign-in and multifactor authentication
  • Microsoft Entra Connect server, or Microsoft Entra Connect cloud provisioning agents configured for user provisioning to Microsoft Entra ID


See the following two sections for licensing and credentials prerequisites.


There are licensing requirements if you switch from Okta sign-on to Conditional Access. The process requires a Microsoft Entra ID P1 license to enable registration for Microsoft Entra multifactor authentication.

Learn more: Assign or remove licenses in the Microsoft Entra admin center

Enterprise Administrator credentials

To configure the service connection point (SCP) record, ensure you have Enterprise Administrator credentials in the on-premises forest.

Evaluate Okta sign-on policies for transition

Locate and evaluate Okta sign-on policies to determine what will be transitioned to Microsoft Entra ID.

  1. In Okta go to Security > Authentication > Sign On.

    Screenshot of Global MFA Sign On Policy entries on the Authentication page.

  2. Go to Applications.

  3. From the submenu, select Applications

  4. From the Active apps list, select the Microsoft Office 365 connected instance.

    Screenshot of settings under Sign On, for Microsoft Office 365.

  5. Select Sign On.

  6. Scroll to the bottom of the page.

The Microsoft Office 365 application sign-on policy has four rules:

  • Enforce MFA for mobile sessions - requires MFA from modern authentication or browser sessions on iOS or Android
  • Allow trusted Windows devices - prevents unnecessary verification or factor prompts for trusted Okta devices
  • Require MFA from untrusted Windows devices - requires MFA from modern authentication or browser sessions on untrusted Windows devices
  • Block legacy authentication - prevents legacy authentication clients from connecting to the service

The following screenshot is conditions and actions for the four rules, on the Sign On Policy screen.

Screenshot of conditions and actions for the four rules, on the Sign On Policy screen.

Configure Conditional Access policies

Configure Conditional Access policies to match Okta conditions. However, in some scenarios, you might need more setup:

  • Okta network locations to named locations in Microsoft Entra ID
  • Okta device trust to device-based Conditional Access (two options to evaluate user devices):
    • See the following section, Microsoft Entra hybrid join configuration to synchronize Windows devices, such as Windows 10, Windows Server 2016 and 2019, to Microsoft Entra ID
    • See the following section, Configure device compliance
    • See, Use Microsoft Entra hybrid join, a feature in Microsoft Entra Connect server that synchronizes Windows devices, such as Windows 10, Windows Server 2016, and Windows Server 2019, to Microsoft Entra ID
    • See, Enroll the device in Microsoft Intune and assign a compliance policy

Microsoft Entra hybrid join configuration

To enable Microsoft Entra hybrid join on your Microsoft Entra Connect server, run the configuration wizard. After configuration, enroll devices.


Microsoft Entra hybrid join isn't supported with the Microsoft Entra Connect cloud provisioning agents.

  1. Configure Microsoft Entra hybrid join.

  2. On the SCP configuration page, select the Authentication Service dropdown.

    Screenshot of the Authentication Service dropdown on the Microsoft Entra Connect dialog.

  3. Select an Okta federation provider URL.

  4. Select Add.

  5. Enter your on-premises Enterprise Administrator credentials

  6. Select Next.


    If you blocked legacy authentication on Windows clients in the global or app-level sign-on policy, make a rule that enables the Microsoft Entra hybrid join process to finish. Allow the legacy authentication stack for Windows clients.
    To enable custom client strings on app policies, contact the Okta Help Center.

Configure device compliance

Microsoft Entra hybrid join is a replacement for Okta device trust on Windows. Conditional Access policies recognize compliance for devices enrolled in Microsoft Intune.

Device compliance policy

Windows 10/11, iOS, iPadOS, and Android enrollment

If you deployed Microsoft Entra hybrid join, you can deploy another group policy to complete auto-enrollment of these devices in Intune.

Configure Microsoft Entra multifactor authentication tenant settings


Steps in this article may vary slightly based on the portal you start from.

Before you convert to Conditional Access, confirm the base MFA tenant settings for your organization.

  1. Sign in to the Microsoft Entra admin center as a Global Administrator.

  2. Browse to Identity > Users > All users.

  3. Select Per-user MFA on the top menu of the Users pane.

  4. The legacy Microsoft Entra multifactor authentication portal appears. Or select Microsoft Entra multifactor authentication portal.

    Screenshot of the multifactor authentication screen.

  5. Confirm there are no users enabled for legacy MFA: On the Multifactor authentication menu, on Multifactor authentication status, select Enabled and Enforced. If the tenant has users in the following views, disable them in the legacy menu.

    Screenshot of the multifactor authentication screen with the search feature highlighted.

  6. Ensure the Enforced field is empty.

  7. Select the Service settings option.

  8. Change the App passwords selection to Do not allow users to create app passwords to sign in to non-browser apps.

    Screenshot of the multifactor authentication screen with service settings highlighted.

  9. Clear the checkboxes for Skip multifactor authentication for requests from federated users on my intranet and Allow users to remember multifactor authentication on devices they trust (between one to 365 days).

  10. Select Save.

    Screenshot of cleared checkboxes on the Require Trusted Devices for Access screen.

Build a Conditional Access policy

To configure Conditional Access policies, see Best practices for deploying and designing Conditional Access.

After you configure the prerequisites and established base settings, you can build Conditional Access policy. Policy can be targeted to an application, a test group of users, or both.

Before you get started:

  1. Sign in to the Microsoft Entra admin center.

  2. Browse to Identity.

  3. To to learn how to create a policy in Microsoft Entra ID. See, Common Conditional Access policy: Require MFA for all users.

  4. Create a device trust-based Conditional Access rule.

    Screenshot of entries for Require Trusted Devices for Access, under Conditional Access.

    Screenshot of the Keep you account secure dialog with the success message.

  5. After you configure the location-based policy and device trust policy, Block legacy authentication with Microsoft Entra ID with Conditional Access.

With these three Conditional Access policies, the original Okta sign-on policies experience is replicated in Microsoft Entra ID.

Enroll pilot members in MFA

Users register for MFA methods.

For individual registration, users go to Microsoft Sign-in pane.

To manage registration, users go to Microsoft My Sign-Ins | Security Info.

Learn more: Enable combined security information registration in Microsoft Entra ID.


If users registered, they're redirected to the My Security page, after they satisfy MFA.

Enable Conditional Access policies

  1. To test, change the created policies to Enabled test user login.

    Screenshot of policies on the Conditional Access, Policies screen.

  2. On the Office 365 Sign-In pane, the test user John Smith is prompted to sign in with Okta MFA and Microsoft Entra multifactor authentication.

    Screenshot of the Azure Sign-In pane.

  3. Complete the MFA verification through Okta.

    Screenshot of MFA verification through Okta.

  4. The user is prompted for Conditional Access.

  5. Ensure the policies are configured to be triggered for MFA.

    Screenshot of MFA verification through Okta prompted for Conditional Access.

Add organization members to Conditional Access policies

After you conduct testing on pilot members, add the remaining organization members to Conditional Access policies, after registration.

To avoid double-prompting between Microsoft Entra multifactor authentication and Okta MFA, opt out from Okta MFA: modify sign-on policies.

  1. Go to the Okta admin console

  2. Select Security > Authentication

  3. Go to Sign-on Policy.


    Set global policies to Inactive if all applications from Okta are protected by application sign-on policies.

  4. Set the Enforce MFA policy to Inactive. You can assign the policy to a new group that doesn't include the Microsoft Entra users.

    Screenshot of Global MFA Sign On Policy as Inactive.

  5. On the application-level sign-on policy pane, select the Disable Rule option.

  6. Select Inactive. You can assign the policy to a new group that doesn't include the Microsoft Entra users.

  7. Ensure there's at least one application-level sign-on policy enabled for the application that allows access without MFA.

    Screenshot of application access without MFA.

  8. Users are prompted for Conditional Access the next time they sign in.

Next steps