Merge pull request #260587 from ankitaduttaMSFT/mstopic

updated metadata

Author: v-ccolin

articles/site-recovery/azure-to-azure-about-networking.md

@@ -1,11 +1,10 @@
 ---
 title: About networking in Azure VM disaster recovery with Azure Site Recovery
 description: Provides an overview of networking for replication of Azure VMs using Azure Site Recovery.
-services: site-recovery
 author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
-ms.topic: article
+ms.topic: conceptual
 ms.date: 11/21/2021
 ms.author: ankitadutta
 ms.custom: engagement-fy23
@@ -41,7 +40,7 @@ Typically, networks are protected using firewalls and network security groups (N
 
 ## Outbound connectivity for URLs
 
-If you are using a URL-based firewall proxy to control outbound connectivity, allow these Site Recovery URLs:
+If you're using a URL-based firewall proxy to control outbound connectivity, allow these Site Recovery URLs:
 
 **URL** | **Details**
 --- | ---
@@ -50,13 +49,13 @@ login.microsoftonline.com | Required for authorization and authentication to the
 *.hypervrecoverymanager.windowsazure.com | Required so that the Site Recovery service communication can occur from the VM.
 *.servicebus.windows.net | Required so that the Site Recovery monitoring and diagnostics data can be written from the VM.
 *.vault.azure.net | Allows access to enable replication for ADE-enabled virtual machines via portal
-*.automation.ext.azure.com | Allows enabling auto-upgrade of mobility agent for a replicated item via portal
+*.automation.ext.azure.com | Allows enabling autoupgrade of mobility agent for a replicated item via portal
 
 ## Outbound connectivity using Service Tags
 
-Apart from controlling URLs, you can also use service tags to control connectivity. To do so, you will first need to create a [Network Security Group](../virtual-network/network-security-group-how-it-works.md) in Azure. Once created, you will need to use our existing service tags and create an NSG rule to allow access to Azure Site Recovery services. 
+Apart from controlling URLs, you can also use service tags to control connectivity. To do so, you must first create a [Network Security Group](../virtual-network/network-security-group-how-it-works.md) in Azure. Once created, you need to use our existing service tags and create an NSG rule to allow access to Azure Site Recovery services. 
 
-The advantages of using service tags to control connectivity, when compared to controlling connectivity using IP addresses, is that there will be no hard dependency on a particular IP address to stay connected to our services. In such a scenario, if the IP address of one of our services changes, then the ongoing replication will not be impacted for your machines. Whereas, a dependency on hard coded IP addresses will cause the replication status to become critical and put your systems at risk. Moreover, service tags ensures better security, stability and resiliency than hard coded IP addresses.
+The advantages of using service tags to control connectivity, when compared to controlling connectivity using IP addresses, is that there is no hard dependency on a particular IP address to stay connected to our services. In such a scenario, if the IP address of one of our services changes, then the ongoing replication is not impacted for your machines. Whereas, a dependency on hard coded IP addresses causes the replication status to become critical and put your systems at risk. Moreover, service tags ensure better security, stability and resiliency than hard coded IP addresses.
 
 While using NSG to control outbound connectivity, these service tags need to be allowed.
 
@@ -65,9 +64,9 @@ While using NSG to control outbound connectivity, these service tags need to be
     - Allow these addresses so that data can be written to the cache storage account, from the VM.
 - Create a [Microsoft Entra service tag](../virtual-network/network-security-groups-overview.md#service-tags) based NSG rule for allowing access to all IP addresses corresponding to Microsoft Entra ID
 - Create an EventsHub service tag-based NSG rule for the target region, allowing access to Site Recovery monitoring.
-- Create an AzureSiteRecovery service tag-based NSG rule for allowing access to Site Recovery service in any region.
+- Create an Azure Site Recovery service tag-based NSG rule for allowing access to Site Recovery service in any region.
 - Create an AzureKeyVault service tag-based NSG rule. This is required only for enabling replication of ADE-enabled virtual machines via portal.
-- Create a GuestAndHybridManagement service tag-based NSG rule. This is required only for enabling auto-upgrade of mobility agent for a replicated item via portal.
+- Create a GuestAndHybridManagement service tag-based NSG rule. This is required only for enabling autoupgrade of mobility agent for a replicated item via portal.
 - We recommend that you create the required NSG rules on a test NSG, and verify that there are no problems before you create the rules on a production NSG.
 
 ## Example NSG configuration
@@ -79,17 +78,17 @@ This example shows how to configure NSG rules for a VM to replicate.
 
 ### NSG rules - East US
 
-1. Create an outbound HTTPS (443) security rule for "Storage.EastUS" on the NSG as shown in the screenshot below.
+1. Create an outbound HTTPS (443) security rule for "Storage.EastUS" on the NSG as shown in the following screenshot:
 
       ![Screenshot shows Add outbound security rule for a network security group for Storage dot East U S.](./media/azure-to-azure-about-networking/storage-tag.png)
 
-2. Create an outbound HTTPS (443) security rule for "AzureActiveDirectory" on the NSG as shown in the screenshot below.
+2. Create an outbound HTTPS (443) security rule for "AzureActiveDirectory" on the NSG as shown in the following screenshot:
 
       ![Screenshot shows Add outbound security rule for a network security group for Microsoft Entra ID.](./media/azure-to-azure-about-networking/aad-tag.png)
 
-3. Similar to above security rules, create outbound HTTPS (443) security rule for "EventHub.CentralUS" on the NSG that corresponds to the target location. This allows access to Site Recovery monitoring.
+3. Similar to the security rules, create outbound HTTPS (443) security rule for "EventHub.CentralUS" on the NSG that corresponds to the target location. This allows access to Site Recovery monitoring.
 
-4. Create an outbound HTTPS (443) security rule for "AzureSiteRecovery" on the NSG. This allows access to Site Recovery Service in any region.
+4. Create an outbound HTTPS (443) security rule for "Azure Site Recovery" on the NSG. This allows access to Site Recovery Service in any region.
 
 ### NSG rules - Central US
 
@@ -99,16 +98,17 @@ These rules are required so that replication can be enabled from the target regi
 
 2. Create an outbound HTTPS (443) security rule for "AzureActiveDirectory" on the NSG.
 
-3. Similar to above security rules, create outbound HTTPS (443) security rule for "EventHub.EastUS" on the NSG that corresponds to the source location. This allows access to Site Recovery monitoring.
+3. Similar to the security rules, create outbound HTTPS (443) security rule for "EventHub.EastUS" on the NSG that corresponds to the source location. This allows access to Site Recovery monitoring.
 
-4. Create an outbound HTTPS (443) security rule for "AzureSiteRecovery" on the NSG. This allows access to Site Recovery Service in any region.
+4. Create an outbound HTTPS (443) security rule for "Azure Site Recovery" on the NSG. This allows access to Site Recovery Service in any region.
 
 ## Network virtual appliance configuration
 
-If you are using network virtual appliances (NVAs) to control outbound network traffic from VMs, the appliance might get throttled if all the replication traffic passes through the NVA. We recommend creating a network service endpoint in your virtual network for "Storage" so that the replication traffic does not go to the NVA.
+If you're using network virtual appliances (NVAs) to control outbound network traffic from VMs, the appliance might get throttled if all the replication traffic passes through the NVA. We recommend creating a network service endpoint in your virtual network for "Storage" so that the replication traffic doesn't go to the NVA.
 
 ### Create network service endpoint for Storage
-You can create a network service endpoint in your virtual network for "Storage" so that the replication traffic does not leave Azure boundary.
+
+You can create a network service endpoint in your virtual network for "Storage" so that the replication traffic doesn't leave Azure boundary.
 
 - Select your Azure virtual network and click on 'Service endpoints'
 
@@ -118,14 +118,15 @@ You can create a network service endpoint in your virtual network for "Storage"
 - Select 'Microsoft.Storage' under 'Service' and the required subnets under 'Subnets' field and click 'Add'
 
 >[!NOTE]
->If you are using firewall enabled cache storage account or target storage account, ensure you ['Allow trusted Microsoft services'](../storage/common/storage-network-security.md). Also, ensure that you allow access to at least one subnet of source Vnet.
+>If you're using firewall enabled cache storage account or target storage account, ensure you ['Allow trusted Microsoft services'](../storage/common/storage-network-security.md). Also, ensure that you allow access to at least one subnet of source Vnet.
 
 
 ### Forced tunneling
 
-You can override Azure's default system route for the 0.0.0.0/0 address prefix with a [custom route](../virtual-network/virtual-networks-udr-overview.md#custom-routes) and divert VM traffic to an on-premises network virtual appliance (NVA), but this configuration is not recommended for Site Recovery replication. If you're using custom routes, you should [create a virtual network service endpoint](azure-to-azure-about-networking.md#create-network-service-endpoint-for-storage) in your virtual network for "Storage" so that the replication traffic does not leave the Azure boundary.
+You can override Azure's default system route for the 0.0.0.0/0 address prefix with a [custom route](../virtual-network/virtual-networks-udr-overview.md#custom-routes) and divert VM traffic to an on-premises network virtual appliance (NVA), but this configuration isn't recommended for Site Recovery replication. If you're using custom routes, you should [create a virtual network service endpoint](azure-to-azure-about-networking.md#create-network-service-endpoint-for-storage) in your virtual network for "Storage" so that the replication traffic doesn't leave the Azure boundary.
 
 ## Next steps
+
 - Start protecting your workloads by [replicating Azure virtual machines](./azure-to-azure-quickstart.md).
 - Learn more about [IP address retention](site-recovery-retain-ip-azure-vm-failover.md) for Azure virtual machine failover.
 - Learn more about disaster recovery of [Azure virtual machines with ExpressRoute](azure-vm-disaster-recovery-with-expressroute.md).

articles/site-recovery/azure-to-azure-autoupdate.md

@@ -1,11 +1,10 @@
 ---
 title: Automatic update of the Mobility service in Azure Site Recovery
 description: Overview of automatic update of the Mobility service when replicating Azure VMs by using Azure Site Recovery.
-services: site-recovery
 author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 03/24/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23

articles/site-recovery/azure-to-azure-customize-networking.md

@@ -1,11 +1,10 @@
 ---
 title: Customize networking configurations for a failover VM  | Microsoft Docs
 description: Provides an overview of customize networking configurations for a failover VM in the replication of Azure VMs using Azure Site Recovery.
-services: site-recovery
 author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
-ms.topic: article
+ms.topic: tutorial
 ms.date: 03/27/2023
 ms.author: ankitadutta
 ms.custom: engagement-fy23

articles/site-recovery/azure-to-azure-enable-global-disaster-recovery.md

@@ -3,7 +3,7 @@ title: Enable disaster recovery across Azure regions across the globe
 description: This article describes the global disaster recovery feature in Azure Site Recovery.
 manager: evansma
 ms.service: site-recovery
-ms.topic: article
+ms.topic: tutorial
 ms.date: 08/09/2021
 ms.author: ankitadutta
 author: ankitaduttaMSFT

articles/site-recovery/azure-to-azure-how-to-enable-replication-ade-vms.md

@@ -4,7 +4,7 @@ description: This article describes how to configure replication for Azure Disk
 author: ankitaduttaMSFT
 manager: gaggupta
 ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 10/19/2022
 ms.author: ankitadutta
 

articles/site-recovery/azure-to-azure-how-to-enable-replication-cmk-disks.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.custom: devx-track-azurepowershell
-ms.topic: article
+ms.topic: how-to
 ms.date: 10/09/2023
 ms.author: ankitadutta
 ---

articles/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md

@@ -4,7 +4,7 @@ description: This article describes how to configure replication for VMs with pr
 author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.service: site-recovery
-ms.topic: article
+ms.topic: how-to
 ms.date: 04/23/2022
 ms.custom: references_regions, subject-rbac-steps, engagement-fy23
 ---

articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md

@@ -4,7 +4,7 @@ description: This article describes when and how to use zone-to-zone disaster re
 author: ankitaduttaMSFT
 manager: aravindang
 ms.service: site-recovery
-ms.topic: article
+ms.topic: tutorial
 ms.date: 10/09/2023
 ms.author: ankitadutta
 ms.custom: references_regions

articles/site-recovery/azure-to-azure-how-to-reprotect.md

@@ -3,9 +3,8 @@ title: Reprotect Azure VMs to the primary region with Azure Site Recovery
 description: Describes how to reprotect Azure VMs after failover, the secondary to primary region, using Azure Site Recovery.
 services: site-recovery
 author: ankitaduttaMSFT
-manager: jsuri
 ms.service: site-recovery
-ms.topic: article
+ms.topic: tutorial
 ms.date: 07/14/2023
 ms.author: ankitadutta
 ---

articles/site-recovery/azure-to-azure-powershell.md

@@ -1,10 +1,10 @@
 ---
 title: Disaster recovery for Azure VMs using Azure PowerShell and Azure Site Recovery
 description: Learn how to set up disaster recovery for Azure virtual machines with Azure Site Recovery using Azure PowerShell.
-services: site-recovery
+ms.service: site-recovery
 author: ankitaduttaMSFT
 manager: rochakm
-ms.topic: article
+ms.topic: how-to
 ms.date: 07/14/2023
 ms.author: ankitadutta 
 ms.custom: devx-track-azurepowershell