feedback updates

habibaum · habibaum · commit 3588cffff8eb · 2025-04-11T15:46:41.000+05:30
diff --git a/articles/migrate/assessment-report.md b/articles/migrate/assessment-report.md
@@ -10,9 +10,9 @@ ms.custom: engagement-fy24
 monikerRange: migrate
 --- 
 
-# Assessment Report 
+# Assessment report of Azure readiness
 
-Each assessment provides four key outputs: Azure readiness, right-sized target recommendations, cost details, and migration guidance. 
+Each assessment provides four key outputs: Azure readiness, right sized target recommendations, cost details, and migration guidance. 
 
 ## Understanding Azure readiness 
 
@@ -26,9 +26,9 @@ Not all workloads are suitable to run in Azure. An Azure Migrate assessment eval
 
 - **Readiness unknown**: Azure Migrate can't determine the readiness of the server because of insufficient metadata. 
 
-Readiness calculations differ based on the source and targets and the methodology to calculate also differs across assessment types. Learn more about readiness calculations of Azure VM assessments, Azure SQL assessments, AVS assessments, and Web app assessments. 
+Readiness calculations differ based on the source and targets and the methodology to calculate also differs across assessment types. 
 
-## Right-sized recommendations 
+## Right sized recommendations 
 
 After the server is marked as ready for Azure, the assessment makes sizing recommendations in the assessment. These recommendations identify the target for the on-premises workloads being assessed. Sizing calculations depend on whether you're using as-is on-premises sizing or performance-based sizing. 
 
@@ -37,7 +37,7 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 **Performance-based** | Assessments that make recommendations based on collected performance data. |  The compute recommendation is based on CPU and memory utilization data.<br/><br/> The storage recommendation is based on the input/output operations per second (IOPS) and throughput of the on-premises disks. Disk types are Azure Standard HDD, Azure Standard SSD, Azure Premium disks, and Azure Ultra disks. 
 **As-is on-premises** | Assessments that don't use performance data to make recommendations. |  The compute recommendation is based on the on-premises server size.<br/><br/> The recommended storage is based on the selected storage type for the assessment. 
 
-In performance based assessment the assessment identifies the appropriate data point to use for rightsizing. Identification is based on the percentile values for performance history and percentile utilization taken as input as assessment setting.   
+In performance-based assessment the assessment identifies the appropriate data point to use for right sizing. Identification is based on the percentile values for performance history and percentile utilization taken as input as assessment setting.   
 
 For example, if the performance history selected is one week and the percentile utilization is the 95th percentile, the assessment sorts the performance data sample points for the last week. It sorts them in ascending order and picks the 95th percentile value for rightsizing. 
  
