Support for moving Azure SQL resources between Azure regions
This article summarizes support and prerequisites for moving Azure SQL resources between Azure regions with Azure Resource Mover.
Requirements
Requirements are summarized in the following table.
| Feature | Supported/Not supported | Details |
|---|---|---|
| Azure SQL Database Hyperscale | Not supported | Can't move databases in the Azure SQL Hyperscale service tier with Resource Mover. |
| Zone redundancy | Supported | Supported move options: - Between regions that support zone redundancy. - Between regions that don't support zone redundancy. - Between a region that supports zone redundancy to a region that doesn't support zone redundancy. - Between a region that doesn't support zone redundancy to a region that does support zone redundancy. |
| Data sync | Hub/sync database: Not supported Sync member: Supported. |
If a sync member is moved, you need to set up data sync to the new target database. |
| Existing geo-replication | Supported | Existing geo replicas are remapped to the new primary in the target region. Seeding must be initialized after the move. Learn more. |
| Transparent Data Encryption (TDE) with Bring Your Own Key (BYOK) | Supported | Learn more about moving key vaults across regions. |
| TDE with service-managed key | Supported. | Learn more about moving key vaults across regions. |
| Dynamic data masking rules | Supported. | Rules are automatically copied over to the target region as part of the move. Learn more. |
| Advanced data security | Not supported. | Workaround: Set up at the SQL Server level in the target region. Learn more. |
| Firewall rules | Not supported. | Workaround: Set up firewall rules for SQL Server in the target region. Database-level firewall rules are copied from the source server to the target server. Learn more. |
| Auditing policies | Not supported. | Policies will reset to default after the move. Learn how to reset. |
| Backup retention | Supported. | Backup retention policies for the source database are carried over to the target database. Learn how to modify settings after the move. |
| Auto tuning | Not supported. | Workaround: Set auto tuning settings after the move. Learn more. |
| Database alerts | Not supported. | Workaround: Set alerts after the move. Learn more. |
| Azure SQL Server stretch database | Not Supported | Can't move SQL server stretch databases with Resource Mover. |
| Azure Synapse Analytics | Not Supported | Can’t move Azure Synapse Analytics with Resource Mover. |
Next steps
Try moving Azure SQL resources to another region with Resource Mover.
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for