Merge pull request #286926 from ankitaduttaMSFT/incub3

JamesJBarnett · web-flow · commit a0cbd62acee7 · 2024-09-23T12:07:48.000-07:00
incubation set 3
diff --git a/articles/resource-mover/support-matrix-move-region-sql.md b/articles/resource-mover/support-matrix-move-region-sql.md
@@ -3,8 +3,8 @@ title: Support for moving Azure SQL resources between regions with Azure Resourc
 description: Review support for moving Azure SQL resources between regions with Azure Resource Mover.
 author: ankitaduttaMSFT
 ms.service: azure-resource-mover
-ms.topic: conceptual
-ms.date: 03/29/2024
+ms.topic: concept-article
+ms.date: 09/18/2024
 ms.author: ankitadutta
 ms.custom: UpdateFrequency.5
 ---
diff --git a/articles/site-recovery/concepts-azure-to-azure-high-churn-support.md b/articles/site-recovery/concepts-azure-to-azure-high-churn-support.md
@@ -1,11 +1,10 @@
 ---
 title: Azure Virtual Machines disaster recovery - High Churn support
 description: Describes how to protect your Azure Virtual Machines having high churning workloads.
-services: site-recovery
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
-ms.topic: conceptual
-ms.date: 05/31/2024
+ms.topic: how-to
+ms.date: 09/18/2024
 ms.author: ankitadutta
 ---
 
diff --git a/articles/site-recovery/concepts-expressroute-with-site-recovery.md b/articles/site-recovery/concepts-expressroute-with-site-recovery.md
@@ -1,12 +1,10 @@
 ---
 title: About using ExpressRoute with Azure Site Recovery
 description: Describes how to use Azure ExpressRoute with the Azure Site Recovery service for disaster recovery and migration.
-services: site-recovery
 author: ankitaduttaMSFT
-manager: rochakm
 ms.service: azure-site-recovery
-ms.topic: conceptual
-ms.date: 10/13/2019
+ms.topic: concept-article
+ms.date: 09/18/2024
 ms.author: ankitadutta
 
 ---
diff --git a/articles/site-recovery/exclude-disks-replication.md b/articles/site-recovery/exclude-disks-replication.md
@@ -1,8 +1,8 @@
 ---
 title: Exclude disks from replication with Azure Site Recovery
 description: How to exclude disks from replication to Azure with Azure Site Recovery.
-ms.topic: conceptual
-ms.date: 12/04/2023
+ms.topic: how-to
+ms.date: 09/18/2024
 ms.service: azure-site-recovery
 ms.author: ankitadutta
 author: ankitaduttaMSFT
diff --git a/articles/site-recovery/hyper-v-azure-support-matrix.md b/articles/site-recovery/hyper-v-azure-support-matrix.md
@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
 description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 12/04/2023
+ms.date: 09/18/2024
 author: ankitaduttaMSFT
 ms.author: ankitadutta
 ---
diff --git a/articles/site-recovery/hyper-v-deployment-planner-analyze-report.md b/articles/site-recovery/hyper-v-deployment-planner-analyze-report.md
@@ -3,10 +3,9 @@ title: Analyze the Hyper-V Deployment Planner report in Azure Site Recovery
 description: This article describes how to analyze a report generated by the Azure Site Recovery Deployment Planner for disaster recovery of Hyper-V VMs to Azure.
 services: site-recovery
 author: ankitaduttaMSFT
-manager: rochakm
 ms.service: azure-site-recovery
-ms.topic: conceptual
-ms.date: 10/21/2019
+ms.topic: concept-article
+ms.date: 09/18/2024
 ms.author: ankitadutta
 
 ---
diff --git a/articles/site-recovery/hyper-v-deployment-planner-cost-estimation.md b/articles/site-recovery/hyper-v-deployment-planner-cost-estimation.md
@@ -3,10 +3,9 @@ title: Review the Azure Site Recovery Deployment Planner cost estimation report
 description: This article describes how to review the cost estimation report generated the Azure Site Recovery Deployment Planner for Hyper-V disaster recovery to Azure.
 services: site-recovery
 author: ankitaduttaMSFT
-manager: rochakm
 ms.service: azure-site-recovery
-ms.topic: conceptual
-ms.date: 4/9/2019
+ms.topic: concept-article
+ms.date: 09/18/2024
 ms.author: ankitadutta
 
 ---
diff --git a/articles/site-recovery/hyper-v-deployment-planner-overview.md b/articles/site-recovery/hyper-v-deployment-planner-overview.md
@@ -2,9 +2,8 @@
 title: Deployment Planner for Hyper-V disaster recovery with Azure Site Recovery
 description: Learn about the Azure Site Recovery Deployment Planner Hyper-V disaster recovery to Azure.
 author: ankitaduttaMSFT