@@ -52,7 +52,7 @@ This value is multiplied by the comfort factor(taken as an input in assessment s
 
 ### Monthly costs 
 
-After right-sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default minimizing the cost is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more about how pricing works in Azure Migrate assessments. 
+After right-sizing target candidates are selected, and if more than one suitable candidate is available the recommended target is selected based on selected migration strategy. By default **Minimizing the cost** is the selected strategy. In the case of Azure VM and AVS assessment that is the only strategy. Once the targets are finalized a monthly cost is calculated by aggregating the cost of all resources, licenses and ancillary services like security. Based on the selected input from assessment settings the prices and offer details are fetched to arrive at the final cost. Learn more [about how pricing](cost-estimation.md) works in Azure Migrate assessments. 
 
 ### Confidence ratings (performance-based) 
 
@@ -75,7 +75,7 @@ If any of these utilization numbers isn't available, the size recommendations mi
 
 ### Ratings 
 
-This table shows the assessment confidence ratings, which depend on the percentage of available data points: 
+The table below shows the confidence ratings for assessment, which depend on the percentage of available data points: 
 
 **Availability of data points** | **Confidence rating** 
 --- | --- 
diff --git a/articles/migrate/cost-estimation.md b/articles/migrate/cost-estimation.md
@@ -11,7 +11,10 @@ monikerRange: migrate
 
 # Cost estimation of Assessment in Azure 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. 
+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. 
+
+> [!NOTE]
+> 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, which estimate hosting costs for recommended targets on Azure, based on region rates, applicable offers, and selected licensing programs.
 
diff --git a/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md b/articles/migrate/onboard-to-azure-arc-with-azure-migrate.md
@@ -62,7 +62,7 @@ Before you set up the appliance,
 
 ## Configure the appliance and start discovery  
 
-Use [this article](./tutorial-discover-vmware.md#start-continuous-discovery) to configure the Azure Migrate appliance and kick off the vCenter Server discovery. 
+This section explains [how to configure the Azure Migrate appliance](./tutorial-discover-vmware.md#start-continuous-discovery) and kick off the vCenter Server discovery. 
 
 As you configure the appliance for discovery, you need to specify the  details in the appliance configuration manager:
 
@@ -78,6 +78,9 @@ After the discovery has been successfully completed, it takes around 15 minutes
 > Software inventory must be completed before onboarding your discovered servers to Azure Arc. 
 
 Once the vCenter Server discovery has been completed, software inventory (discovery of installed applications) will be automatically initiated. During software inventory, the server credentials provided will be iterated and validated against the discovered servers. You can start onboarding after the software inventory has been completed and the credentials have been mapped. It may take up to 6 hours for software inventory to complete after it is turned on.  
+
+Follow these steps: 
+
 1. Navigate to the **Onboard to Azure Arc** panel. 
 
     ![Arc onboarding](./media/onboard-to-azure-arc-with-azure-migrate/azure-arc-onboarding-panel-after-being-enabled.png)
@@ -114,13 +117,13 @@ Once the vCenter Server discovery has been completed, software inventory (discov
 
 ## Troubleshooting Azure Arc onboarding errors
 
-If you receive an error when onboarding to Azure Arc using the Azure Migrate appliance, the following section can help identify the probable cause and suggested steps to resolve your problem. 
+If you receive an error when onboarding to Azure Arc using the Azure Migrate appliance, the following information can help identify the probable cause and suggested steps to resolve your problem. 
 
-If you don't see the error code listed below or if the error code starts with **_AZCM_**, refer to [this guide for troubleshooting Azure Arc](/azure/azure-arc/servers/troubleshoot-agent-onboard).
+If you don't see the error code listed below or if the error code starts with **_AZCM_**, see [this guide for troubleshooting Azure Arc](/azure/azure-arc/servers/troubleshoot-agent-onboard).
 
 ### Error 60001 - UnableToConnectToPhysicalServer  
 
-**Possible causes**  
+**Possible cause**  
 Either the [prerequisites](./migrate-support-matrix-physical.md) to connect to the server have not been met or there are network issues in connecting to the server, for instance some proxy settings.
 
 **Recommended actions**   
@@ -134,7 +137,7 @@ Either the [prerequisites](./migrate-support-matrix-physical.md) to connect to t
 
 ### Error 60002 - InvalidServerCredentials  
 
-**Possible causes**  
+**Possible cause**  
 Unable to connect to server. Either you have provided incorrect credentials on the appliance or the credentials previously provided have expired.
 
 **Recommended actions**  
@@ -144,7 +147,7 @@ Unable to connect to server. Either you have provided incorrect credentials on t
 
 ### Error 60005 - SSHOperationTimeout  
 
-**Possible causes**  
+**Possible cause**  
 - The operation took longer than expected either due to network latency issues or due to the lack of latest updates on the server. 
 
 **Recommended actions**  
@@ -155,7 +158,7 @@ Unable to connect to server. Either you have provided incorrect credentials on t
 
 ### Error 60108 - SoftwareInventoryCredentialNotAssociated  
 
-**Possible causes**  
+**Possible cause**  
 - No credentials were found to be associated with the server.
 
 **Recommended actions**  
@@ -165,34 +168,34 @@ Unable to connect to server. Either you have provided incorrect credentials on t
 
 ### Error 60109 - ArcOsNotSupported  
 
-**Possible causes**  
+**Possible cause**  
 - The server hosts an unsupported operating system for Azure Arc onboarding.
 
-**Recommended actions**  
+**Recommended action**  
 - [Review the supported operating systems](/azure/azure-arc/servers/prerequisites#supported-operating-systems) for Azure Arc. 
  
 ### Error 10002 - ScriptExecutionTimedOutOnVm  
 
-**Possible causes**  
+**Possible cause**  
 - The onboarding task did not complete in time. Then execution took longer than expected. 
 
-**Recommended actions**  
+**Recommended action**  
 - The issue should automatically resolve in some time. If the issue persists, contact Microsoft Support.  
  
 ### Error 50000 - AccessDenied 
 
-**Possible causes**  
+**Possible cause**  
 - The operation could not be completed due to forbidden access on the server. The user account provided on the appliance to access the server does not have the required permissions or the credentials are incorrect. WinRM error code: 0x80070005
 
-**Recommended actions**  
+**Recommended action**  
 - Validate the possible causes and retry the operation. If the issue persists, contact support.
 
 ### Error 960/951/60009/60078 - NullResult/UnhandledException/ServerUnknownError/UnhandledError
 
-**Possible causes**  
+**Possible cause**  
 - The operation failed due to an internal error. 
 
-**Recommended actions**  
+**Recommended action**  
 - Retry the operation after some time. If the issue persists, contact support and provide the appliance machine ID (available in the **footer** of the appliance configuration manager).
 
 ## Next steps 
diff --git a/articles/migrate/resource-tagging.md b/articles/migrate/resource-tagging.md
@@ -9,7 +9,7 @@ ms.date: 03/20/2025
 monikerRange: migrate
 ---
 
-# Tagging in Azure Migrate
+# Tags in Azure Migrate
 
 ## Overview
 
diff --git a/articles/migrate/review-assessment.md b/articles/migrate/review-assessment.md
@@ -43,7 +43,7 @@ After the server is marked as ready for Azure, the assessment makes sizing recom
 | **Performance-based** | The compute recommendation is based on CPU and memory utilization data. <br> The storage recommendation is based on the input/output operations per second (IOPS) and throughput of the on-premises disks. Available disk types are Azure Standard HDD, Azure Standard SSD, Azure Premium disks, and Azure Ultra disks.  |
 | **As-is on-premises** | The compute recommendation is based on the on-premises server size. <br> The recommended storage is based on the selected storage type for the assessment.|
 
-You can review the source properties that were used for right-sizing the targets. For each on-premises workload, the configuration properties and the aggregated performance data are available. Review the allocated cores, allocated memory, CPU utilization, and memory utilization for compute right sizing and disk size, read IO/s, and throughput for storage recommendations.  
+You can review the source properties that were used for right sizing the targets. For each on-premises workload, the configuration properties and the aggregated performance data are available. Review the allocated cores, allocated memory, CPU utilization, and memory utilization for compute right sizing and disk size, read IO/s, and throughput for storage recommendations.  
 
 On the **Target recommendations** page, you can review the target configuration and the recommendation reasoning for each target component like compute, storage, network etc.  
 
@@ -56,7 +56,7 @@ If you use as-is on-premises sizing, the assessment doesn't consider the perform
 - **Storage and disk sizing**: The assessment recommends the appropriate disk type based on the storage type specified in the assessment properties. Available storage types are Standard HDD, Standard SSD, Premium, and Ultra disk.  
 - **Network sizing**: The assessment considers the network adapter on the on-premises server. 
 
-## Calculate sizing (performance-based) 
+## Calculate sizing for performance-based assessment
 
 If you use performance-based sizing in an Azure VM assessment, the assessment makes sizing recommendations as follows: 
 
@@ -88,8 +88,8 @@ For storage sizing in an Azure VM assessment, Azure Migrate tries to map each di
     - Provisioned IOPS is calculated using the following logic: 
       - If source throughput discovered is in the allowable range for the Ultra disk size, provisioned IOPS is equal to source disk IOPS.
       - Else, provisioned IOPS is calculated using IOPS to be provisioned = (source disk throughput) *1024/256 
-      - Provisioned throughput range is dependent on provisioned IOPS 
-
+      - Provisioned throughput range is dependent on provisioned IOPS. [Learn more](assessment-report.md#confidence-ratings-performance-based)
+      
 ### Network sizing 
 
 For an Azure VM assessment, the assessment tries to find an Azure VM that supports the number and required performance of network adapters attached to the on-premises server. 
@@ -107,7 +107,7 @@ After it calculates storage and network requirements, the assessment considers C
 - If a suitable size is found, Azure Migrate applies storage and networking calculations. It then applies location and pricing-tier settings for the final VM size recommendation. 
 - If there are multiple eligible Azure VM sizes, the one with the lowest cost is recommended. 
 
-After sizing recommendations are completed, an Azure VM assessment in Azure Migrate calculates compute and storage costs for after migration. 
+After sizing recommendations are completed, an Azure VM assessment in Azure Migrate calculates compute and storage costs for migration. 
 
 ## Compute cost 
 
diff --git a/articles/migrate/vm-assessment-properties.md b/articles/migrate/vm-assessment-properties.md
@@ -14,7 +14,7 @@ monikerRange: migrate
 This article describes VM assessment properties that you can use to customize the assessment to fit your requirements. Also, see the [general assessment properties](assessment-properties.md) that are applicable for all workloads in cross-workload assessment.
 
 ## Assessment properties
-This section describes the various components that are part of an assessment.
+This section describes the components that are part of an assessment.
 
 | **Setting Category**  | **Setting** | **Details** |                
 |-------------------|---------|--------  |                                                     
@@ -25,7 +25,8 @@ 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 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).
+> * Azure Migrate supports only Managed disks for migration assessment. 
+> * 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. 
