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/automation/how-to/move-account.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -130,7 +130,5 @@ When the move is complete, verify that the capabilities listed below are enabled
130
130
131
131
## Next steps
132
132
133
-
134
-
To learn how to move Automation to a new region, see [Move Automation account to another region](../../operational-excellence/relocation-automation.md).
135
-
136
-
To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
133
+
- To learn how to move Automation to a new region, see [Move Automation account to another region](../../azure-resource-manager/management/relocation/relocation-automation.md).
134
+
- To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/relocation/relocation-app-gateway.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ ms.custom:
41
41
42
42
To relocate Application Gateway and optional WAF, you must create a separate Application Gateway deployment with a new public IP address at the target location. Workloads are then migrated from the source Application Gateway setup to the new one. Since you're changing the public IP address, changes to DNS configuration, virtual networks, and subnets are also required.
43
43
44
-
If you only want to relocate in order to gain availability zones support, see [Migrate Application Gateway and WAF to availability zone support](../reliability/migrate-app-gateway-v2.md).
44
+
If you only want to relocate in order to gain availability zones support, see [Migrate Application Gateway and WAF to availability zone support](../../../reliability/migrate-app-gateway-v2.md).
45
45
46
46
**To create a separate Application Gateway, WAF (optional) and IP address:**
47
47
@@ -54,10 +54,10 @@ If you only want to relocate in order to gain availability zones support, see [M
54
54
1. Confirm that the backend pool server or service, such as VM, Virtual Machine Scale Sets, PaaS, is relocated *before* you relocate.
55
55
56
56
1. Create an Application Gateway and configure a new Frontend Public IP Address for the virtual network:
57
-
- Without WAF: [Create an application gateway](../application-gateway/quick-create-portal.md#create-an-application-gateway).
58
-
- With WAF: [Create an application gateway with a Web Application Firewall](../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md).
57
+
- Without WAF: [Create an application gateway](../../../application-gateway/quick-create-portal.md#create-an-application-gateway).
58
+
- With WAF: [Create an application gateway with a Web Application Firewall](../../../web-application-firewall/ag/application-gateway-web-application-firewall-portal.md).
59
59
60
-
1. If you have a WAF config or custom rules-only WAF Policy, [transition it to to a full WAF policy](../web-application-firewall/ag/migrate-policy.md).
60
+
1. If you have a WAF config or custom rules-only WAF Policy, [transition it to to a full WAF policy](../../../web-application-firewall/ag/migrate-policy.md).
61
61
62
62
1. If you use a zero-trust network (source region) for web applications with Azure Firewall and Application Gateway, follow the guidelines and strategies in [Zero-trust network for web applications with Azure Firewall and Application Gateway](/azure/architecture/example-scenario/gateway/application-gateway-before-azure-firewall).
App Service resources are region-specific and can't be moved across regions. You must create a copy of your existing App Service resources in the target region, then relocate your content over to the new app. If your source app uses a custom domain, you can [migrate it to the new app in the target region](../app-service/manage-custom-dns-migrate-domain.md) after completion of the relocation.
18
+
App Service resources are region-specific and can't be moved across regions. You must create a copy of your existing App Service resources in the target region, then relocate your content over to the new app. If your source app uses a custom domain, you can [migrate it to the new app in the target region](../../../app-service/manage-custom-dns-migrate-domain.md) after completion of the relocation.
19
19
20
-
To make copying your app easier, you can [backup and restore individual App Service app](../app-service/manage-backup.md?tabs=portal) into an App Service plan in another region.
20
+
To make copying your app easier, you can [backup and restore individual App Service app](../../../app-service/manage-backup.md?tabs=portal) into an App Service plan in another region.
21
21
22
22
## Prerequisites
23
23
@@ -32,14 +32,14 @@ To make copying your app easier, you can [backup and restore individual App Serv
32
32
Identify all the App Service resources that you're currently using. For example:
33
33
34
34
- App Service apps
35
-
-[App Service plans](../app-service/overview-hosting-plans.md)
Certain resources, such as imported certificates or hybrid connections, contain integration with other Azure services. For information on how to move those resources across regions, see the [documentation for the respective services](overview-relocation.md).
45
45
@@ -153,12 +153,12 @@ Keep in mind that for App Service Environment (Isolated) tiers, you need to rede
153
153
154
154
**To relocate your App Service resources to a new region using Azure portal:**
155
155
156
-
1.[Create a back up of the source app](../app-service/manage-backup.md).
157
-
1.[Create an app in a new App Service plan, in the target region](../app-service/app-service-plan-manage.md#create-an-app-service-plan).
158
-
1.[Restore the back up in the target app](../app-service/manage-backup.md)
159
-
1. If you use a custom domain, [bind it preemptively to the target app](../app-service/manage-custom-dns-migrate-domain.md#2-create-the-dns-records) with `asuid.` and [enable the domain in the target app](../app-service/manage-custom-dns-migrate-domain.md#3-enable-the-domain-for-your-app).
156
+
1.[Create a back up of the source app](../../../app-service/manage-backup.md).
157
+
1.[Create an app in a new App Service plan, in the target region](../../../app-service/app-service-plan-manage.md#create-an-app-service-plan).
158
+
1.[Restore the back up in the target app](../../../app-service/manage-backup.md)
159
+
1. If you use a custom domain, [bind it preemptively to the target app](../../../app-service/manage-custom-dns-migrate-domain.md#2-create-the-dns-records) with `asuid.` and [enable the domain in the target app](../../../app-service/manage-custom-dns-migrate-domain.md#3-enable-the-domain-for-your-app).
160
160
1. Configure everything else in your target app to be the same as the source app and verify your configuration.
161
-
1. When you're ready for the custom domain to point to the target app, [remap the domain name](../app-service/manage-custom-dns-migrate-domain.md#4-remap-the-active-dns-name).
161
+
1. When you're ready for the custom domain to point to the target app, [remap the domain name](../../../app-service/manage-custom-dns-migrate-domain.md#4-remap-the-active-dns-name).
162
162
163
163
### Relocate using IaC
164
164
@@ -169,7 +169,7 @@ SLA requirements should determine how much additional effort is required. For ex
169
169
The inclusion of external, global traffic routing edge services, such as Traffic Manager, or Azure Front Door help to facilitate cut-over for external users and applications.
170
170
171
171
>[!TIP]
172
-
>It's possible to use Traffic Manager (ATM) when failing over App Services behind private endpoints. Although the private endpoints are not reachable by Traffic Manager Probes - if all endpoints are degraded, then ATM allows routing. For more information, see [Controlling Azure App Service traffic with Azure Traffic Manager](../app-service/web-sites-traffic-manager.md).
172
+
>It's possible to use Traffic Manager (ATM) when failing over App Services behind private endpoints. Although the private endpoints are not reachable by Traffic Manager Probes - if all endpoints are degraded, then ATM allows routing. For more information, see [Controlling Azure App Service traffic with Azure Traffic Manager](../../../app-service/web-sites-traffic-manager.md).
173
173
174
174
## Validate
175
175
@@ -188,8 +188,8 @@ Once the relocation is completed, test and validate Azure App Service with the r
188
188
189
189
## Clean up
190
190
191
-
Delete the source app and App Service plan. [An App Service plan in the non-free tier carries a charge, even if no app is running in it.](../app-service/app-service-plan-manage.md#delete-an-app-service-plan)
191
+
Delete the source app and App Service plan. [An App Service plan in the non-free tier carries a charge, even if no app is running in it.](../../../app-service/app-service-plan-manage.md#delete-an-app-service-plan)
192
192
193
193
## Next steps
194
194
195
-
[Azure App Service App Cloning Using PowerShell](../app-service/app-service-web-app-cloning.md)
195
+
[Azure App Service App Cloning Using PowerShell](../../../app-service/app-service-web-app-cloning.md)
0 commit comments