You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/devices/enterprise-state-roaming-enable.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
-
title: Enable Enterprise State Roaming in Azure Active Directory | Microsoft Docs
2
+
title: Enable Enterprise State Roaming in Azure Active Directory
3
3
description: Frequently asked questions about Enterprise State Roaming settings in Windows devices.
4
4
5
5
services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: devices
8
8
ms.topic: conceptual
9
-
ms.date: 06/28/2019
9
+
ms.date: 02/12/2020
10
10
11
11
ms.author: joflore
12
12
author: MicrosoftGuyJFlo
@@ -16,11 +16,15 @@ ms.reviewer: na
16
16
ms.collection: M365-identity-device-management
17
17
---
18
18
# Enable Enterprise State Roaming in Azure Active Directory
19
+
19
20
Enterprise State Roaming is available to any organization with an Azure AD Premium or Enterprise Mobility + Security
20
21
(EMS) license. For more information on how to get an Azure AD subscription, see the [Azure AD product page](https://azure.microsoft.com/services/active-directory).
21
22
22
23
When you enable Enterprise State Roaming, your organization is automatically granted a free, limited-use license for Azure Rights Management protection from Azure Information Protection. This free subscription is limited to encrypting and decrypting enterprise settings and application data synced by Enterprise State Roaming. You must have [a paid subscription](https://azure.microsoft.com/pricing/details/information-protection/) to use the full capabilities of the Azure Rights Management service.
23
24
25
+
> [!NOTE]
26
+
> This article applies to the Microsoft Edge Legacy HTML-based browser launched with Windows 10 in July 2015. The article does not apply to the new Microsoft Edge Chromium-based browser released on January 15, 2020. For more information on the Sync behavior for the new Microsoft Edge, see the article [Microsoft Edge Sync](https://docs.microsoft.com/deployedge/microsoft-edge-enterprise-sync).
27
+
24
28
## To enable Enterprise State Roaming
25
29
26
30
1. Sign in to [Azure AD admin center](https://aad.portal.azure.com/).
@@ -32,6 +36,7 @@ When you enable Enterprise State Roaming, your organization is automatically gra
32
36
For a Windows 10 device to use the Enterprise State Roaming service, the device must authenticate using an Azure AD identity. For devices that are joined to Azure AD, the user’s primary sign-in identity is their Azure AD identity, so no additional configuration is required. For devices that use on-premises Active Directory, the IT admin must [Configure hybrid Azure Active Directory joined devices](hybrid-azuread-join-manual-steps.md).
33
37
34
38
## Data storage
39
+
35
40
Enterprise State Roaming data is hosted in one or more [Azure regions](https://azure.microsoft.com/regions/) that best align with the country/region value set in the Azure Active Directory instance. Enterprise State Roaming data is partitioned based on three major geographic regions: North America, EMEA, and APAC. Enterprise State Roaming data for the tenant is locally located with the geographical region, and is not replicated across regions. For example:
36
41
37
42
| Country/region value | has their data hosted in |
@@ -44,6 +49,7 @@ Enterprise State Roaming data is hosted in one or more [Azure regions](https://a
44
49
The country/region value is set as part of the Azure AD directory creation process and cannot be subsequently modified. If you need more details on your data storage location, file a ticket with [Azure support](https://azure.microsoft.com/support/options/).
45
50
46
51
## View per-user device sync status
52
+
47
53
Follow these steps to view a per-user device sync status report.
48
54
49
55
1. Sign in to [Azure AD admin center](https://aad.portal.azure.com/).
@@ -58,23 +64,27 @@ Follow these steps to view a per-user device sync status report.
58
64

59
65
60
66
## Data retention
67
+
61
68
Data synced to the Microsoft cloud using Enterprise State Roaming is retained until it is manually deleted or until the data in question is determined to be stale.
62
69
63
70
### Explicit deletion
71
+
64
72
Explicit deletion is when an Azure admin deletes a user or a directory or otherwise requests explicitly that data is to be deleted.
65
73
66
74
***User deletion**: When a user is deleted in Azure AD, the user account roaming data is deleted after 90 to 180 days.
67
75
***Directory deletion**: Deleting an entire directory in Azure AD is an immediate operation. All the settings data associated with that directory is deleted after 90 to 180 days.
68
76
***On request deletion**: If the Azure AD admin wants to manually delete a specific user’s data or settings data, the admin can file a ticket with [Azure support](https://azure.microsoft.com/support/).
69
77
70
78
### Stale data deletion
79
+
71
80
Data that has not been accessed for one year (“the retention period”) will be treated as stale and may be deleted from the Microsoft cloud. The retention period is subject to change but will not be less than 90 days. The stale data may be a specific set of Windows/application settings or all settings for a user. For example:
72
81
73
82
* If no devices access a particular settings collection (for example, an application is removed from the device, or a settings group such as “Theme” is disabled for all of a user’s devices), then that collection becomes stale after the retention period and may be deleted.
74
83
* If a user has turned off settings sync on all their devices, then none of the settings data will be accessed, and all the settings data for that user will become stale and may be deleted after the retention period.
75
84
* If the Azure AD directory admin turns off Enterprise State Roaming for the entire directory, then all users in that directory will stop syncing settings, and all settings data for all users will become stale and may be deleted after the retention period.
76
85
77
86
### Deleted data recovery
87
+
78
88
The data retention policy is not configurable. Once the data is permanently deleted, it is not recoverable. However, The settings data is deleted only from the Microsoft cloud, not from the end-user device. If any device later reconnects to the Enterprise State Roaming service, the settings are again synced and stored in the Microsoft cloud.
Copy file name to clipboardExpand all lines: articles/active-directory/devices/enterprise-state-roaming-faqs.md
+26-10Lines changed: 26 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
-
title: Settings and data roaming FAQ | Microsoft Docs
3
-
description: Provides answers to some questions IT administrators might have about settings and app data sync.
2
+
title: Enterprise State Roaming FAQ - Azure Active Directory
3
+
description: Frequently asked questions about ESR
4
4
5
5
services: active-directory
6
6
ms.service: active-directory
7
7
ms.subservice: devices
8
8
ms.topic: troubleshooting
9
-
ms.date: 06/28/2019
9
+
ms.date: 02/12/2020
10
10
11
11
ms.author: joflore
12
12
author: MicrosoftGuyJFlo
@@ -16,23 +16,29 @@ ms.reviewer: na
16
16
ms.collection: M365-identity-device-management
17
17
---
18
18
# Settings and data roaming FAQ
19
+
19
20
This article answers some questions IT administrators might have about settings and app data sync.
20
21
21
22
## What data roams?
23
+
22
24
**Windows settings**:
23
25
the PC settings that are built into the Windows operating system. Generally, these are settings that personalize your PC, and they include the following broad categories:
24
26
25
27
**Theme*, which includes features such as desktop theme and taskbar settings.
26
28
**Internet Explorer settings*, including recently opened tabs and favorites.
27
29
**Microsoft Edge browser settings*, such as favorites and reading list.
28
30
**Passwords*, including Internet passwords, Wi-Fi profiles, and others.
29
-
**Language preferences*, which includes settings for keyboard layouts, system language, date and time, and more.
31
+
**Language preferences*, which include settings for keyboard layouts, system language, date and time, and more.
30
32
**Ease of access features*, such as high-contrast theme, Narrator, and Magnifier.
31
33
**Other Windows settings*, such as mouse settings.
32
34
33
-
**Application data**: Universal Windows apps can write settings data to a roaming folder, and any data written to this folder will automatically be synced. It’s up to the individual app developer to design an app to take advantage of this capability. For more details about how to develop a Universal Windows app that uses roaming, see the [appdata storage API](https://msdn.microsoft.com/library/windows/apps/mt299098.aspx) and the [Windows 8 appdata roaming developer blog](https://blogs.msdn.com/b/windowsappdev/archive/2012/07/17/roaming-your-app-data.aspx).
35
+
> [!NOTE]
36
+
> This article applies to the Microsoft Edge Legacy HTML-based browser launched with Windows 10 in July 2015. The article does not apply to the new Microsoft Edge Chromium-based browser released on January 15, 2020. For more information on the Sync behavior for the new Microsoft Edge, see the article [Microsoft Edge Sync](https://docs.microsoft.com/deployedge/microsoft-edge-enterprise-sync).
37
+
38
+
**Application data**: Universal Windows apps can write settings data to a roaming folder, and any data written to this folder will automatically be synced. It’s up to the individual app developer to design an app to take advantage of this capability. For more information about how to develop a Universal Windows app that uses roaming, see the [appdata storage API](https://msdn.microsoft.com/library/windows/apps/mt299098.aspx) and the [Windows 8 appdata roaming developer blog](https://blogs.msdn.com/b/windowsappdev/archive/2012/07/17/roaming-your-app-data.aspx).
34
39
35
40
## What account is used for settings sync?
41
+
36
42
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, this connected Microsoft account functionality is being replaced with a primary/secondary account framework.
37
43
38
44
The primary account is defined as the account used to sign in to Windows. This can be a Microsoft account, an Azure Active Directory (Azure AD) account, an on-premises Active Directory account, or a local account. In addition to the primary account, Windows 10 users can add one or more secondary cloud accounts to their device. A secondary account is generally a Microsoft account, an Azure AD account, or some other account such as Gmail or Facebook. These secondary accounts provide access to additional services such as single sign-on and the Windows Store, but they are not capable of powering settings sync.
@@ -49,10 +55,9 @@ If an app’s owner cannot be identified, it will roam with the primary account.
49
55
50
56
> [!NOTE]
51
57
> Windows 10 devices that are enterprise-owned and are connected to Azure AD can no longer connect their Microsoft accounts to a domain account. The ability to connect a Microsoft account to a domain account and have all the user's data sync to the Microsoft account (that is, the Microsoft account roaming via the connected Microsoft account and Active Directory functionality) is removed from Windows 10 devices that are joined to a connected Active Directory or Azure AD environment.
52
-
>
53
-
>
54
58
55
59
## How do I upgrade from Microsoft account settings sync in Windows 8 to Azure AD settings sync in Windows 10?
60
+
56
61
If you are joined to the Active Directory domain running Windows 8.1 with a connected Microsoft account, you will sync settings through your Microsoft account. After upgrading to Windows 10, you will continue to sync user settings via Microsoft account as long as you are a domain-joined user and the Active Directory domain does not connect with Azure AD.
57
62
58
63
If the on-premises Active Directory domain does connect with Azure AD, your device will attempt to sync settings using the connected Azure AD account. If the Azure AD administrator does not enable Enterprise State Roaming, your connected Azure AD account will stop syncing settings. If you are a Windows 10 user and you sign in with an Azure AD identity, you will start syncing windows settings as soon as your administrator enables settings sync via Azure AD.
@@ -63,9 +68,11 @@ If you stored any personal data on your corporate device, you should be aware th
63
68
* Personal data such as Wi-Fi passwords, web credentials, and Internet Explorer favorites that were previously synced via a connected Microsoft account will be synced via Azure AD.
64
69
65
70
## How do Microsoft account and Azure AD Enterprise State Roaming interoperability work?
71
+
66
72
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 Azure AD account, all data will sync via Azure AD. If you sign in to Windows by using a personal Microsoft account, all data will sync via the Microsoft account. Universal appdata will roam using only the primary sign-in account on the device, and it will roam only if the app’s license is owned by the primary account. Universal appdata for the apps owned by any secondary accounts will not be synced.
67
73
68
74
## Do settings sync for Azure AD accounts from multiple tenants?
75
+
69
76
When multiple Azure AD accounts from different Azure AD tenants are on the same device, you must update the device's registry to communicate with the Azure Rights Management service for each Azure AD tenant.
70
77
71
78
1. Find the GUID for each Azure AD tenant. Open the Azure portal and select an Azure AD tenant. The GUID for the tenant is on the Properties page for the selected tenant (https://portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Properties), labeled **Directory ID**.
@@ -75,6 +82,7 @@ When multiple Azure AD accounts from different Azure AD tenants are on the same
75
82
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 just once.
76
83
77
84
## What are the roaming settings options for existing Windows desktop applications?
85
+
78
86
Roaming only works for Universal Windows apps. There are two options available for enabling roaming on an existing Windows desktop application:
79
87
80
88
* The [Desktop Bridge](https://aka.ms/desktopbridge) helps you bring your existing Windows desktop apps to the Universal Windows Platform. From here, minimal code changes will be required to take advantage of Azure AD app data roaming. The Desktop Bridge provides your apps with an app identity, which is needed to enable app data roaming for existing desktop apps.
@@ -88,36 +96,44 @@ Administrators can configure UE-V to roam Windows desktop app data by changing r
88
96
89
97
In the future, Microsoft may investigate ways to make UE-V deeply integrated into Windows and extend UE-V to roam settings through the Azure AD cloud.
90
98
91
-
## Can I store synced settings and data on premises?
99
+
## Can I store synced settings and data on-premises?
100
+
92
101
Enterprise State Roaming stores all synced data in the Microsoft cloud. UE-V offers an on-premises roaming solution.
93
102
94
103
## Who owns the data that’s being roamed?
104
+
95
105
The enterprises own the data roamed via Enterprise State Roaming. Data is stored in an Azure datacenter. All user data is encrypted both in transit and at rest in the cloud using the Azure Rights Management service from Azure Information Protection. This is an improvement compared to Microsoft account-based settings sync, which encrypts only certain sensitive data such as user credentials before it leaves the device.
96
106
97
107
Microsoft is committed to safeguarding customer data. An enterprise user’s settings data is automatically encrypted by the Azure Rights Management service before it leaves a Windows 10 device, so no other user can read this data. If your organization has a paid subscription for the Azure Rights Management service, you can use other protection features, such as track and revoke documents, automatically protect emails that contain sensitive information, and manage your own keys (the "bring your own key" solution, also known as BYOK). For more information about these features and how this protection service works, see [What is Azure Rights Management](/azure/information-protection/what-is-information-protection).
98
108
99
109
## Can I manage sync for a specific app or setting?
110
+
100
111
In Windows 10, there is no MDM or Group Policy setting to disable roaming for an individual application. Tenant administrators can disable appdata sync for all apps on a managed device, but there is no finer control at a per-app or within-app level.
101
112
102
113
## How can I enable or disable roaming?
114
+
103
115
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.
104
116
105
117
## What is Microsoft’s recommendation for enabling roaming in Windows 10?
118
+
106
119
Microsoft has a few different settings roaming solutions available, including Roaming User Profiles, UE-V, and Enterprise State Roaming. Microsoft is committed to making an investment in Enterprise State Roaming in future versions of Windows. If your organization is not 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 very similar technologies, they are not mutually exclusive. They complement each other to help ensure that your organization provides the roaming services that your users need.
107
120
108
121
When using both Enterprise State Roaming and UE-V, the following rules apply:
109
122
110
123
* Enterprise State Roaming is the primary roaming agent on the device. UE-V is being used to supplement the “Win32 gap.”
111
-
* UE-V roaming for Windows settings and modern UWP app data should be disabled when using the UE-V group polices. These are already covered by Enterprise State Roaming.
124
+
* UE-V roaming for Windows settings and modern UWP app data should be disabled when using the UE-V group policies. These are already covered by Enterprise State Roaming.
112
125
113
126
## How does Enterprise State Roaming support virtual desktop infrastructure (VDI)?
127
+
114
128
Enterprise State Roaming is supported on Windows 10 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 is not officially supported.
115
129
116
130
## What happens when my organization purchases a subscription that includes Azure Rights Management after using roaming?
131
+
117
132
If your organization is already using roaming in Windows 10 with the Azure Rights Management limited-use free subscription, purchasing a [paid subscription](https://azure.microsoft.com/pricing/details/information-protection/) that includes the Azure Rights Management protection service will not have any impact on the functionality of the roaming feature, and no configuration changes will be required by your IT administrator.
118
133
119
134
## Known issues
120
-
Please see the documentation in the [troubleshooting](enterprise-state-roaming-troubleshooting.md) section for a list of known issues.
135
+
136
+
See the documentation in the [troubleshooting](enterprise-state-roaming-troubleshooting.md) section for a list of known issues.
0 commit comments