Skip to content

Commit 64bc4d5

Browse files
authored
Update migrate-okta-sign-on-policies-to-azure-active-directory-conditional-access.md
1 parent 8423b18 commit 64bc4d5

File tree

1 file changed

+12
-12
lines changed

1 file changed

+12
-12
lines changed

articles/active-directory/manage-apps/migrate-okta-sign-on-policies-to-azure-active-directory-conditional-access.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Learn more: [What is Conditional Access?](/azure/active-directory/conditional-ac
2020

2121
This tutorial assumes you have:
2222

23-
* Office 365 tenant federated to Okta for sign-in and multi-factor authentication.
23+
* Office 365 tenant federated to Okta for sign-in and multi-factor authentication
2424
* Azure AD Connect server, or Azure AD Connect cloud provisioning agents configured for user provisioning to Azure AD
2525

2626
## Prerequisites
@@ -56,18 +56,19 @@ Locate and evaluate Okta sign-on policies to determine what will be transitioned
5656

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

59-
- **Enforce MFA for Mobile Sessions** - Requires MFA from modern authentication or browser sessions on iOS or Android
60-
- **Allow Trusted Windows Devices** - Prevents unnecessary verification or factor prompts for trusted Okta devices
61-
- **Require MFA from Untrusted Windows Devices** - Requires MFA from modern authentication or browser sessions on untrusted Windows devices
62-
- **Block Legacy Authentication** - Prevents legacy authentication clients from connecting to the service
59+
- **Enforce MFA for mobile sessions** - requires MFA from modern authentication or browser sessions on iOS or Android
60+
- **Allow trusted Windows devices** - prevents unnecessary verification or factor prompts for trusted Okta devices
61+
- **Require MFA from untrusted Windows devices** - requires MFA from modern authentication or browser sessions on untrusted Windows devices
62+
- **Block legacy authentication** - prevents legacy authentication clients from connecting to the service
63+
64+
The following screenshot is conditions and actions for the four rules, on the Sign On Policy screen.
6365

6466
![Screenshot of conditions and actions for the four rules, on the Sign On Policy screen.](media/migrate-okta-sign-on-policies-to-azure-active-directory-conditional-access/sign-on-rules.png)
6567

6668
## Configure Conditional Access policies
6769

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

70-
7172
* Okta network locations to named locations in Azure AD
7273
* [Using the location condition in a Conditional Access policy](../conditional-access/location-condition.md)
7374
* Okta device trust to device-based Conditional Access (two options to evaluate user devices):
@@ -80,8 +81,8 @@ Configure Conditional Access policies to match Okta conditions. However, in some
8081

8182
To enable hybrid Azure AD join on your Azure AD Connect server, run the configuration wizard. After configuration, enroll devices.
8283

83-
>[!NOTE]
84-
>Hybrid Azure AD join isn't supported with the Azure AD Connect cloud provisioning agents.
84+
>[!NOTE]
85+
>Hybrid Azure AD join isn't supported with the Azure AD Connect cloud provisioning agents.
8586
8687
1. [Configure hybrid Azure AD join](../devices/howto-hybrid-azure-ad-join.md).
8788
2. On the **SCP configuration** page, select the **Authentication Service** dropdown.
@@ -94,8 +95,7 @@ To enable hybrid Azure AD join on your Azure AD Connect server, run the configur
9495
7. Select **Next**.
9596

9697
> [!TIP]
97-
> If you blocked legacy authentication on Windows clients in the global or app-level sign-on policy, make a rule that enables the hybrid Azure AD join process to finish.
98-
> Allow the legacy authentication stack for Windows clients. </br>To enable custom client strings on app policies, contact the [Okta Help Center](https://support.okta.com/help/).
98+
> If you blocked legacy authentication on Windows clients in the global or app-level sign-on policy, make a rule that enables the hybrid Azure AD join process to finish. Allow the legacy authentication stack for Windows clients. </br>To enable custom client strings on app policies, contact the [Okta Help Center](https://support.okta.com/help/).
9999
100100
### Configure device compliance
101101

@@ -179,8 +179,8 @@ To manage registration, users go to [Microsoft My Sign-Ins | Security Info](http
179179

180180
Learn more: [Enable combined security information registration in Azure Active Directory](../authentication/howto-registration-mfa-sspr-combined.md).
181181

182-
>[!NOTE]
183-
>If users registered, they're redirected to the **My Security** page, after they satisfy MFA.
182+
>[!NOTE]
183+
>If users registered, they're redirected to the **My Security** page, after they satisfy MFA.
184184
185185
## Enable Conditional Access policies
186186

0 commit comments

Comments
 (0)