Skip to content

Commit 1b9f050

Browse files
mumianmumian
committed
fix broken links and add redirects
1 parent 844fd64 commit 1b9f050

11 files changed

+232
-141
lines changed

‎articles/azure-cache-for-redis/cache-moving-resources.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,9 @@
11
---
22
title: Move Azure Cache for Redis instances to different regions
33
description: How to move Azure Cache for Redis instances to a different Azure region.
4-
5-
6-
7-
84
ms.topic: how-to
95
ms.custom: subject-moving-resources, engagement-fy23
106
ms.date: 10/20/2022
11-
127
---
138

149
# Move Azure Cache for Redis instances to different regions
@@ -117,9 +112,9 @@ Once your new cache in the targeted region is populated with all necessary data,
117112

118113
When the unlinking process completes, the secondary cache is available for both reads and writes.
119114

120-
>[!NOTE]
121-
>When the geo-replication link is removed, the replicated data from the primary linked cache remains in the secondary cache.
122-
>
115+
>[!NOTE]
116+
>When the geo-replication link is removed, the replicated data from the primary linked cache remains in the secondary cache.
117+
>
123118
124119
1. Delete the original instance.
125120

‎articles/azure-resource-manager/management/relocation/includes/app-service-certificates.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
ms.service: app-service
32
ms.topic: include
43
ms.date: 08/12/2024
54
---
@@ -11,9 +10,8 @@ App Service certificate resources can be moved to a new resource group or subscr
1110
There are different types of certificates that need to be taken into consideration as you plan your service relocation:
1211