-manager: rochakm
 ms.service: azure-site-recovery
-ms.topic: conceptual
+ms.topic: how-to
 ms.date: 03/13/2024
 ms.author: ankitadutta
 
@@ -61,9 +60,7 @@ The tool provides the following details:
 
 
 >[!IMPORTANT]
->
->Because usage is likely to increase over time, all the preceding tool calculations are performed assuming a 30% growth factor in  workload characteristics, and using a 95th percentile value of all the profiling metrics (read/write IOPS, churn, and so forth). Both of these elements (growth factor and percentile calculation) are configurable. To learn more about growth factor, see the "Growth-factor considerations" section. To learn more about  percentile value, see the "Percentile value used for the calculation" section.
->
+>Because usage is likely to increase over time, all the preceding tool calculations are performed assuming a 30% growth factor in workload characteristics, and using a 95th percentile value of all the profiling metrics (read/write IOPS, churn, and so forth). Both of these elements (growth factor and percentile calculation) are configurable. To learn more about growth factor, see the "Growth-factor considerations" section. To learn more about  percentile value, see the "Percentile value used for the calculation" section.
 
 ## Support matrix
 
@@ -130,13 +127,12 @@ If you have previous version of the deployment planner, do either of the followi
 
 
   >[!NOTE]
-  >
   >When you start profiling with the new version, pass the same output directory path so that the tool appends profile data on the existing files. A complete set of profiled data will be used to generate the report. If you pass a different output directory, new files are created, and old profiled data is not used to generate the report.
   >
   >Each new deployment planner is a cumulative update of the .zip file. You don't need to copy the newest files to the previous  folder. You can create and use a new folder.
 
 ## Version history
-The latest Azure Site Recovery Deployment Planner tool version is 2.5.
+The latest Azure Site Recovery Deployment Planner tool version is 3.0.
 Refer to [Azure Site Recovery Deployment Planner Version History](/azure/site-recovery/site-recovery-deployment-planner-history) page for the fixes that are added in each update.
 
 
diff --git a/articles/site-recovery/migrate-overview.md b/articles/site-recovery/migrate-overview.md
@@ -3,7 +3,7 @@ title: Compare Azure Migrate and Site Recovery for migration to Azure
 description: Summarizes the advantages of using Azure Migrate for migration instead of Site Recovery.
 services: site-recovery
 ms.service: azure-site-recovery
-ms.topic: conceptual
+ms.topic: concept-article
 ms.date: 10/31/2023
 ms.author: ankitadutta
 author: ankitaduttaMSFT
@@ -12,7 +12,7 @@ ms.custom: engagement-fy23
 
 # Migrating to Azure
 
-For migration, we recommend that you use the Azure Migrate service to migrate your VMs and servers to Azure, instead of using Azure Site Recovery service. Learn about [Azure Migrate](../migrate/migrate-services-overview.md).
+For migration, we recommend that you use the Azure Migrate service to migrate your virtual machines and servers to Azure, instead of using Azure Site Recovery service. Learn about [Azure Migrate](../migrate/migrate-services-overview.md).
 
 ## Why use Azure Migrate?
 
@@ -23,22 +23,22 @@ Using Azure Migrate for migration provides many advantages:
 - The Migration and modernization tool is purpose-built for server migration to Azure. It's optimized for migration. You don't need to learn about concepts and scenarios that aren't directly relevant to migration. 
 - Azure Migrate can be used to identify modernization opportunities and migration previews.
 - Some key features like OS upgrade are only available with Azure Migrate
-- There are no tool usage charges for migration for 180 days, from the time replication is started for a VM. This gives you time to complete migration. You only pay for the storage and network resources used in replication, and for compute charges consumed during test migrations.
-- Azure Migrate supports all migration scenarios supported by Site Recovery. In addition, for VMware VMs, Azure Migrate provides an agentless migration option.
+- There are no tool usage charges for migration for 180 days, from the time replication is started for a virtual machine. This gives you time to complete migration. You only pay for the storage and network resources used in replication, and for compute charges consumed during test migrations.
+- Azure Migrate supports all migration scenarios supported by Site Recovery. In addition, for VMware virtual machines, Azure Migrate provides an agentless migration option.
 - We're prioritizing new migration features for the Migration and modernization tool only. These features aren't targeted for Site Recovery.
 
 ## When to use Site Recovery?
 
 Site Recovery should be used:
 
 - For disaster recovery of on-premises machines to Azure.
