Merge pull request #280364 from anaharris-ms/reloc-add-include

JamesJBarnett · web-flow · commit 83353cc4ae08 · 2024-07-10T15:37:26.000-07:00
Relocation: Cleanup work
diff --git a/articles/operational-excellence/relocation-app-gateway.md b/articles/operational-excellence/relocation-app-gateway.md
@@ -14,6 +14,8 @@ ms.custom:
 
 # Relocate Azure Application Gateway and Web Application Firewall (WAF) to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
  This article covers the recommended approach, guidelines, and practices to relocate Application Gateway and WAF between Azure regions. 
 
 >[!IMPORTANT]
diff --git a/articles/operational-excellence/relocation-automation.md b/articles/operational-excellence/relocation-automation.md
@@ -1,5 +1,5 @@
 ---
-title: Relocation guidance for Azure Automation
+title: Relocate Azure Automation to another region
 description: Learn how to relocate an Azure Automation to a another region
 author: anaharris-ms
 ms.author: anaharris
@@ -13,6 +13,9 @@ ms.custom:
 
 # Relocate Azure Automation to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
+
 This article covers relocation guidance for [Azure Automation](../automation/overview.md) across regions.
 
 If your Azure Automation instance doesn't have any configuration and the instance itself needs to be moved alone, you can choose to redeploy the NetApp File instance by using [Bicep, ARM Template, or Terraform](/azure/templates/microsoft.automation/automationaccounts?tabs=bicep&pivots=deployment-language-bicep).
diff --git a/articles/operational-excellence/relocation-cosmos-db.md b/articles/operational-excellence/relocation-cosmos-db.md
@@ -14,6 +14,8 @@ ms.reviewer: mjbrown
 
 # Relocate an Azure Cosmos DB NoSQL account to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 
 This article describes how to either:
 
diff --git a/articles/operational-excellence/relocation-event-grid-custom-topics.md b/articles/operational-excellence/relocation-event-grid-custom-topics.md
@@ -12,7 +12,11 @@ ms.custom:
 ---
 
 # Relocate Azure Event Grid custom topics to another region
-This article describes how to relocate your Azure Event Grid resources to another Azure region. You might relocate these resources for a number of reasons, such as to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. 
+
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
+
+This article describes how to relocate your Azure Event Grid resources to another Azure region. 
 
 The high-level steps are: 
 
diff --git a/articles/operational-excellence/relocation-event-grid-domains.md b/articles/operational-excellence/relocation-event-grid-domains.md
@@ -13,6 +13,9 @@ ms.custom:
 
 # Relocate Azure Event Grid domains to another region
 
+
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
  This article covers the recommended approach, guidelines, and practices to relocate Event Grid domains to another region. 
 
 
diff --git a/articles/operational-excellence/relocation-event-grid-system-topics.md b/articles/operational-excellence/relocation-event-grid-system-topics.md
@@ -12,7 +12,10 @@ ms.custom:
 ---
 
 # Relocate Azure Event Grid system topics to another region
-You might want to move your resources to another region for a number of reasons. For example, to take advantage of a new Azure region, to meet internal policy and governance requirements, or in response to capacity planning requirements. 
+
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
+This article covers the recommended approach, guidelines, and practices to relocate Event Grid system topics to another region. 
 
 Here are the high-level steps covered in this article: 
 
diff --git a/articles/operational-excellence/relocation-event-hub-cluster.md b/articles/operational-excellence/relocation-event-hub-cluster.md
@@ -14,11 +14,15 @@ ms.custom:
 
 # Relocate an Azure Event Hubs dedicated cluster to another region
 
+
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article shows you how to export an Azure Resource Manager template for an existing Event Hubs dedicated cluster and then use the template to create a cluster with same configuration settings in another region. 
 
 If you have other resources such as namespaces and event hubs in the Azure resource group that contains the Event Hubs cluster, you may want to export the template at the resource group level so that all related resources can be moved to the new region in one step. The steps in this article show you how to export an **Event Hubs cluster** to the template. The steps for exporting a **resource group** to the template are similar. 
 
 ## Prerequisites
+
 Ensure that the dedicated cluster can be created in the target region. The easiest way to find out is to use the Azure portal to try to [create an Event Hubs dedicated cluster](../event-hubs/event-hubs-dedicated-cluster-create-portal.md). You see the list of regions that are supported at that point of time for creating the cluster. 
 
 
diff --git a/articles/operational-excellence/relocation-event-hub.md b/articles/operational-excellence/relocation-event-hub.md
@@ -1,5 +1,5 @@
 ---
-title: Relocation guidance in Azure Event Hubs
+title: Relocate Azure Event Hubs to another region
 description: Learn how to relocate Azure Event Hubs to a another region
 author: anaharris-ms
 ms.author: anaharris
diff --git a/articles/operational-excellence/relocation-key-vault.md b/articles/operational-excellence/relocation-key-vault.md
@@ -14,6 +14,9 @@ ms.custom: subject-relocation, devx-track-azurepowershell
 
 # Relocate Azure Key Vault to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