1312
| Certificate type | Exportable | Comments |
14-
| ----- | ----- | ----- |
13+
| ----- | ----- | ----- |
1514
| [App Service managed](/azure/app-service/configure-ssl-certificate#import-an-app-service-certificate) | No | Recreate these certificates in the new region. |
1615
| [Azure Key Vault managed](/azure/app-service/configure-ssl-certificate#import-a-certificate-from-key-vault) | Yes | These certificates can be [exported from Key Vault](/azure/key-vault/certificates/how-to-export-certificate) and then [imported into Key Vault](/azure/key-vault/certificates/tutorial-import-certificate) in the new region. |
17-
| Private key (self-managed) | Yes | Certificates you acquired outside of Azure can be exported from App Service and then imported either into the new app or [into Key Vault](/azure/key-vault/certificates/tutorial-import-certificate) in the new region. |
16+
| Private key (self-managed) | Yes | Certificates you acquired outside of Azure can be exported from App Service and then imported either into the new app or [into Key Vault](/azure/key-vault/certificates/tutorial-import-certificate) in the new region. |
1817
| Public key | No | Your app might have certificates with only a public key and no secret, which are used to access other secured endpoints. Obtain the required public key certificate files and import them into the app in the new region. |
19-

‎articles/azure-resource-manager/management/relocation/includes/app-service-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
ms.service: app-service
32
ms.topic: include
43
ms.date: 08/12/2024
54
---
@@ -10,4 +9,5 @@ ms.date: 08/12/2024
109

1110
- Existing [Key Vault references](/azure/app-service/app-service-key-vault-references) can't be exported across an Azure geographical boundary. You must recreate any required references in the new region.
1211

13-
- Your app configuration might be managed by [Azure App Configuration](/azure/azure-app-configuration/overview) or from some other central (downstream) database dependency. Review any App Configuration store or similar stores for environment and region-specific settings that might require modifications.
12+
- Your app configuration might be managed by [Azure App Configuration](/azure/azure-app-configuration/overview) or from some other central (downstream) database dependency. Review any App Configuration store or similar stores for environment and region-specific settings that might require modifications.
13+

‎articles/azure-resource-manager/management/relocation/includes/app-service-identities.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
ms.service: app-service
32
ms.topic: include
43
ms.date: 08/12/2024
54
---
@@ -8,6 +7,7 @@ ms.date: 08/12/2024
87

98
- You need to recreate any system assigned managed identities along with your app in the new target region. Typically, an automatically created Microsoft Entra ID app, used by EasyAuth, defaults to the app resource name.
109

11-
- User-assigned managed identities also can't be moved across regions. To keep user-assigned managed identities in the same resource group with your app, you must recreate them in the new region. For more information, see [Relocate managed identities for Azure resources to another region](../relocation-managed-identity.md).
10+
- User-assigned managed identities also can't be moved across regions. To keep user-assigned managed identities in the same resource group with your app, you must recreate them in the new region. For more information, see [Relocate managed identities for Azure resources to another region](/entra/identity/managed-identities-azure-resources/how-to-managed-identity-regional-move).
11+
12+
- Grant the managed identities the same permissions in your relocated services as the original identities that they're replacing, including Group memberships.
1213

13-
- Grant the managed identities the same permissions in your relocated services as the original identities that they're replacing, including Group memberships.

‎articles/azure-resource-manager/management/relocation/includes/private-endpoint-include.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
---
2-
ms.service: azure-container-registry
32
ms.topic: include
43
ms.date: 07/29/2024
54
---
@@ -22,4 +21,4 @@ You can use the following options to configure your DNS settings for private end
2221

2322
- **Use the host file (only recommended for testing)**. You can use the host file on a virtual machine to override the DNS.
2423
- **Use a private DNS zone.** You can use private DNS zones to override the DNS resolution for a private endpoint. A private DNS zone can be linked to your virtual network to resolve specific domains.
25-
- **Use your DNS forwarder (optional).** You can use your DNS forwarder to override the DNS resolution for a private link resource. Create a DNS forwarding rule to use a private DNS zone on your DNS server hosted in a virtual network.
24+
- **Use your DNS forwarder (optional).** You can use your DNS forwarder to override the DNS resolution for a private link resource. Create a DNS forwarding rule to use a private DNS zone on your DNS server hosted in a virtual network.

‎articles/azure-resource-manager/management/relocation/includes/service-relocation-reason-include.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
title: include file
33
description: include file
4-
ms.service: azure
54
ms.topic: include
65
ms.date: 06/25/2024
76
ms.custom: include file
@@ -14,4 +13,4 @@ There are various reasons why you may want to move your existing Azure resources
1413
- Deploy features or services available in specific regions only.
1514
- Meet internal policy and governance requirements.
1615
- Align with company mergers and acquisitions
17-
- Meet capacity planning requirements.
16+
- Meet capacity planning requirements.

‎articles/azure-resource-manager/management/relocation/relocation-container-registry.md

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -75,28 +75,28 @@ Inspect the registry properties in the template JSON file you downloaded, and ma
7575
- Change the registry name's `defaultValue` to the desired name of the target registry
7676
- Update the `location` to the desired Azure region for the target registry
7777
78-
```json
79-
{
80-
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
81-
"contentVersion": "1.0.0.0",
82-
"parameters": {
83-
"registries_myregistry_name": {
84-
"defaultValue": "myregistry",
85-
"type": "String"
86-
}
87-
},
88-
"variables": {},
89-
"resources": [
78+
```json
9079
{
91-
"type": "Microsoft.ContainerRegistry/registries",
92-
"apiVersion": "2020-11-01-preview",
93-
"name": "[parameters('myregistry_name')]",
94-
"location": "centralus",
95-
...
80+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
81+
"contentVersion": "1.0.0.0",
82+
"parameters": {
83+
"registries_myregistry_name": {
84+
"defaultValue": "myregistry",
85+
"type": "String"
86+
}
87+
},
88+
"variables": {},
89+
"resources": [
90+
{
91+
"type": "Microsoft.ContainerRegistry/registries",
92+
"apiVersion": "2020-11-01-preview",
93+
"name": "[parameters('myregistry_name')]",
94+
"location": "centralus",
95+
...
96+
}
97+
]
9698
}
97-
]
98-
}
99-
```
99+
```
100100
101101
- Validate all the associated resources detail in the downloaded template such as Registry scopeMaps, replications configuration, Diagnostic settings like log analytics.
102102
@@ -155,9 +155,9 @@ done
155155
1. Associate the dependent resources to the target Azure Container Registry such as log analytics workspace in Diagnostic settings.
156156
1. Configure Azure Container Registry integration with both type of AKS clusters, provisioned or yet to be provisioned by running the following command:
157157

158-
```azurecli
159-
Set-AzAksCluster -Name myAKSCluster -ResourceGroupName myResourceGroup -AcrNameToAttach <acr-name>
160-
```
158+
```azurecli
159+
Set-AzAksCluster -Name myAKSCluster -ResourceGroupName myResourceGroup -AcrNameToAttach <acr-name>
160+
```
161161
162162
1. Make the necessary changes to the Kubernetes manifest file to integrate same with relocated Azure Container Registry (ACR).
163163
1. Update development and deployment systems to use the target registry instead of the source registry.