-- For disaster recovery of Azure VMs, between Azure regions.
+- For disaster recovery of Azure virtual machines, between Azure regions.
 
 ## Which service to use for migration?
  
 We recommend using Azure Migrate to migrate on-premises servers to Azure.  However, if you've already started your migration journey with Site Recovery, consider the following details:
 
-- If you're already using Azure Site Recovery to replicate your servers, you don't need to deploy a Migrate appliance. Remove the BCDR protection, and replicate with a new appliance.
+- If you're already using Azure Site Recovery to replicate your servers, you don't need to deploy a Migrate appliance. Remove the Business Continuity Disaster Recovery protection, and replicate with a new appliance.
 - However, there are benefits to conducting assessment, dependency analysis, and business case review with the Azure Migrate discovery appliance even for workloads that are already replicating.
 - There could be architecture changes required to support the workload in the long term. In this case, address the requirements while continuing to use Azure Site Recovery to replicate so that you don't lose protections.
 
@@ -49,7 +49,7 @@ Suggestions to choose between Azure Migrate and Site Recovery:
 
 - **For new migration**: If you're beginning a new migration and don't have either Azure Site Recovery or Migrate in place, we recommend that you use Azure Migrate.
 - **For disaster recovery of on-premises machines to Azure**: For disaster recovery of on-premises machines to Azure, we recommend that you use Azure Site Recovery. You can also use this service to migrate machines to Azure once it has been determined that they should be moved off-premise. 
-- **For disaster recovery of Azure VMs between Azure region**: For disaster recovery of Azure VMs between Azure regions, we recommend that you use Azure Site Recovery. Although you can use Azure Migrate to initially move them into Azure.
+- **For disaster recovery of Azure virtual machines between Azure region**: For disaster recovery of Azure virtual machines between Azure regions, we recommend that you use Azure Site Recovery. Although you can use Azure Migrate to initially move them into Azure.
 - **If you're already using Azure Site Recovery**: If you're currently using Azure Site Recovery to actively protect your machines, continue to use it for replication. However, consider using Azure Migrate for conducting business cases and dependency analysis.
 
 ## Next steps
diff --git a/articles/site-recovery/monitor-site-recovery.md b/articles/site-recovery/monitor-site-recovery.md
@@ -3,7 +3,7 @@ title: Monitor Azure Site Recovery
 description: Start here to learn how to monitor Azure Site Recovery.
 ms.date: 03/21/2024
 ms.custom: horz-monitor
-ms.topic: conceptual
+ms.topic: concept-article
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
diff --git a/articles/site-recovery/monitoring-common-questions.md b/articles/site-recovery/monitoring-common-questions.md
@@ -2,9 +2,8 @@
 title: Common questions about Azure Site Recovery monitoring 
 description: Get answers to common questions about Azure Site Recovery monitoring, using inbuilt monitoring and Azure Monitor (Log Analytics)
 ms.service: azure-site-recovery
