The attribute is of the type, single-valued string. The schema of the object type User in the Azure AD Connector is extended to include the preferredDataLocation attribute.Azure AD Connect support for synchronizationĪzure AD Connect supports synchronization of the preferredDataLocation attribute for User objects in version 1.1.524.0 and later. Please talk to your Microsoft representative for details.įor a list of all geos supported by Azure AD Connect see Microsoft 365 Multi-Geo availability. Multi-Geo is also available to customers with an active Enterprise Agreement. You can have the user's Microsoft 365 resources, such as the mailbox and OneDrive, in the same geo as the user, and still have one tenant for your entire organization.Īs of June 1, 2023, Multi-Geo is available for CSP partners to purchase, at a minimum of 5% of their customer’s total Microsoft 365 subscription seats. For a multinational organization, this might not be optimal.īy setting the attribute preferredDataLocation, you can define a user's geo. For example, if the Tenant is located in North America, then the users' Exchange mailboxes are also located in North America. (The terms region and geo are used interchangeably.) Supported Multi-Geo locationsįor a list of all geos supported by Azure AD Connect see Microsoft 365 Multi-Geo availability Enable synchronization of preferred data locationīy default, Microsoft 365 resources for your users are located in the same geo as your Azure AD tenant. When someone uses Multi-Geo capabilities in Microsoft 365, you use this attribute to designate the geo-location of the user’s Microsoft 365 data.
#WWW MICROSOFT 365 HOW TO#
The purpose of this topic is to walk you through how to configure the attribute for preferred data location in Azure Active Directory (Azure AD) Connect sync.
0 kommentar(er)