‎articles/azure-resource-manager/management/relocation/relocation-event-hub.md

Lines changed: 74 additions & 74 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Modify the template by changing the Event Hubs namespace name and region.
7676
1. Select **Load file**, and then follow the instructions to load the **template.json** file that you downloaded in the last section.
7777
1. In the **template.json** file, name the Event Hubs namespace by setting the default value of the namespace name. This example sets the default value of the Event Hubs namespace name to `namespace-name`.
7878

79-
```json
79+
```json
8080
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
8181
"contentVersion": "1.0.0.0",
8282
"parameters": {
@@ -85,86 +85,86 @@ Modify the template by changing the Event Hubs namespace name and region.
8585
"type": "String"
8686
},
8787
},
88-
```
88+
```
8989

9090
1. Edit the **location** property in the **template.json** file to the target region. This example sets the target region to `centralus`.
9191

92-
```json
93-
"resources": [
94-
{
95-
"type": "Microsoft.KeyVault/vaults",
96-
"apiVersion": "2023-07-01",
97-
"name": "[parameters('vaults_name')]",
98-
"location": "centralus",
99-
},
100-
{
101-
"type": "Microsoft.EventHub/namespaces",
102-
"apiVersion": "2023-01-01-preview",
103-
"name": "[parameters('namespaces_name')]",
104-
"location": "centralus",
105-
},
106-
{
107-
"type": "Microsoft.EventHub/namespaces/authorizationrules",
108-
"apiVersion": "2023-01-01-preview",
109-
"name": "[concat(parameters('namespaces_name'), '/RootManageSharedAccessKey')]",
110-
"location": "centralus",
111-
"dependsOn": [
112-
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_name'))]"
113-
],
114-
"properties": {
115-
"rights": [
116-
"Listen",
117-
"Manage",
118-
"Send"
119-
]
120-
}
121-
},
122-
{
123-
"type": "Microsoft.EventHub/namespaces/networkrulesets",
124-
"apiVersion": "2023-01-01-preview",
125-
"name": "[concat(parameters('namespaces_name'), '/default')]",
126-
"location": "centralus",
127-
"dependsOn": [
128-
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_name'))]"
129-
],
130-
"properties": {
131-
"publicNetworkAccess": "Enabled",
132-
"defaultAction": "Deny",
133-
"virtualNetworkRules": [
134-
{
135-
"subnet": {
136-
"id": "[concat(parameters('virtualNetworks_vnet_akv_externalid'), '/subnets/default')]"
137-
},
138-
"ignoreMissingVnetServiceEndpoint": false
139-
}
92+
```json
93+
"resources": [
94+
{
95+
"type": "Microsoft.KeyVault/vaults",
96+
"apiVersion": "2023-07-01",
97+
"name": "[parameters('vaults_name')]",
98+
"location": "centralus",
99+
},
100+
{
101+
"type": "Microsoft.EventHub/namespaces",
102+
"apiVersion": "2023-01-01-preview",
103+
"name": "[parameters('namespaces_name')]",
104+
"location": "centralus",
105+
},
106+
{
107+
"type": "Microsoft.EventHub/namespaces/authorizationrules",
108+
"apiVersion": "2023-01-01-preview",
109+
"name": "[concat(parameters('namespaces_name'), '/RootManageSharedAccessKey')]",
110+
"location": "centralus",
111+
"dependsOn": [
112+
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_name'))]"
140113
],
141-
"ipRules": [],
142-
"trustedServiceAccessEnabled": false
143-
}
144-
},
145-
{
146-
"type": "Microsoft.EventHub/namespaces/privateEndpointConnections",
147-
"apiVersion": "2023-01-01-preview",
148-
"name": "[concat(parameters('namespaces_peterheesbus_name'), '/81263915-15d5-4f14-8d65-25866d745a66')]",
149-
"location": "centralus",
150-
"dependsOn": [
151-
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_peterheesbus_name'))]"
152-
],
153-
"properties": {
154-
"provisioningState": "Succeeded",
155-
"privateEndpoint": {
156-
"id": "[parameters('privateEndpoints_pvs_eventhub_externalid')]"
157-
},
158-
"privateLinkServiceConnectionState": {
159-
"status": "Approved",
160-
"description": "Auto-Approved"
114+
"properties": {
115+
"rights": [
116+
"Listen",
117+
"Manage",
118+
"Send"
119+
]
120+
}
121+
},
122+
{
123+
"type": "Microsoft.EventHub/namespaces/networkrulesets",
124+
"apiVersion": "2023-01-01-preview",
125+
"name": "[concat(parameters('namespaces_name'), '/default')]",
126+
"location": "centralus",
127+
"dependsOn": [
128+
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_name'))]"
129+
],
130+
"properties": {
131+
"publicNetworkAccess": "Enabled",
132+
"defaultAction": "Deny",
133+
"virtualNetworkRules": [
134+
{
135+
"subnet": {
136+
"id": "[concat(parameters('virtualNetworks_vnet_akv_externalid'), '/subnets/default')]"
137+
},
138+
"ignoreMissingVnetServiceEndpoint": false
139+
}
140+
],
141+
"ipRules": [],
142+
"trustedServiceAccessEnabled": false
143+
}
144+
},
145+
{
146+
"type": "Microsoft.EventHub/namespaces/privateEndpointConnections",
147+
"apiVersion": "2023-01-01-preview",
148+
"name": "[concat(parameters('namespaces_peterheesbus_name'), '/81263915-15d5-4f14-8d65-25866d745a66')]",
149+
"location": "centralus",
150+
"dependsOn": [
151+
"[resourceId('Microsoft.EventHub/namespaces', parameters('namespaces_peterheesbus_name'))]"
152+
],
153+
"properties": {
154+
"provisioningState": "Succeeded",
155+
"privateEndpoint": {
156+
"id": "[parameters('privateEndpoints_pvs_eventhub_externalid')]"
157+
},
158+
"privateLinkServiceConnectionState": {
159+
"status": "Approved",
160+
"description": "Auto-Approved"
161+
}
161162
}
162163
}
163-
}
164-
]
165-
```
164+
]
165+
```
166166

