pre plr updates

habibaum · habibaum · commit ecefa73f767d · 2025-04-08T11:04:11.000+05:30
diff --git a/articles/migrate/centralized-issue-tracking.md b/articles/migrate/centralized-issue-tracking.md
@@ -4,7 +4,7 @@ description: Describes how to track issues and provide resolutions from one tab.
 author: ankitsurkar06
 ms.author: ankitsurkar
 ms.service: azure-migrate
-ms.topic: how-to
+ms.topic: Conceptual
 ms.date: 03/20/2025
 monikerRange: migrate
 ---
@@ -19,7 +19,7 @@ Azure Migrate offers a comprehensive platform for migrating, modernizing, and op
 
 The new **Action Center** feature in Azure Migrate addresses this challenge by offering a **centralized hub** where users can view and manage all migration-related issues, pending actions, and jobs across their projects. This includes issues related to **discovery**, **dependency visualization**, and **assessments**, streamlining the troubleshooting process by bringing together different types of issues in a single interface. This unified view helps users stay organized and prioritize their actions effectively, enabling faster issue resolution and a smoother migration experience.
 
-## How to access Action Center
+## Access Action Center
 
 The Action Center can be accessed directly from the Azure Migrate dashboard, providing an integrated and accessible solution for managing migration issues and actions.
 
diff --git a/articles/migrate/cost-estimation.md b/articles/migrate/cost-estimation.md
@@ -13,7 +13,7 @@ monikerRange: migrate
 
 Azure Migrate assessments provide you with an estimated cost of hosting the recommended targets on Azure. These costs are identified for each right-sized target on Azure. The cost estimates are dependent on the rates in the specified region, any applicable offers, and the licensing program selected by you. 
 
-This article describes Azure Migrate assessments estimate hosting costs for recommended targets on Azure, based on region rates, applicable offers, and selected licensing programs.
+This article describes Azure Migrate assessments, which estimate hosting costs for recommended targets on Azure, based on region rates, applicable offers, and selected licensing programs.
 
 ## Pricing settings 
 
diff --git a/articles/migrate/how-to-create-sql-assessment.md b/articles/migrate/how-to-create-sql-assessment.md
@@ -14,8 +14,6 @@ ms.custom: engagement-fy23
 
 This article to create SQL assessments for migration to Azure, targeting different Azure PaaS and laaS options using Azure Migrate. By creating as assessment for your SQL instances, you'll receive recommended target environments and key insights, such as **readiness**, **target right-sizing**, and monthly **costs** for hosting and running these applications.
 
-In this article, you'll learn how to:
-
 * Set up your Azure Migrate environment to assess web applications.
 * Select a set of related applications discovered using Azure Migrate appliance.
 * Provide assessment configuration, including preferred Azure targets, target regions, and Azure reserved instances.
@@ -29,19 +27,19 @@ In this article, you'll learn how to:
 
 ## Create a workload assessment for webapps
 
-1. On the **Azure Migrate** project overview page, under **Decide and plan**, select **Assessments**
+1. On the **Azure Migrate** project overview page, under **Decide and plan**, select **Assessments**.
 
     :::image type="content" source="./media/how-to-create-sql-assessment/assessment.png" alt-text=" Screenshot of assessment page on how to sql create an assessment.":::
 
-1. In **Assessments** page, select **Create assessment**
+1. In **Assessments** page, select **Create assessment**.
 
     :::image type="content" source="./media/how-to-create-sql-assessment/create-assessment.png" alt-text="Screenshot of assessment page on how to create an assessment.":::
 
-1. Provide a suitable name for the assessment, then select **Add workloads**
+1. Provide a suitable name for the assessment, then select **Add workloads**.
 
     :::image type="content" source="./media/how-to-create-sql-assessment/add-workloads.png" alt-text="Screenshot of sql assessment page on how to add the workloads.":::
 
-1. Use the appropriate filters, select the webapp and then select **Add**
+1. Use the appropriate filters, select the webapp and then select **Add**.
 
     :::image type="content" source="./media/how-to-create-sql-assessment/select-add.png" alt-text="Screenshot of sql assessment page on how to select webapp and add.":::
 
