Skip to main content
Druva Documentation

Microsoft 365 Multi-Geo for Exchange Online and OneDrive users in inSync

inSync Cloud Editions: File:/tick.png Elite Plus File:/tick.png Elite File:/cross.png Enterprise File:/cross.png Business


Many financial and legal services organizations use Microsoft 365 with Multi-Geo to provision and store data at rest in the Microsoft 365 supported geo-locations to meet their data residency requirements. This feature is to enable such organizations to protect Exchange Online and OneDrive data of Microsoft 365 Multi-Geo enabled tenants, inSync now lets you assign Druva storage to users based on their geo-location.

Things to consider while managing Exchange Online and OneDrive users for Microsoft Multi-Geo

inSync administrators can ensure continuous data protection of a user’s Exchange Online and OneDrive data whenever your organization enables Multi-Geo in its Microsoft 365 tenant.

As an inSync administrator, you might have to take the necessary actions as listed below:

  • Ensure that Druva AWS storage regions exist for all data sources for your Microsoft 365 enabled geo-locations. To enable the desired AWS storage regions, contact Druva Support

  • Determine the user’s region attribute to be used within your preferred user provisioning method to map and manage users. Here are a few scenarios:

    • If your preferred method to import users is on-prem AD to import users

      • Decide  the user attribute in AD which uniquely identifies the user’s geo-location or country

      • Use this attribute to create region-wise AD mapping in Druva inSync to map users with profile and region-specific Druva AWS storage. For more information, see Create an AD/LDAP mapping.

    • If your preferred method to map users is Azure AD, then you can use SCIM mapping with Azure AD

      • Leverage user Preferred Data Location (PDL) attribute in Azure AD to define Attribute Mappings between Azure AD and Druva inSync. For more information, see Manage Users from Azure Active Directory using SCIM

      • Define region-wise SCIM mapping in Druva inSync to map users with profile and region-specific Druva AWS storage.
    • Change in user’s Preferred Data Location (PDL)

      • If the user’s PDL changes, you can change and assign Druva AWS storage region as per the new geo-location or country. For more information, see Change storage assigned to a user.

The older snapshot will continue to remain in the previous region prior to the PDL changes.

 Note: For planned support of SharePoint Online and Microsoft Teams, contact  Druva Support.

  • Was this article helpful?