Applies to Product - Dynamics 365 Lifecycle Services
What’s happening?
The customer has requested to retain their primary region as UK South while setting the secondary backup location to India to meet audit requirements regarding data residency.
Reason:
Customers cannot manually select the secondary region for backups as it is predefined by Azure based on the primary region.
Resolution:
- Inform the customer that the secondary region is automatically determined by Azure and cannot be manually set.
- If the customer requires backups to reside in a specific region (e.g., India for compliance purposes), suggest the following custom backup solutions:
- Export critical data from the environment regularly using tools like Azure Data Factory, Power Automate, or the Data Management Framework (DMF), and store it in Azure resources (e.g., Blob Storage, SQL Database) in the required region.
- Ensure that the exported data complies with regulations around encryption, retention, and access.
- If full data residency is required for compliance, advise deploying a new environment in the desired region (e.g., India), which may involve additional licensing and operational costs.