-services: site-recovery
-ms.date: 10/13/2023
-ms.topic: conceptual
+ms.date: 09/18/2024
+ms.topic: overview
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
@@ -19,7 +18,7 @@ This article answers common questions about monitoring Azure [Site Recovery](sit
 Site Recovery uses a multi-step, asynchronous process to replicate machines to Azure.
 
 - In the penultimate step of replication, recent changes on the machine, along with metadata, are copied into a log/cache storage account.
-- These changes, along with the tag that identifies a recoverable point, are written to the storage account/managed disk in the target region.
+- These changes, along with the tag that identifies a recoverable point, is written to the storage account/managed disk in the target region.
 - Site Recovery can now generate a recoverable point for the machine.
 - At this point, the RPO has been met for the changes uploaded to the storage account so far. In other words, the machine RPO at this point is equal to amount of time that's elapsed from the timestamp corresponding to the recoverable point.
 - Now, Site Recovery picks the uploaded data from the storage account, and applies it to the replica disks created for the machine.
@@ -34,7 +33,7 @@ An incorrect system time on the replicating source machine, or on on-premises in
 ## Inbuilt Site Recovery logging
 
 
-### Why is the VM count in the vault infrastructure view different from the total count shown in Replicated Items?
+### Why is the virtual machine count in the vault infrastructure view different from the total count shown in Replicated Items?
 
 The vault infrastructure view is scoped by replication scenarios. Only machines in the currently selected replication scenario are included in the count for the view. In addition, we only count VMs that are configured to replicate to Azure. Failed over machines, or machines replicating back to an on-premises site, aren't counted in the view.
 
@@ -51,7 +50,7 @@ Only machines for which initial replication has completed are included in the co
 - AzureSiteRecoveryReplicationDataUploadRate and AzureSiteRecoveryProtectedDiskDataChurn are sent every five minutes. 
 - AzureSiteRecoveryJobs is sent at the trigger and completion of a job.
 - AzureSiteRecoveryEvents is sent whenever an event is generated. 
-- AzureSiteRecoveryReplicatedItems is sent whenever there is any environment change. Typically, the data refresh time is 15 minutes after a change. 
+- AzureSiteRecoveryReplicatedItems is sent whenever there's any environment change. Typically, the data refresh time is 15 minutes after a change. 
 
 ### How long is data kept in Azure Monitor logs? 
 
@@ -67,16 +66,16 @@ Typically the size of a log is 15-20 KB.
 
 ### Is there any cost for using built-in Azure Monitor alerts for Azure Site Recovery? 
 
-With built-in Azure Monitor alerts, alerts for critical operations/failures generate by default (that you can view in the portal or via non-portal interfaces) at no additional cost. However, to route these alerts to a notification channel (such as email), it incurs a minor cost for notifications beyond the free tier (of 1000 emails per month). [Learn more about Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
+With built-in Azure Monitor alerts, alerts for critical operations/failures generate by default (that you can view in the portal or via nonportal interfaces) at no extra cost. However, to route these alerts to a notification channel (such as email), it incurs a minor cost for notifications beyond the free tier (of 1,000 emails per month). [Learn more about Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
 
 ### Will the current email notification solution for Azure Site Recovery in Recovery Services vault continue to work? 
 
-As of today, the current email notification solution co-exists in parallel with the new built-in Azure Monitor alerts solution. we recommend you to try out the Azure Monitor based alerting to familiarize yourself with the new experience and leverage its capabilities.
+As of today, the current email notification solution coexists in parallel with the new built-in Azure Monitor alerts solution. We recommend you to try out the Azure Monitor based alerting to familiarize yourself with the new experience and use its capabilities.
 
 ### What is the difference between alert rule, alert processing rule and action group?
 
 - Alert rule: Refers to a user-created rule that specifies the condition on which an alert should be fired.
-- Alert processing rule (earlier called Action rule): Refers to a user-created rule that specifies the notification channels a particular fired alert should be routed to. You can also use alert processing rules to suppress notifications for a period of time. 
+- Alert processing rule (earlier called Action rule): Refers to a user-created rule that specifies the notification channels a particular fired alert should be routed to. You can also use alert processing rules to suppress notifications for time. 
 - Action group: Refers to the notification channel (such as email, ITSM endpoint, logic app, webhook, and so on) that a fired alert can be routed to.
 
 In the case of built-in Azure Monitor alerts, as alerts already generate by default, you don't need to create an alert rule. To route these alerts to a notification channel, you should create an alert processing rule and an action group for these alerts. [Learn more](site-recovery-monitor-and-troubleshoot.md#configure-email-notifications-for-alerts)
diff --git a/articles/site-recovery/physical-azure-set-up-source.md b/articles/site-recovery/physical-azure-set-up-source.md
@@ -1,5 +1,5 @@
 ---
-title: Set up the configuration server for disaster recovery of physical servers to Azure using Azure Site Recovery | Microsoft Docs'
+title: Set up the configuration server for disaster recovery of physical servers to Azure using Azure Site Recovery
 description: This article describes how to set up the on-premises configuration server for disaster recovery of on-premises physical servers to Azure.
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
diff --git a/articles/site-recovery/site-recovery-deployment-planner-history.md b/articles/site-recovery/site-recovery-deployment-planner-history.md
@@ -3,7 +3,7 @@ title: Azure Site Recovery Deployment Planner Version History
 description: Known different Site Recovery Deployment Planner Versions fixes and known limitations along with their release dates.
 services: site-recovery
 author: ankitaduttaMSFT
-ms.topic: conceptual
+ms.topic: overview
 ms.service: azure-site-recovery
 ms.date: 08/07/2024
 ms.author: ankitadutta
diff --git a/articles/site-recovery/site-recovery-vmware-deployment-planner-cost-estimation.md b/articles/site-recovery/site-recovery-vmware-deployment-planner-cost-estimation.md
diff --git a/articles/site-recovery/upgrade-2012R2-to-2016.md b/articles/site-recovery/upgrade-2012R2-to-2016.md
diff --git a/articles/site-recovery/vmware-azure-multi-tenant-overview.md b/articles/site-recovery/vmware-azure-multi-tenant-overview.md
diff --git a/articles/site-recovery/vmware-azure-set-up-process-server-azure.md b/articles/site-recovery/vmware-azure-set-up-process-server-azure.md
