You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/move-resources-overview.md
+119Lines changed: 119 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,6 +61,125 @@ You can move resources to another region using a couple of different methods:
61
61
62
62
To move resources that aren't supported by Azure Resource Mover or to move any service manually, see [Azure services relocation guidance overview](/azure/operational-excellence/overview-relocation).
63
63
64
+
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.
65
+
66
+
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](/azure/cloud-adoption-framework/relocate/) as well as the following Well-architected Framework (WAF) Operational Excellence principles:
67
+
68
+
*[Deploy with confidence](/azure/well-architected/operational-excellence/principles#deploy-with-confidence)
* Possible and actual service dependencies that also require relocation planning.
77
+
* Lists of considerations, features, and limitations in relation to relocation planning for that service.
78
+
* Links to how-tos and relevant product-specific relocation information.
79
+
80
+
The following tables provide links to each Azure service relocation document. The tables also provide information on which kind of relocation method is supported.
81
+
82
+
#### Analytics
83
+
84
+
| Product | Relocation | Relocation with data migration | Resource Mover |
### Move resources from non availability zone to availability zone support
65
184
66
185
To move resources from a region that doesn't support availability zones to one that does, see [Availability zone migration guidance overview for Microsoft Azure products and services](/azure/reliability/availability-zones-migration-overview).
>Customers with fast release cycles often leverage CI/CD pipelines. In those cases, you might consider altering the build and release pipelines instead of re-deploying the AKS clusters in the target region.
15
+
>[!NOTE]
16
+
>Customers with fast release cycles often leverage CI/CD pipelines. In those cases, you might consider altering the build and release pipelines instead of re-deploying the AKS clusters in the target region.
17
17
18
18
## Prerequisites
19
19
@@ -36,7 +36,7 @@ Before you begin the relocation planning stage, first review the following prere
-[Virtual Network configuration](./relocation-virtual-network.md). Define sufficient subnet sizes to allow container IP growth if using the Azure advanced networking model
41
41
- Public IP address
42
42
- Virtual Network Gateway (VNG). If site-to-site communication is required to an on-premises environment in the target region, a VNG must be created in the target virtual network.
0 commit comments