diff --git a/articles/migrate/how-to-review-sql-assessment.md b/articles/migrate/how-to-review-sql-assessment.md
@@ -94,7 +94,7 @@ The assessment aggregates all the configuration and performance data to identify
 
 **As on-premises sizing calculation**
 
-The instances to SQL Server on Azure VM assessment report outline the ideal approach for migrating SQL Server instances to SQL Server on Azure VM, adhering to the best practices. [Learn more](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist?preserve-view=true&view=azuresql#vm-size)
+The instances to SQL Server on Azure VM assessment report outline the ideal approach for migrating SQL Server instances to SQL Server on Azure VM, adhering to the best practices. [Learn more](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-checklist?preserve-view=true&view=azuresql#vm-size).
 
 **Storage sizing**
 
@@ -118,7 +118,7 @@ After identifying storage disks, the assessment considers CPU and memory require
 
 ## Performance-based sizing calculation
 
-If the source is a SQL Server Always On Failover Cluster Instance (FCI), the assessment report outlines the approach for migrating to a two-node SQL Server Failover Cluster Instance. This approach preserves high availability and disaster recovery objectives while adhering to the best practices. [Learn more](/azure/azure-sql/virtual-machines/windows/hadr-cluster-best-practices?view=azuresql&preserve-view=true&tabs=windows2012)
+If the source is a SQL Server Always On Failover Cluster Instance (FCI), the assessment report outlines the approach for migrating to a two-node SQL Server Failover Cluster Instance. This approach preserves high availability and disaster recovery objectives while adhering to the best practices. [Learn more](/azure/azure-sql/virtual-machines/windows/hadr-cluster-best-practices?view=azuresql&preserve-view=true&tabs=windows2012).
 
 **Storage sizing**
 
diff --git a/articles/migrate/resource-tagging.md b/articles/migrate/resource-tagging.md
@@ -51,7 +51,7 @@ To view tags, select the workload for which you wish to view the tags assigned.
 
 To filter using tags, follow these steps:
 
-1.	Select **Add filter** button beside the search bar.
+1.	Select **Add filter** beside the search bar.
 
 2.	Select the tag key that you want to filter with.
 
diff --git a/articles/migrate/review-assessment.md b/articles/migrate/review-assessment.md
@@ -16,7 +16,7 @@ This article describes the various components of an Azure VM assessment and how
 
 Once you create the Azure VM assessment, you can review it at **Decide and plan** > **Assessments** > **Workloads**.  
 
-If it's a performance-based assessment with servers discovered using appliance, you can review the confidence rating of the assessment before you look at the report. The confidence rating is an indicator of the quality of the data that was available for creating assessments. [Learn more](confidence-ratings.md)
+If it's a performance-based assessment with servers discovered using appliance, you can review the confidence rating of the assessment before you look at the report. The confidence rating is an indicator of the quality of the data that was available for creating assessments. [Learn more](confidence-ratings.md).
 
 On the **Overview** page, you can review the overall readiness and estimated monthly cost of hosting the VMs on Azure after migration using the lift and shift method. 
 
@@ -27,9 +27,9 @@ For each source server, you can review the Azure readiness. Azure readiness is d
 
 - **Ready for Azure**: The workloads can be migrated as-is to Azure without any changes. It will start in Azure with full Azure support. 
 
-- **Conditionally ready for Azure**: The workloads might start in Azure but might not have full Azure support. For example, Azure doesn't support a server that's running an old version of Windows Server. You must be careful before you migrate these servers to Azure. To fix any readiness issue, follow the remediation guidance the assessment suggests. 
+- **Conditionally ready for Azure**: The workloads might start in Azure but might not have full Azure support. For example, Azure doesn't support a server that's running an old version of Windows Server. You must be careful before you migrate these servers to Azure. To fix any readiness issues, follow the remediation guidance the assessment suggests. 
 
-- **Not ready for Azure**: The server won't start in Azure. For example, if an on-premises server's disk stores more than 64 TB, Azure can't host the server. Follow the remediation guidance to fix the issue before migration. 
+- **Not ready for Azure**: The server won't start in Azure. For example, if an on-premises server's disk stores more than 64 TB, Azure can't host the server. Follow the remediation guidance to fix the issues before migration. 
 
 - **Readiness unknown**: Azure Migrate can't determine the readiness of the server because of insufficient metadata. 
 
@@ -133,15 +133,15 @@ The cost for Standard or Premium disks is calculated based on the selected/recom
 
 ### Ultra disk 
 
-The cost for Ultra disk is calculated based on the provisioned size, provisioned IOPS, and provisioned throughput. [Learn more](/pricing/details/managed-disks/)
+The cost for Ultra disk is calculated based on the provisioned size, provisioned IOPS, and provisioned throughput. [Learn more](/pricing/details/managed-disks/).
 
 The cost is calculated using the following logic: 
 
 - Cost of disk size is calculated by multiplying provisioned disk size by hourly price of disk capacity.
 - Cost of provisioned IOPS is calculated by multiplying provisioned IOPS by hourly provisioned IOPS price.
 - Cost of provisioned throughput is calculated by multiplying provisioned throughput by hourly provisioned throughput price.
 
-The Ultra disk VM reservation fee isn't added in the total cost. [Learn more](https://azure.microsoft.com/pricing/details/managed-disks/) 
+The Ultra disk VM reservation fee isn't added in the total cost. [Learn more](https://azure.microsoft.com/pricing/details/managed-disks/). 
 
 The assessment calculates the total monthly storage costs by aggregating the storage costs of all servers. Currently, the calculation doesn't consider offers specified in the assessment settings. 
 
diff --git a/articles/migrate/review-azure-vmware-solution-assessment.md b/articles/migrate/review-azure-vmware-solution-assessment.md
@@ -9,7 +9,7 @@ ms.date: 11/07/2024
 ms.custom: engagement-fy24
 ---
 
-# Review an Azure VMware Solution (AVS) assessment
+# Tutorial: Review an Azure VMware Solution (AVS) assessment
 
 An Azure VMware Solution (AVS) assessment describes:
 
@@ -38,7 +38,7 @@ You can select  **Sizing assumptions** to understand the assumptions that went i
 
 2. Review the server status:
     - **Ready for AVS**: The server can be migrated as-is to Azure (AVS) without any changes. It will start in AVS with full AVS support.
-    - **Ready with conditions**: There might be some compatibility issues, for example, internet protocol or deprecated OS in VMware, and need to be remediated before migrating to Azure VMware Solution. To fix any readiness issuesc, follow the remediation guidance the assessment suggests.
+    - **Ready with conditions**: There might be some compatibility issues, for example, internet protocol or deprecated OS in VMware, and need to be remediated before migrating to Azure VMware Solution. To fix any readiness issues, follow the remediation guidance the assessment suggests.
     - **Not ready for AVS**: The VM will not start in AVS. For example, if the on-premises VMware VM has an external device attached such as a cd-rom the VMware vMotion operation will fail (if using VMware vMotion).
     - **Readiness unknown**: Azure Migrate couldn't determine the readiness of the server because of insufficient metadata collected from the on-premises environment.
 
diff --git a/articles/migrate/review-sql-assessment.md b/articles/migrate/review-sql-assessment.md
@@ -32,7 +32,7 @@ This indicates the number of SQL servers, instances, and databases that were ass
 
 This indicates the different migration strategies that you can consider for your SQL deployments. You can review the readiness for target deployment types and the cost estimates for SQL Servers/Instances/Databases that are marked ready or ready with conditions: 
 
-- **Recommended deployment**: This is a strategy where an Azure SQL deployment type is the most compatible with your SQL instance. It is the most cost-effective and is recommended. Migrating to a Microsoft-recommended target reduces your overall migration effort. If your instance is ready for SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database, the target deployment type, which has the least migration readiness issues and is the most cost-effective is recommended.
+- **Recommended deployment**: This is a strategy where an Azure SQL deployment type is the most compatible with your SQL instance and it is the most cost-effective. Migrating to a Microsoft-recommended target reduces your overall migration effort. If your instance is ready for SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database, the target deployment type, which has the least migration readiness issues and is the most cost-effective.
 You can see the SQL Server instance readiness for different recommended deployment targets and monthly cost estimates for SQL instances marked *Ready* and *Ready with conditions*.
 
     - You can go to the Readiness report to:
@@ -110,6 +110,7 @@ The assessment summary shows the estimated monthly compute and storage costs for
 1. You can also drill down to the database list to review the Azure SQL configuration and cost estimates per database when an Azure SQL Database configuration is recommended.
 
 ### Review confidence rating
+
 Azure Migrate assigns a confidence rating to all Azure SQL assessments based on the availability of the performance/utilization data points needed to compute the assessment for all the assessed SQL instances and databases. The rating is from one star (lowest) to five stars (highest).
 The confidence rating helps you estimate the reliability of size recommendations in the assessment. Confidence ratings are as follows:
 
diff --git a/articles/migrate/target-right-sizing.md b/articles/migrate/target-right-sizing.md
@@ -4,7 +4,7 @@ description: Describes how Azure Migrate provides sizing recommendations for the
 author: rashi-ms
 ms.author: v-uhabiba
 ms.service: azure-migrate
-ms.topic: how-to
+ms.topic: Conceptual
 ms.date: 03/26/2025
 ---
 
@@ -36,15 +36,15 @@ If you use the appliance for discovery, it collects performance data directly fr
 
 3. The assessment stores all the 10-minute data points for the last month. All the peaks are arranged in the ascending order to identify the appropriate data point to use for right sizing.  
 
-### How is performance data collected for import-based discovery?  
+### Performance data collected for import-based discovery  
 
 If you import servers using a CSV file, the performance values you specify (CPU utilization, Memory utilization, Disk IOPS, and throughput) are used if you choose performance-based sizing. You won't be able to provide performance history and percentile information.  
 
 This method is especially helpful if you've over-allocated the on-premises server, its utilization is low, and you want to right-size the Azure VM to save costs.  
 
 If you don't want to use the performance data, reset the sizing criteria to as-is on-premises, as described in the previous section.  
 
-### How is the performance data used for right-sizing? 
+### Performance data used for right-sizing
 
 When you create an assessment, the assessment identifies the appropriate level of utilization to consider for right-sizing. It's identified based on the performance history and percentile utilization. The performance history specifies the duration used when performance data is evaluated, and percentile utilization specifies the percentile value of the performance sample used for right-sizing. 
 
diff --git a/articles/migrate/vm-assessment-properties.md b/articles/migrate/vm-assessment-properties.md
@@ -24,7 +24,7 @@ This section describes the various components that are part of an assessment.
 | | **Azure Hybrid Benefit**| Specifies whether you have software assurance and are eligible for [Azure Hybrid Benefit](/pricing/hybrid-benefit/) to use your existing OS licenses. For Azure VM assessments, you can bring in both Windows and Linux licenses. If the setting is enabled, Azure prices for selected operating systems aren't considered for VM costing.  |
 
 > [!Note] 
-> In Azure Government, it is important to review the [[supported target](supported-geographies.md)] assessment locations. VM size recommendations in assessments will use the VM series specifically designed for Government Cloud regions.  [Learn more](/explore/global-infrastructure/products-by-region/?regions=usgov-non-regional,us-dod-central,us-dod-east,usgov-arizona,usgov-iowa,usgov-texas,usgov-virginia&products=virtual-machines).
+> In Azure Government, it is recommended to review the [[supported target](supported-geographies.md)] assessment locations. VM size recommendations in assessments will use the VM series specifically designed for Government Cloud regions.  [Learn more](/explore/global-infrastructure/products-by-region/?regions=usgov-non-regional,us-dod-central,us-dod-east,usgov-arizona,usgov-iowa,usgov-texas,usgov-virginia&products=virtual-machines).
 
 ## Next Steps
 [Review](best-practices-assessment.md) the best practices for creating an assessment with Azure Migrate. 
