Skip to content

Commit c3177e9

Browse files
authored
Merge pull request #106346 from iainfoulds/patch-2
[AzureAD-MFA] Remove sentence on reactivating MFA Server
2 parents f539689 + 2b5359e commit c3177e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/authentication/concept-mfa-authprovider.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ You cannot change the usage model (per enabled user or per authentication) after
3838

3939
If you purchased enough licenses to cover all users that are enabled for MFA, you can delete the MFA provider altogether.
4040

41-
If your MFA provider is not linked to an Azure AD tenant, or you link the new MFA provider to a different Azure AD tenant, user settings and configuration options are not transferred. Also, existing Azure MFA Servers need to be reactivated using activation credentials generated through the MFA Provider. Reactivating the MFA Servers to link them to the MFA Provider doesn't impact phone call and text message authentication, but mobile app notifications stop working for all users until they reactivate the mobile app.
41+
If your MFA provider is not linked to an Azure AD tenant, or you link the new MFA provider to a different Azure AD tenant, user settings and configuration options are not transferred. Also, existing Azure MFA Servers need to be reactivated using activation credentials generated through the MFA Provider.
4242

4343
### Removing an authentication provider
4444

0 commit comments

Comments
 (0)