roll back some changes so the PR can be merged

Author: mumian

articles/automation/how-to/move-account.md

@@ -130,5 +130,7 @@ When the move is complete, verify that the capabilities listed below are enabled
 
 ## Next steps
 
-- 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).
-- To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
+
+To learn how to move Automation to a new region, see [Move Automation account to another region](../../operational-excellence/relocation-automation.md).
+
+To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).

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

@@ -1,6 +1,10 @@
 ---
 title: Move Azure Cache for Redis instances to different regions
 description: How to move Azure Cache for Redis instances to a different Azure region.
+
+
+
+
 ms.topic: how-to
 ms.custom: subject-moving-resources, engagement-fy23
 ms.date: 10/20/2022
@@ -115,9 +119,9 @@ Once your new cache in the targeted region is populated with all necessary data,
 
     When the unlinking process completes, the secondary cache is available for both reads and writes.
 
-    >[!NOTE]
-    >When the geo-replication link is removed, the replicated data from the primary linked cache remains in the secondary cache.
-    >
+>[!NOTE]
+>When the geo-replication link is removed, the replicated data from the primary linked cache remains in the secondary cache.
+>
 
 1. Delete the original instance.
 
@@ -237,4 +241,4 @@ Learn more about Azure Cache for Redis features.
 
 - [Geo-replication FAQ](cache-how-to-geo-replication.md#geo-replication-faq)
 - [Azure Cache for Redis service tiers](cache-overview.md#service-tiers)
-- [High availability for Azure Cache for Redis](cache-high-availability.md)
+- [High availability for Azure Cache for Redis](cache-high-availability.md)

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

@@ -73,30 +73,30 @@ This section is a planning checklist in the following areas:
 
 Some further points to consider:
 
-- App Assigned Addresses, where an App Service app’s SSL connection is bound to a specific app designated IP, can be used for allow-listing calls from third party networks into App Service. For example, a network / IT admin may want to lock down outbound calls from an on-premises network or virtual network to use a static, well-known address. As such, if the App Assigned Address feature is in use, upstream firewall rules - such as internal, external, or third parties -  for the callers into the app should be checked and informed of the new address. Firewall rules can be internal, external, or third parties, such as partners or well-known customers.
+- App Assigned Addresses, where an App Service app's SSL connection is bound to a specific app designated IP, can be used for allow-listing calls from third party networks into App Service. For example, a network / IT admin may want to lock down outbound calls from an on-premises network or virtual network to use a static, well-known address. As such, if the App Assigned Address feature is in use, upstream firewall rules - such as internal, external, or third parties -  for the callers into the app should be checked and informed of the new address. Firewall rules can be internal, external, or third parties, such as partners or well-known customers.
 - Consider any upstream Network Virtual Appliance (NVA) or Reverse Proxy. The NVA config may need to change if you're rewriting the host header or and/or SSL terminating.
 
 > [!NOTE]
 > App Service Environment is the only App Service offering allows downstream calls to downstream application dependencies over SSL, where the SSL relies on self-signed/PKI with built with [nonstandard Root CA certificates](/azure/app-service/environment/overview-certificates#private-client-certificate). The multitenant service doesn't provide access for customers to upload to the trusted certificate store.
 >
-> App Service Environment today doesn't allow SSL certificate purchase, only Bring Your Own certificates. IP-SSL isn't possible (and doesn’t make sense), but SNI is. Internal App Service Environment wouldn't be associated with a public domain and therefore the SSL certs used must be provided by the customer and are therefore transportable, for example certs for internal use generated using PKI. App Service Environment v3 in external mode shares the same features as the regular multitenant App Service.
+> App Service Environment today doesn't allow SSL certificate purchase, only Bring Your Own certificates. IP-SSL isn't possible (and doesn't make sense), but SNI is. Internal App Service Environment wouldn't be associated with a public domain and therefore the SSL certs used must be provided by the customer and are therefore transportable, for example certs for internal use generated using PKI. App Service Environment v3 in external mode shares the same features as the regular multitenant App Service.
 
 [!INCLUDE [app-service-configuration](includes/app-service-configuration.md)]
 
 - Make sure to check any disk file configuration, which may or may not be overridden by application settings.
 
-### VNet Connectivity / Custom Names / DNS
+### Virtual network Connectivity / Custom Names / DNS
 
-- App Service Environment is a VNet-Injected single tenant service. App Service Environment networking differs from the multitenant App Service,  which requires one or both “Private Endpoints” or “Regional VNet integration”. Other options that may be in play include the legacy P2S VPN based VNet integration and Hybrid Connections (an Azure Relay service).
+- App Service Environment is a VNet-Injected single tenant service. App Service Environment networking differs from the multitenant App Service,  which requires one or both "Private Endpoints" or "Regional VNet integration". Other options that may be in play include the legacy P2S VPN based VNet integration and Hybrid Connections (an Azure Relay service).
 
   > [!NOTE]
   > ASEv3 Networking is simplified - the Azure Management traffic and the App Service Environments own downstream dependencies aren't visible to the customer Virtual Network, greatly simplifying the configuration required where the customer is using a force-tunnel for all traffic, or sending a subset of outbound traffic, through a Network Virtual Appliance/Firewall.
   >
-  > Hybrid Connections (Azure Relay) are regional. If Hybrid Connections are used and although an Azure Relay Namespace can be moved to another region, it would be simpler to redeploy the Hybrid Connection (ensure the Hybrid connection is setup in the new region on deploy of the target resources) and relink it to the Hybrid Connection Manager. The Hybrid Connection Manager location should be carefully considered.
+  > Hybrid Connections (Azure Relay) are regional. If you're using Hybrid Connections, it's often simpler to redeploy them rather than move the Azure Relay Namespace to another region—even though moving is possible. Ensure the Hybrid Connection is configured in the new region when deploying the target resources, and relink it to the Hybrid Connection Manager. Be sure to carefully consider the location of the Hybrid Connection Manager.
 
 - **Follow the strategy for a warm standby region.** Ensure that core networking and connectivity, Hub network, domain controllers, DNS, VPN or Express Route, etc., are present and tested prior to the resource relocation.
 - **Validate any upstream or downstream network ACLs and configuration**. For example, consider an external downstream service that allowlists only your App traffic. A relocation to a new Application Plan for a multitenant App Service would then also be a change in outbound IP addresses.
-- In most cases, it's best to **ensure that the target region VNets have unique address space**. A unique address space facilitates virtual network connectivity if it’s required, for example, to replicate data. Therefore, in these scenarios there's an implicit requirement to change:
+- In most cases, it's best to **ensure that the target region VNets have unique address space**. A unique address space facilitates virtual network connectivity if it's required, for example, to replicate data. Therefore, in these scenarios there's an implicit requirement to change:
 
   - Private DNS
   - Any hard coded or external configuration that references resources by IP address (without a hostname)
@@ -127,7 +127,7 @@ Some further points to consider:
 
 The virtual network service endpoints for Azure App Service  restrict access to a specified virtual network. The endpoints can also restrict access to a list of IPv4 (internet protocol version 4) address ranges. Any user connecting to the Event Hubs from outside those sources is denied access. If Service endpoints were configured in the source region for the Event Hubs resource, the same would need to be done in the target one.
 
-For a successful recreation of the Azure App Service  to the target region, the virtual network and subnet must be created beforehand. In case the move of these two resources is being carried out with the Azure Resource Mover tool, the service endpoints won’t be configured automatically. Hence, they need to be configured manually, which can be done through the [Azure portal](/azure/key-vault/general/quick-create-portal), the [Azure CLI](/azure/key-vault/general/quick-create-cli), or [Azure PowerShell](/azure/key-vault/general/quick-create-powershell).
+For a successful recreation of the Azure App Service  to the target region, the virtual network and subnet must be created beforehand. In case the move of these two resources is being carried out with the Azure Resource Mover tool, the service endpoints won't be configured automatically. Hence, they need to be configured manually, which can be done through the [Azure portal](/azure/key-vault/general/quick-create-portal), the [Azure CLI](/azure/key-vault/general/quick-create-cli), or [Azure PowerShell](/azure/key-vault/general/quick-create-powershell).
 
 ## Relocate
 
@@ -152,7 +152,7 @@ Keep in mind that for App Service Environment (Isolated) tiers, you need to rede
 
 Use IaC when an existing Continuous Integration and Continuous Delivery/Deployment(CI/CD) pipeline exists, or can be created. With an CI/CD pipeline in place, your App Service resource can be created in the target region with a deployment action or a Kudu zip deployment.
 
-SLA requirements should determine how much additional effort is required. For example: Is this a redeploy with limited downtime, or is it a near real time cut-over required with minimal to no downtime?
+The SLA requirements should determine how much additional effort is required. For example: Is this a redeployment with limited downtime, or does it require a near real-time cutover with minimal to no downtime?
 
 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.
 
@@ -168,8 +168,8 @@ Once the relocation is completed, test and validate Azure App Service with the r
 - Perform integration testing on the target region deployment, including all formal regression testing. Integration testing should align with the usual Rhythm of Business deployment and test processes applicable to the workload.
 - In some scenarios, particularly where the relocation includes updates, changes to the applications or Azure Resources, or a change in usage profile, use load testing to validate that the new workload is fit for purpose. Load testing is also an opportunity to validate operations and monitoring coverage. For example, use load testing to validate that the required infrastructure and application logs are being generated correctly. Load tests should be measured against established workload performance baselines.
 
->[!TIP]
->An App Service relocation is also an opportunity to reassess Availability and Disaster Recovery planning. App Service and App Service Environment (App Service Environment v3) supports [availability zones](/azure/reliability/availability-zones-overview) and it's recommended that configure with an availability zone configuration. Keep in mind the prerequisites for deployment, pricing, and limitations and factor these into the resource move planning. For more information on availability zones and App Service, see [Reliability in Azure App Service](/azure/reliability/reliability-app-service).
+> [!TIP]
+> An App Service relocation is also an opportunity to reassess availability and disaster recovery planning. App Service and App Service Environment (App Service Environment v3) support [availability zones](/azure/reliability/availability-zones-overview) and it's recommended that configure with an availability zone configuration. Keep in mind the prerequisites for deployment, pricing, and limitations and factor these into the resource move planning. For more information on availability zones and App Service, see [Reliability in Azure App Service](/azure/reliability/reliability-app-service).
 
 ## Clean up
 

articles/azure-resource-manager/management/relocation/relocation-automation.md

@@ -1,6 +1,6 @@
 ---
 title: Relocate Azure Automation to another region
-description: Learn how to relocate an Azure Automation to a another region
+description: Learn how to relocate an Azure Automation to another region
 ms.date: 01/19/2024
 ms.topic: how-to
 ms.custom: subject-relocation
@@ -19,7 +19,7 @@ If your Azure Automation instance doesn't have any configuration and the instanc
 - Identify all Automation dependant resources.
 - If the system-assigned managed identity isn't being used at source, you must map user-assigned managed identity at the target.
 - If the target Azure Automation needs to be enabled for private access, associate with Virtual Network for private endpoint.
-- If the source Azure Automation is enabled with a private connection, create a private link and configure the private link with DNS at target.
+- If the source Azure Automation is enabled with a private connection, create a private link and configure the private link with Domain Name System (DNS) at target.
 - For Azure Automation to communicate with Hybrid RunBook Worker, Azure Update Manager, Change Tracking, Inventory Configuration, and Automation State Configuration, you must enable port 443 for both inbound and outbound internet access.
 
 ## Downtime
@@ -40,20 +40,16 @@ To get started, export a Resource Manager template. This template contains setti
 
 ## Redeploy
 
-In the diagram below, the red flow lines illustrate redeployment of the target instance along with configuration movement.
+In the following diagram, the red flow lines illustrate redeployment of the target instance along with configuration movement.
 
 :::image type="content" source="media/automation/automation-pattern-design.png" alt-text="Diagram illustrating cold standby redeployment with configuration movement.":::
 
 **To deploy the template to create an Automation instance in the target region:**
 
 1. Reconfigure the template parameters for the target.
-
-1. Deploy the template using [ARM](/azure/automation/quickstart-create-automation-account-template), [Portal](/azure/automation/automation-create-standalone-account?tabs=azureportal)  or [PowerShell](/powershell/module/az.automation/import-azautomationrunbook?view=azps-11.2.0&preserve-view=true).
-
+1. Deploy the template using [Azure Resource Manager](/azure/automation/quickstart-create-automation-account-template), [Azure portal](/azure/automation/automation-create-standalone-account?tabs=azureportal), or [Azure PowerShell](/powershell/module/az.automation/import-azautomationrunbook?view=azps-11.2.0&preserve-view=true).
 1. Use PowerShell to export all associated runbooks from the source Azure Automation instance and import them to the target instance. Reconfigure the properties as per target. For more information, see [Export-AzAutomationRunbook](/powershell/module/az.automation/export-azautomationrunbook?view=azps-11.2.0&viewFallbackFrom=azps-9.4.0&preserve-view=true).
-
 1. Associate the relocated Azure Automation instance to the target Log Analytics workspace.
-
 1. Configure the target virtual machines with desired state configuration from the relocated Azure Automation instance as per source.
 
 ## Next steps