167-
To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
167+
To obtain region location codes, see [Azure Locations](https://azure.microsoft.com/global-infrastructure/locations/). The code for a region is the region name with no spaces, **Central US** = **centralus**.
168168

169169
1. Remove resources of type private endpoint in the template.
170170

‎articles/azure-resource-manager/management/relocation/relocation-firewall.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ This article shows you how to relocate an Azure Firewall that protects an Azure
3131
- If you're using the TLS Inspection feature of Azure Firewall Premium tier, the following dependencies also need to be deployed in the target region:
3232

3333
- [Azure Key Vault](./relocation-key-vault.md)
34-
- [Azure Managed Identity](./relocation-managed-identity.md)
34+
- [Azure Managed Identity](/entra/identity/managed-identities-azure-resources/how-to-managed-identity-regional-move)
3535

3636
## Downtime
3737

@@ -97,8 +97,9 @@ If you're running classic firewall rules without Firewall policy, migrate to Fir
9797
1. Sign in to the [Azure portal](https://portal.azure.com).
9898

9999
1. If you're using Premium SKU with TLS Inspection enabled,
100+
100101
1. [Relocate the key vault](./relocation-key-vault.md) that's used for TLS inspection into the new target region. Then, follow [the procedures](../../../application-gateway/key-vault-certs.md) to move certificates or generate new certificates for TLS inspection into the new key vault in the target region.
101-
1. [Relocate managed identity](./relocation-managed-identity.md) into the new target region. Reassign the corresponding roles for the key vault in the target region and subscription.
102+
1. [Relocate managed identity](/entra/identity/managed-identities-azure-resources/how-to-managed-identity-regional-move) into the new target region. Reassign the corresponding roles for the key vault in the target region and subscription.
102103

103104
1. In the Azure portal, select **Create a resource**.
104105

@@ -150,7 +151,7 @@ To find the location code for your target region, see [Data residency in Azure](
150151

151152
1. If you're using Premium SKU with TLS Inspection enabled,
152153
1. [Relocate the key vault](./relocation-key-vault.md) used for TLS inspection into the new target region and follow the procedures to move certificates or generate new certificates for TLS inspection in the new key vault in the target region.
153-
1. [Relocate managed identity](./relocation-managed-identity.md) into the new target region and reassign the corresponding roles for the key vault in the target region and subscription.
154+
1. [Relocate managed identity](/entra/identity/managed-identities-azure-resources/how-to-managed-identity-regional-move) into the new target region and reassign the corresponding roles for the key vault in the target region and subscription.
154155

155156
1. In the `template.json` file, replace:
156157
- `firewallName` with the default value of your Azure Firewall name.

0 commit comments

Comments
 (0)