Skip to content

Commit a909257

Browse files
authored
Merge pull request #232183 from Justinha/mfa-server
Mfa server
2 parents 1478ea9 + 36226ed commit a909257

File tree

3 files changed

+11
-7
lines changed

3 files changed

+11
-7
lines changed

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 01/29/2023
9+
ms.date: 03/27/2023
1010

1111
ms.author: justinha
1212
author: justinha
@@ -192,15 +192,15 @@ Migrating user data doesn't remove or alter any data in the Multi-Factor Authent
192192

193193
The MFA Server Migration utility targets a single Azure AD group for all migration activities. You can add users directly to this group, or add other groups. You can also add them in stages during the migration.
194194

195-
To begin the migration process, enter the name or GUID of the Azure AD group you want to migrate. Once complete, press Tab or click outside the window and the utility will begin searching for the appropriate group. The window will populate all users in the group. A large group can take several minutes to finish.
195+
To begin the migration process, enter the name or GUID of the Azure AD group you want to migrate. Once complete, press Tab or click outside the window to begin searching for the appropriate group. All users in the group are populated. A large group can take several minutes to finish.
196196

197197
To view attribute data for a user, highlight the user, and select **View**:
198198

199199
:::image type="content" border="true" source="./media/how-to-mfa-server-migration-utility/view-user.png" alt-text="Screenshot of how to view use settings.":::
200200

201-
This window displays the attributes for the selected user in both Azure AD and the on-premises MFA Server. You can use this window to view how data was written to a user after they’ve been migrated.
201+
This window displays the attributes for the selected user in both Azure AD and the on-premises MFA Server. You can use this window to view how data was written to a user after migration.
202202

203-
The settings option allows you to change the settings for the migration process:
203+
The **Settings** option allows you to change the settings for the migration process:
204204

205205
:::image type="content" border="true" source="./media/how-to-mfa-server-migration-utility/settings.png" alt-text="Screenshot of settings.":::
206206

@@ -209,17 +209,21 @@ The settings option allows you to change the settings for the migration process:
209209
- The migration utility tries direct matching to UPN before using the on-premises Active Directory attribute.
210210
- If no match is found, it calls a Windows API to find the Azure AD UPN and get the SID, which it uses to search the MFA Server user list.
211211
- If the Windows API doesn’t find the user or the SID isn’t found in the MFA Server, then it will use the configured Active Directory attribute to find the user in the on-premises Active Directory, and then use the SID to search the MFA Server user list.
212-
- Automatic synchronization – Starts a background service that will continually monitor any authentication method changes to users in the on-premises MFA Server, and write them to Azure AD at the specified time interval defined
212+
- Automatic synchronization – Starts a background service that will continually monitor any authentication method changes to users in the on-premises MFA Server, and write them to Azure AD at the specified time interval defined.
213+
- Synchronization server – Allows the MFA Server Migration Sync service to run on a secondary MFA Server rather than only run on the primary. To configure the Migration Sync service to run on a secondary server, the `Configure-MultiFactorAuthMigrationUtility.ps1` script must be run on the server to register a certificate with the MFA Server Migration Utility app registration. The certificate is used to authenticate to Microsoft Graph.
213214

214-
The migration process can be an automatic process, or a manual process.
215+
The migration process can be automatic or manual.
215216

216217
The manual process steps are:
217218

218219
1. To begin the migration process for a user or selection of multiple users, press and hold the Ctrl key while selecting each of the user(s) you wish to migrate.
219220
1. After you select the desired users, click **Migrate Users** > **Selected users** > **OK**.
220221
1. To migrate all users in the group, click **Migrate Users** > **All users in AAD group** > **OK**.
222+
1. You can migrate users even if they are unchanged. By default, the utility is set to **Only migrate users that have changed**. Click **Migrate all users** to re-migrate previously migrated users that are unchanged. Migrating unchanged users can be useful during testing if an administrator needs to reset a user’s Azure MFA settings and wants to re-migrate them.
221223

222-
For the automatic process, click **Automatic synchronization** in the settings dialog, and then select whether you want all users to be synced, or only members of a given Azure AD group.
224+
:::image type="content" border="true" source="./media/how-to-mfa-server-migration-utility/migrate-users.png" alt-text="Screenshot of Migrate users dialog.":::
225+
226+
For the automatic process, click **Automatic synchronization** in **Settings**, and then select whether you want all users to be synced, or only members of a given Azure AD group.
223227

224228
The following table lists the sync logic for the various methods.
225229

6.88 KB
Loading
8.87 KB
Loading

0 commit comments

Comments
 (0)