Skip to main content

How can we help you?

Druva Documentation

Multi-Geo support 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

Overview

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.

Enable Multi-Geo capabilities for Microsoft 365 tenant

Microsoft allows you to enable Multi-Geo capabilities for your Microsoft 365 tenant. By enabling Multi-Geo capabilities on the tenant, you can have a single Microsoft 365 tenant that spans across multiple data center geographies, and have full control over where the data is stored. Currently, Multi-Geo is supported for Exchange Online, OneDrive, and SharePoint.


In a Multi-Geo tenant, information about geo locations, groups, and locations is mastered in the Azure active directory (AD). Administrators can use service admin centers to manage geo locations. For more information, see Microsoft documentation.

You may have to reach out to a Microsoft account representative to enable this feature for your Microsoft 365 tenant.

Enable data locations

In a Multi-Geo tenant, users are assigned to a Preferred Data Location (PDL) where data is stored. For new users, their Exchange mailbox and OneDrive will be set up in that location. For existing users, Exchange Online data will be moved to the new location, but an additional step is needed for OneDrive to migrate to the new location. Microsoft provides the ability to change user data location and will move data from one location to another when a user changes locations via multiple PowerShell Commands. Here are a few examples of these sample commands:

Things to consider for Microsoft Multi-Geo

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 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:

    • Import users using Azure AD Integration: You can import users from Microsoft 365 Multi-Geo tenant based on their geo location, group them in a profile and assign Druva storage as per their geo location. Create Azure AD mapping with the attribute name as preferredDataLocation. For example, if your preferred geo location is Canada, create Azure AD mapping as follows: Azure AD Attribute {preferredDataLocation} = {CAN} For more information, see Create Azure AD mapping.

    • 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.

  • Was this article helpful?