Edit

Azure services relocation guidance overview (Preview)

  • Article

As Microsoft continues to expand Azure global infrastructure and launch new Azure regions worldwide, there's an increasing number of options available for you to relocate your workloads into new regions. Region relocation options vary by service and by workload architecture. To successfully relocate a workload to another region, you need to plan your relocation strategy with an understanding of what each service in your workload requires and supports.

Azure region relocation documentation (Preview) contains service-specific relocation guidance for Azure products and services. The relocation documentation set is founded on both Azure Cloud Adoption Framework - Relocate cloud workloads as well as the following Well-architected Framework (WAF) Operational Excellence principles:

Each service specific guide can contain service-specific information on topics such as:

Service categories across region types

Azure services are grouped into three categories: foundational, mainstream, and strategic. Azure's general policy on deploying services into any given region is primarily driven by region type, service categories, and customer demand.

  • Foundational: Available in all recommended and alternate regions when the region is generally available, or within 90 days of a new foundational service becoming generally available.
  • Mainstream: Available in all recommended regions within 90 days of the region general availability. Demand-driven in alternate regions, and many are already deployed into a large subset of alternate regions.
  • Strategic (previously Specialized): Targeted service offerings, often industry-focused or backed by customized hardware. Demand-driven availability across regions, and many are already deployed into a large subset of recommended regions.

To see which services are deployed in a region and the future roadmap for preview or general availability of services in a region, see Products available by region.

If a service offering isn't available in a region, contact your Microsoft sales representative for more information and to explore options.

Region type Non-regional Foundational Mainstream Strategic Availability zones Data residency
Recommended Y Y Y Demand-driven Y Y
Alternate Y Y Demand-driven Demand-driven N/A Y

Azure services relocation guides

The following tables provide links to each Azure service relocation document. The tables also provide information on which kind of relocation method is supported.

An icon that signifies this service is foundational. Foundational services

Product Relocation with data Relocation without data Resource Mover
Azure Key Vault ✅ ✅ ❌
Azure Event Hubs ❌ ✅ ❌
Azure Event Hubs Cluster ❌ ✅ ❌
Azure Key Vault ✅ ✅ ❌
Azure Site Recovery (Recovery Services vaults) ✅ ✅ ❌
Azure Virtual Network ❌ ✅ ✅
Azure Virtual Network - Network Security Groups ❌ ✅ ✅

An icon that signifies this service is mainstream. Mainstream services

Product Relocation with data Relocation without data Resource Mover
Azure API Management ✅ ✅ ❌
Azure App Service ❌ ✅ ❌
Azure Backup (Recovery Services vault) ✅ ✅ ❌
Azure Batch ✅ ✅ ❌
Azure Cache for Redis ❌ ✅ ❌
Azure Container Registry ✅ ✅ ❌
Azure Cosmos DB ✅ ✅ ❌
Azure Database for MariaDB Server ✅ ✅ ❌
Azure Database for MySQL Server✅ ✅ ❌
Azure Database for PostgreSQL ✅ ✅ ❌
Azure Functions ❌ ✅ ❌
Azure Logic apps ❌ ✅ ❌
Azure Monitor - Log Analytics ❌ ✅ ❌
Azure Private Link Service ❌ ✅ ❌
Azure Storage Account ✅ ✅ ❌
Managed identities for Azure resources ❌ ✅ ❌
Azure Stream Analytics - Stream Analytics jobs ✅ ✅ ❌
Azure Stream Analytics - Stream Analytics cluster ✅ ✅ ❌

An icon that signifies this service is strategic. Strategic services

Product Relocation with data Relocation without data Resource Mover
Azure Automation ✅ ✅ ❌
Azure IoT Hub ✅ ✅ ❌
Power BI ❌ ✅ ❌

Additional information