Settings and data roaming FAQ for administrators

In Windows 8.1, settings sync always used consumer Microsoft accounts. Enterprise users had the ability to connect a Microsoft account to their Active Directory domain account to gain access to settings sync. In Windows 10 and newer, this connected Microsoft account functionality is being replaced with a primary/secondary account framework.

The primary account is defined as the account used to sign in to Windows. This can be a Microsoft account, a Microsoft Entra account, an on-premises Active Directory account, or a local account. In addition to the primary account, Windows 10 and newer users can add one or more secondary cloud accounts to their device. A secondary account is generally a Microsoft account, a Microsoft Entra account, or some other account such as Gmail or Facebook. These secondary accounts provide access to other services such as single sign-on and the Windows Store, but they aren't capable of powering settings sync.

Data is never mixed between the different user accounts on the device. There are two rules for settings sync:

• Windows settings always roam with the primary account.
• App data is tagged with the account used to acquire the app. Only apps tagged with the primary account sync. App ownership tagging is determined when an app is side-loaded through the Windows Store or mobile device management (MDM).

If an application owner can't be identified, it will roam with the primary account. If a device is upgraded from Windows 8 or Windows 8.1 to Windows 10 and newer, all the apps are tagged as acquired by the Microsoft account. This is because most users acquire apps through the Windows Store, and there was no Windows Store support for Microsoft Entra accounts prior to Windows 10. If an app is installed via an offline license, the app is tagged using the primary account on the device.

After upgrading to Windows 10 and newer, you continue to sync user settings via Microsoft account as long as you're a domain-joined user, and the Active Directory domain doesn't connect with Microsoft Entra ID.

If the on-premises Active Directory domain does connect with Microsoft Entra ID, your device attempts to sync settings using the connected Microsoft Entra account. If the Microsoft Entra administrator doesn't enable Enterprise State Roaming, your connected Microsoft Entra account stops syncing settings. If you're running Windows 10 and newer and you sign in with a Microsoft Entra identity, you start syncing windows settings as soon as your administrator enables settings sync via Microsoft Entra ID.

If you stored any personal data on your corporate device, you should know Windows OS and application data begin syncing to Microsoft Entra ID. This has the following implications:

• Your personal Microsoft account settings will drift from the settings on your work or school Microsoft Entra accounts. This is because the Microsoft account and Microsoft Entra settings sync are now using separate accounts.
• Personal data such as Wi-Fi passwords, web credentials, and Internet Explorer favorites that were previously synced via a connected Microsoft account is synced via Microsoft Entra ID.

In the November 2015 or later releases of Windows 10, Enterprise State Roaming is only supported for a single account at a time. If you sign in to Windows by using a work or school Microsoft Entra account, all data syncs via Microsoft Entra ID. If you sign in to Windows by using a personal Microsoft account, all data syncs via the Microsoft account. Universal app data roam using only the primary sign-in account on the device, and it roams only if the app's license is owned by the primary account. Universal app data for the apps owned by any secondary accounts isn't synced.

When multiple Microsoft Entra accounts from different Microsoft Entra tenants are on the same device, you must update the device's registry to communicate with the Azure Rights Management service for each Microsoft Entra tenant.

1. Find the GUID for each Microsoft Entra tenant. Sign in to the Microsoft Entra admin center, browse to Identity > Overview > Properties > Tenant ID.
2. After you have the GUID, you'll need to add the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\SettingSync\WinMSIPC<tenant ID GUID>. From the tenant ID GUID key, create a new Multi-String value (REG-MULTI-SZ) named AllowedRMSServerUrls. For its data, specify the licensing distribution point URLs of the other Azure tenants that the device accesses.
3. You can find the licensing distribution point URLs by running the Get-AadrmConfiguration cmdlet from the AADRM module. If the values for the LicensingIntranetDistributionPointUrl and LicensingExtranetDistributionPointUrl are different, specify both values. If the values are the same, specify the value once.

Enterprise State Roaming stores all synced data in the Microsoft cloud. UE-V offers an on-premises roaming solution.

Prior to Nov 2022 all user data was secured using Azure Rights Management.

Starting in November 2022, Microsoft no longer uses Azure Rights Management for all data encryption. Microsoft is committed to safeguarding customer data. Certain sensitive data such as passwords are encrypted client side with keys derived from the Microsoft Entra tenant to ensure an extra layer of security. All user data (including nonsensitive data) is encrypted in transit and at rest in the cloud. For a list of sensitive and nonsensitive data items roamed, see Windows roaming settings reference.

In Windows 10 or newer, administrators can disable sync for all settings sync groups on a managed device with MDM or Group Policy.

In the Settings app, go to Accounts > Sync your settings. From this page, you can see which account is being used to roam settings, and you can enable or disable individual groups of settings to be roamed.

Microsoft has a few different settings roaming solutions available, including UE-V and Enterprise State Roaming. If your organization isn't ready or comfortable with moving data to the cloud, then we recommend that you use UE-V as your primary roaming technology. If your organization requires roaming support for existing Windows desktop applications but is eager to move to the cloud, we recommend that you use both Enterprise State Roaming and UE-V. Although UE-V and Enterprise State Roaming are similar technologies, they aren't mutually exclusive. They complement each other to help ensure that your organization provides the roaming services that your users need.

When using both Enterprise State Roaming and UE-V, Enterprise State Roaming is the primary roaming agent on the device. UE-V is being used to supplement Win32 applications.

• Enterprise State Roaming is the primary roaming agent on the device. UE-V is being used to supplement the "Win32 gap."
• UE-V roaming for Windows settings and modern UWP app data should be disabled when using the UE-V group policies. These settings are already covered by Enterprise State Roaming.

Enterprise State Roaming is supported on Windows 10 or newer client SKUs, but not on server SKUs. If a client VM is hosted on a hypervisor machine and you remotely sign in to the virtual machine, your data will roam. If multiple users share the same OS and users remotely sign in to a server for a full desktop experience, roaming might not work. The latter session-based scenario isn't officially supported.

The per-user device sync status report was removed from the Microsoft Entra admin center. The report was removed because it only provided details for unsupported versions of Windows. Enterprise state roaming requires Windows 11 or Windows 10 version 21H2 or newer.

Next steps

For an overview, see enterprise state roaming overview