Skip to content

Commit 311a20e

Browse files
Merge pull request #230671 from tilarso/patch-44
Update howto-registration-mfa-sspr-combined-troubleshoot.md
2 parents ead321d + 3ef56ab commit 311a20e

File tree

1 file changed

+0
-17
lines changed

1 file changed

+0
-17
lines changed

articles/active-directory/authentication/howto-registration-mfa-sspr-combined-troubleshoot.md

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -51,13 +51,6 @@ The following table lists all audit events generated by combined registration:
5151
| --- | --- |
5252
| I don't have the option to add a particular method. | 1. Determine whether the method is enabled for Multi-Factor Authentication or for SSPR. <br> 2. If the method is enabled, save the policies again and wait 1-2 hours before testing again. <br> 3. If the method is enabled, ensure that the user hasn't already set up the maximum number of that method that they're allowed to set up.|
5353

54-
## Disable combined registration
55-
56-
When a user registers a phone number and/or mobile app in the combined registration experience, our service stamps a set of flags (StrongAuthenticationMethods) for those methods on that user. This functionality allows the user to perform Multi-Factor Authentication with those methods whenever Multi-Factor Authentication is required.
57-
58-
If an admin enables combined registration, users register through the combined registration experience, and then the admin disables combined registration, users might unknowingly be registered for Multi-Factor Authentication also.
59-
60-
If a user who has completed combined registration goes to the legacy self-service password reset (SSPR) registration page at [https://aka.ms/ssprsetup](https://aka.ms/ssprsetup), the user will be prompted to perform Multi-Factor Authentication before they can access that page. This step is expected from a technical standpoint, but it's new for users who were previously registered for SSPR only. Though this extra step does improve the user's security posture by providing another level of security, admins might want to roll back their users so that they're no longer able to perform Multi-Factor Authentication.
6154

6255
### How to roll back users
6356

@@ -142,16 +135,6 @@ In a PowerShell window, run the following command, providing the script and user
142135

143136
`<script location> -path <user file location>`
144137

145-
### Disable the updated experience
146-
147-
To disable the updated experience for your users, complete these steps:
148-
149-
1. Sign in to the Azure portal as a user administrator.
150-
2. Go to **Azure Active Directory** > **User settings** > **Manage user feature settings**.
151-
3. Under **Users can use the combined security information registration experience**, set the selector to **None**, and then select **Save**.
152-
153-
Users will no longer be prompted to register by using the updated experience.
154-
155138
## Next steps
156139

157140
* [Learn more about combined registration for self-service password reset and Azure AD Multi-Factor Authentication](concept-registration-mfa-sspr-combined.md)

0 commit comments

Comments
 (0)