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/authentication/howto-registration-mfa-sspr-combined.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: authentication
8
8
ms.topic: how-to
9
-
ms.date: 04/15/2020
9
+
ms.date: 04/17/2020
10
10
11
11
ms.author: iainfou
12
12
author: iainfoulds
@@ -44,34 +44,34 @@ If you have configured the Site to Zone Assignment List in Internet Explorer, th
44
44
45
45
## Conditional Access policies for combined registration
46
46
47
-
Securing when and how users register for Azure Multi-Factor Authentication and self-service password reset is now possible with user actions in Conditional Access policy. This feature is available to organizations who have enabled the [combined registration feature](../authentication/concept-registration-mfa-sspr-combined.md). This functionality may be enabled in organizations where they want users to register for Azure Multi-Factor Authentication and SSPR from a central location such as a trusted network location during HR onboarding. For more information about creating trusted locations in Conditional Access, see the article [What is the location condition in Azure Active Directory Conditional Access?](../conditional-access/location-condition.md#named-locations)
47
+
Securing when and how users register for Azure Multi-Factor Authentication and self-service password reset is now possible with user actions in Conditional Access policy. This feature is available to organizations who have enabled the [combined registration feature](../authentication/concept-registration-mfa-sspr-combined.md). This functionality may be enabled in organizations where they want users to register for Azure Multi-Factor Authentication and SSPR from a central location such as a trusted network location during HR onboarding.
48
48
49
-
### Create a policy to require registration from a trusted location
49
+
For more information about creating trusted locations in Conditional Access, see the article [What is the location condition in Azure Active Directory Conditional Access?](../conditional-access/location-condition.md#named-locations)
50
50
51
-
The following policy applies to all selected users, who attempt to register using the combined registration experience, and blocks access unless they are connecting from a location marked as trusted network.
51
+
### Create a policy to require registration from a trusted location
52
52
53
-

53
+
The following policy applies to all selected users that attempt to register using the combinedregistration experience, and blocks access unless they are connecting from a location marked as trusted network.
54
54
55
55
1. In the **Azure portal**, browse to **Azure Active Directory** > **Security** > **Conditional Access**
56
-
1. Select **New policy**
57
-
1.In Name, Enter a Name for this policy. For example, **Combined Security Info Registration on Trusted Networks**
58
-
1. Under **Assignments**, click**Users and groups**, and select the users and groups you want this policy to apply to
56
+
1. Select **+ New policy**
57
+
1. Enter a name for this policy, such as *Combined Security Info Registration on Trusted Networks*.
58
+
1. Under **Assignments**, select**Users and groups**. Choose the users and groups you want this policy to apply to, then select **Done**.
59
59
60
60
> [!WARNING]
61
-
> Users must be enabled for [combined registration](../authentication/howto-registration-mfa-sspr-combined.md).
61
+
> Users must be enabled for combined registration.
62
+
63
+
1. Under **Cloud apps or actions**, select **User actions**. Check **Register security information**, then select **Done**.
64
+
65
+

62
66
63
-
1. Under **Cloud apps or actions**, select **User actions**, check **Register security information (preview)**
64
-
1. Under **Conditions** > **Locations**
67
+
1. Under **Conditions** > **Locations**, configure the following options:
65
68
1. Configure **Yes**
66
69
1. Include **Any location**
67
70
1. Exclude **All trusted locations**
68
-
1. Click **Done** on the Locations blade
69
-
1. Click **Done** on the Conditions blade
70
-
1. Under **Access controls** > **Grant**
71
-
1. Click **Block access**
72
-
1. Then click **Select**
71
+
1. Select **Done** on the *Locations* window, then select **Done** on the *Conditions* window.
72
+
1. Under **Access controls** > **Grant**, choose **Block access**, then **Select**
0 commit comments