+
 Azure Key Vault doesn't support key vault relocation to another region. 
 
 Instead of relocation, you need to:
diff --git a/articles/operational-excellence/relocation-log-analytics.md b/articles/operational-excellence/relocation-log-analytics.md
@@ -1,5 +1,5 @@
 ---
-title: Relocation guidance for Log Analytics workspace
+title: Relocate Log Analytics workspace to another region
 description: Learn how to relocate Log Analytics workspace to a new region.
 author: anaharris-ms
 ms.author: anaharris
@@ -14,6 +14,8 @@ ms.custom:
 
 # Relocate Azure Monitor - Log Analytics workspace to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 A relocation plan for Log Analytics workspace must include the relocation of any resources that log data with Log Analytics Workspace. 
 
 Log Analytics workspace doesn't natively support migrating workspace data from one region to another and associated devices.  Instead, you must create a new Log Analytics workspace in the target region and reconfigure the devices and settings in the new workspace. 
diff --git a/articles/operational-excellence/relocation-managed-identity.md b/articles/operational-excellence/relocation-managed-identity.md
@@ -14,7 +14,7 @@ ms.custom:
 
 # Relocate managed identities for Azure resources to another region
 
-There are situations in which you'd want to move your existing user-assigned managed identities from one region to another. For example, you may need to move a solution that uses user-assigned managed identities to another region. You may also want to move an existing identity to another region as part of disaster recovery planning, and testing.
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
 
 Moving user-assigned managed identities across Azure regions isn't supported.  You can however, recreate a user-assigned managed identity in the target region.
 
diff --git a/articles/operational-excellence/relocation-postgresql-flexible-server.md b/articles/operational-excellence/relocation-postgresql-flexible-server.md
@@ -13,6 +13,8 @@ ms.custom:
 
 # Relocate Azure Database for PostgreSQL to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article covers relocation guidance for Azure Database for PostgreSQL, Single Server, and Flexible Servers across geographies where region pairs aren't available for replication and geo-restore.
 
 To learn how to relocate Azure Cosmos DB for PostgreSQL (formerly called Azure Database for PostgreSQL - Hyperscale (Citus)), see [Read replicas in Azure Cosmos DB for PostgreSQL](/azure/cosmos-db/postgresql/concepts-read-replicas).
diff --git a/articles/operational-excellence/relocation-private-link.md b/articles/operational-excellence/relocation-private-link.md
@@ -13,6 +13,8 @@ ms.custom:
 
 # Relocate Azure Private Link Service to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article shows you how to relocate [Azure Private Link Service](/azure/private-link/private-link-overview) when moving your workload to another region. 
 
 To learn how to to reconfigure [private endpoints](/azure/private-link/private-link-overview) for a particular service, see the [appropriate service relocation guide](overview-relocation.md).
diff --git a/articles/operational-excellence/relocation-site-recovery.md b/articles/operational-excellence/relocation-site-recovery.md
@@ -14,6 +14,7 @@ ms.custom:
 # Relocate Azure Recovery Vault and Site Recovery to another region
 
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
 
 This article shows you how to relocate [Azure Recovery Vault and Site Recovery](../site-recovery/site-recovery-overview.md) when moving your workload to another region.
 
diff --git a/articles/operational-excellence/relocation-storage-account.md b/articles/operational-excellence/relocation-storage-account.md
@@ -13,6 +13,8 @@ ms.custom: subject-relocation, devx-track-azurepowershell
 
 # Relocate Azure Storage Account to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article shows you how to relocate an Azure Storage Account to a new region by creating a copy of your storage account into another region. You also learn how to relocate your data to that account by using AzCopy, or another tool of your choice.
 
 
diff --git a/articles/operational-excellence/relocation-virtual-network-nsg.md b/articles/operational-excellence/relocation-virtual-network-nsg.md
@@ -12,6 +12,8 @@ ms.custom: subject-relocation, devx-track-azurepowershell
 
 # Relocate Azure network security group (NSG) to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article shows you how to relocate an NSG to a new region by creating a copy of the source configuration and security rules of the NSG to another region.
 
 
diff --git a/articles/operational-excellence/relocation-virtual-network.md b/articles/operational-excellence/relocation-virtual-network.md
@@ -13,6 +13,8 @@ ms.custom: subject-relocation, devx-track-azurepowershell
 
 # Relocate Azure Virtual Network to another region
 
+[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)]
+
 This article shows you how to relocate a virtual network to a new region by redeploying the virtual network. Redeployment supports both independent relocation of multiple workloads and private IP address range change in the target region.  It's recommended that you use a Resource Manager template to relocate your virtual network. 
 
 However, can also choose to move your virtual network with Azure Resource Mover. However, if you choose to move your virtual network with Azure Resource Mover, make sure that you understand the following considerations:
