You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/manage-apps/migrate-okta-sign-on-policies-to-azure-active-directory-conditional-access.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Learn more: [What is Conditional Access?](/azure/active-directory/conditional-ac
20
20
21
21
This tutorial assumes you have:
22
22
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
24
24
* Azure AD Connect server, or Azure AD Connect cloud provisioning agents configured for user provisioning to Azure AD
25
25
26
26
## Prerequisites
@@ -56,18 +56,19 @@ Locate and evaluate Okta sign-on policies to determine what will be transitioned
56
56
57
57
The Microsoft Office 365 application sign-on policy has four rules:
58
58
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.
63
65
64
66

65
67
66
68
## Configure Conditional Access policies
67
69
68
70
Configure Conditional Access policies to match Okta conditions. However, in some scenarios, you might need more setup:
69
71
70
-
71
72
* Okta network locations to named locations in Azure AD
72
73
*[Using the location condition in a Conditional Access policy](../conditional-access/location-condition.md)
73
74
* 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
80
81
81
82
To enable hybrid Azure AD join on your Azure AD Connect server, run the configuration wizard. After configuration, enroll devices.
82
83
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.
85
86
86
87
1.[Configure hybrid Azure AD join](../devices/howto-hybrid-azure-ad-join.md).
87
88
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
94
95
7. Select **Next**.
95
96
96
97
> [!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/).
99
99
100
100
### Configure device compliance
101
101
@@ -179,8 +179,8 @@ To manage registration, users go to [Microsoft My Sign-Ins | Security Info](http
179
179
180
180
Learn more: [Enable combined security information registration in Azure Active Directory](../authentication/howto-registration-mfa-sspr-combined.md).
181
181
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.
0 commit comments