Howe do you change Microsoft Purview Regions without losing data?

Question

We have created DLP, Information Protection and IRM policies in Region West of Purview. When it should have been in the East Region. Are we able to change the region without losing all the data? Our origination is expanding Purview to utilize the data catalog and Data Mapping which used to be Azure Purview but is now bundled. We are trying to determine if we move to the EAST region if everything needs to be recreated or if you can have Parts of the Purview in East (Data Governance) and parts of Purview in East (Information Protection, DLP, Insider Risk Mgmt)? We have asked our CSM and have yet to get a clear understanding of the downstream impacts... Please advise..

Answer 1

Hi @User123456789

According to this documentation: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-support-resources#microsoftpurview

Microsoft Purview services, including DLP, Information Protection, and Insider Risk Management, are region-bound, meaning they cannot be moved across regions.

However, here are the key considerations and possible solutions:

• Microsoft does not support moving Purview accounts or policies between regions. You will need to manually recreate the policies in the new region.
• Data does not automatically transfer when switching regions, and there is no built-in migration tool for moving Purview resources between regions.

Multi-Region Setup

• You can have different Purview services in different regions:
  • Data Governance (Catalog, Data Mapping) in East
  • Information Protection, DLP, and Insider Risk Management in West
• However, there might be latency and integration limitations when operating across multiple regions.

Reference: https://techcommunity.microsoft.com/blog/microsoft-security-blog/introducing-multi-region-and-multi-vnets-for-managed-virtual-network-in-microsof/4034144?utm_

Considerations Before Moving to the East Region

• Data Residency & Compliance: Ensure your policies comply with data residency requirements.
• Manual Recreation Effort: You will need to export policies, configurations, and mappings and then manually recreate them in the new region.
• Integration Challenges: If Purview services are split between regions, ensure cross-region compatibility before deployment.

For more details refer: How does Microsoft Purview choose the region for the enterprise version of Microsoft Purview?

• Supported regions for Microsoft Purview Data Governance

Hope this helps. Do let us know if you have any further queries.