Skip to content

Commit 8452b13

Browse files
Merge pull request #214530 from Justinha/util1
Update how-to-mfa-server-migration-utility.md
2 parents 4e6d606 + e8172e8 commit 8452b13

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

articles/active-directory/authentication/how-to-mfa-server-migration-utility.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 09/14/2022
9+
ms.date: 10/10/2022
1010

1111
ms.author: justinha
1212
author: justinha
1313
manager: martinco
14-
ms.reviewer: michmcla
14+
ms.reviewer: jpettere
1515

1616
ms.collection: M365-identity-device-management
1717
---
@@ -27,8 +27,7 @@ Admins can use the MFA Server Migration Utility to target single users or groups
2727

2828
## Limitations and requirements
2929

30-
- The MFA Server Migration Utility is currently in public preview. Some features might not be supported or have limited capabilities. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
31-
- The MFA Server Migration Utility requires a new preview build of the MFA Server solution to be installed on your Primary MFA Server. The build makes updates to the MFA Server data file, and includes the new MFA Server Migration Utility. You don’t have to update the WebSDK or User portal. Installing the update _doesn't_ start the migration automatically.
30+
- The MFA Server Migration Utility requires a new build of the MFA Server solution to be installed on your Primary MFA Server. The build makes updates to the MFA Server data file, and includes the new MFA Server Migration Utility. You don’t have to update the WebSDK or User portal. Installing the update _doesn't_ start the migration automatically.
3231
- The MFA Server Migration Utility copies the data from the database file onto the user objects in Azure AD. During migration, users can be targeted for Azure AD MFA for testing purposes using [Staged Rollout](../hybrid/how-to-connect-staged-rollout.md). Staged migration lets you test without making any changes to your domain federation settings. Once migrations are complete, you must finalize your migration by making changes to your domain federation settings.
3332
- AD FS running Windows Server 2016 or higher is required to provide MFA authentication on any AD FS relying parties, not including Azure AD and Office 365.
3433
- Review your AD FS claims rules and make sure none requires MFA to be performed on-premises as part of the authentication process.
@@ -130,7 +129,7 @@ Open MFA Server, click **User Portal**:
130129
|- OATH token|See [OATH token documentation](howto-mfa-mfasettings.md#oath-tokens)|
131130
|Allow users to select language|Language settings will be automatically applied to a user based on the locale settings in their browser|
132131
|Allow users to activate mobile app|See [MFA Service settings](howto-mfa-mfasettings.md#mfa-service-settings)|
133-
|- Device limit|Azure AD limits users to 5 cumulative devices (mobile app instances + hardware OATH token + software OATH token) per user|
132+
|- Device limit|Azure AD limits users to five cumulative devices (mobile app instances + hardware OATH token + software OATH token) per user|
134133
|Use security questions for fallback|Azure AD allows users to choose a fallback method at authentication time should the chosen authentication method fail|
135134
|- Questions to answer|Security Questions in Azure AD can only be used for SSPR. See more details for [Azure AD Custom Security Questions](concept-authentication-security-questions.md#custom-security-questions)|
136135
|Allow users to associate third-party OATH token|See [OATH token documentation](howto-mfa-mfasettings.md#oath-tokens)|
@@ -249,7 +248,7 @@ Once you've successfully migrated user data, you can validate the end-user exper
249248

250249
1. Navigate to the following url: [Enable staged rollout features - Microsoft Azure](https://portal.azure.com/?mfaUIEnabled=true%2F#view/Microsoft_AAD_IAM/StagedRolloutEnablementBladeV2).
251250

252-
1. Change **Azure multifactor authentication (preview)** to **On**, and then click **Manage groups**.
251+
1. Change **Azure multifactor authentication** to **On**, and then click **Manage groups**.
253252

254253
:::image type="content" border="true" source="./media/how-to-mfa-server-migration-utility/staged-rollout.png" alt-text="Screenshot of Staged Rollout.":::
255254

0 commit comments

Comments
 (0)