Merge pull request #314250 from paulth1/migrate-business-case-and-assessment

[AQ] edit pass: Migrate business case and assessment

Author: ShawnJackson

articles/migrate/assessment-prerequisites.md

@@ -1,47 +1,47 @@
 ---
 title: Assessment Prerequisites
-description: Lists the prerequisites to perform assessments in Azure Migrate
+description: This article lists the prerequisites to perform assessments in Azure Migrate.
 author: ankitsurkar06
 ms.author: ankitsurkar
 ms.service: azure-migrate
 ms.topic: concept-article
 ms.date: 09/08/2025
 ms.reviewer: v-uhabiba
 
-# Customer intent: As a cloud administrator, I want to ensure all prerequisites for Azure Migrate assessments are met so that I can obtain accurate readiness and sizing evaluations for our workloads before migration.
+# Customer intent: As a cloud administrator, I want to ensure that all prerequisites for Azure Migrate assessments are met so that I can obtain accurate readiness and sizing evaluations for our workloads before migration.
 ---
 
-# Prerequisites for assessments 
- 
-Azure Migrate assessments identifies the readiness and right-sized Azure targets using the configuration and performance data collected from the source workloads. The quality of assessments depends on the quality of the data available for assessments. Thus, to get high quality assessments ensure you have all the prerequisites fulfilled. Before creating the assessments, ensure the following: 
+# Prerequisites for assessments
 
-- You discovered the inventory of all the workloads and applications you intend to assess. 
-- You resolved any data collection issues that your workloads are flagged for.
-- You have enough performance data collected before you create the assessment. You can create assessments anytime, but we recommend letting the appliance collect the performance data for at least 24 hours.  
-- In the case of appliance-based discovery, for better results. Ensure that the appliances are in a connected state and performance data is flowing. 
-- If you have an Enterprise agreement with Microsoft and want to use the negotiated prices to identify the resource cost, ensure that you have access to the required subscriptions. 
+Azure Migrate assessments identify the readiness and rightsized Azure targets by using the configuration and performance data collected from the source workloads. The quality of assessments depends on the quality of the data available for assessments. To get high-quality assessments, make sure that you meet all the prerequisites. Before you create the assessments, ensure that you:
 
-## Discovery sources 
+- Discovered the inventory of all the workloads and applications that you intend to assess.
+- Resolved any data collection issues for which your workloads were flagged.
+- Have enough performance data collected before you create the assessment. You can create assessments anytime, but we recommend that you let the appliance collect the performance data for at least 24 hours.
+- Confirmed that the appliances are in a connected state and performance data is flowing for better results for appliance-based discovery.
+- Have access to the required subscriptions if you have an Enterprise Agreement with Microsoft and want to use the negotiated prices to identify the resource cost.
 
-The discovery source might vary for different workloads depending on the data required for creating the assessments. You can discover your on-premises servers by using either of the following methods: 
+## Discovery sources
 
-   - [Deploying](tutorial-discover-vmware.md) a light-weight Azure Migrate appliance to perform agentless discovery. 
-   - [Importing](tutorial-import-vmware-using-rvtools-xlsx.md) the workload information using predefined templates. 
+The discovery source might vary for different workloads depending on the data that's required to create the assessments. You can discover your on-premises servers by using one of the following methods:
 
-The recommended discovery source is the Azure Migrate appliance as it provides an in-depth view of your machines and ensures regular flow of configuration and performance data, and accounts for changes in the source environment.  
+   - [Deploy](tutorial-discover-vmware.md) a lightweight Azure Migrate appliance to perform agentless discovery.
+   - [Import](tutorial-import-vmware-using-rvtools-xlsx.md) the workload information by using predefined templates.
 
-## What data does the appliance collect? 
+We recommend the Azure Migrate appliance as the discovery source. It provides an in-depth view of your machines and ensures regular flow of configuration and performance data. It also accounts for changes in the source environment.
 
-If you're using the Azure Migrate appliance for assessment, see [metadata and performance data](discovered-metadata.md) collected as an input for the assessment. 
+## What data does the appliance collect?
+
+If you use the Azure Migrate appliance for assessment, see the [metadata and performance data](discovered-metadata.md) that's collected as an input for the assessment.
 
 ## Tag workloads correctly
 
-It is recommended to correctly tag all the servers and workloads for appropriate target recommendations. Assessment uses special tags for identifying the machines and workloads operating in the Dev/Test environment and to mark the workloads and servers for retention or retirement. 
+Make sure that you tag all the servers and workloads correctly for the appropriate target recommendations. Assessment uses special tags to identify the machines and workloads that operate in the dev/test environment and mark the workloads and servers for retention or retirement.
+
+If the workloads and servers operate in the dev/test environment, tag them with `AzM.Environment: Dev`. If this tag is absent on the servers or workloads, they're considered as production workloads by default.
 
-In case the workloads and servers are operating in the Dev/Test environment they should be tagged with the tag **AzM.Environment: Dev**. In case this tag is absent on the servers or workloads, they are considered as production workloads by default. 
+To retain or retire workloads and servers, tag them with `AzM.MigrationIntent: Retain` or `AzM.MigrationIntent: Retire`. If the tag isn't applied, Azure Migrate treats the server or workload as a candidate for migration or modernization. Apply the same tag consistently to servers and all associated workloads to ensure accurate recommendations. For example, if Server 1 must be retained, apply the `Retain` tag to the server and all hosted databases.
 
-In case the workloads and servers are to be retained or retired they should be tagged with the tag **AzM.MigrationIntent: Retain** or **AzM.MigrationIntent:Retire** respectively. In case these tags are absent on these servers or workloads, they are considered for migration or modernization. 
-It is recommended that the servers and all the associated workloads are tagged consistently for appropriate and consistent recommendations. For eg. In case *Server 1* hosts *Database 1* and *Database 2* and the server has to be retained, it is expected that the tag exists on server as well as the databases for appropriate recommendation. 
+## Related content
 
-## Next steps
-Migrate [VMware VMs](tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [physical servers](tutorial-migrate-physical-virtual-machines.md).
+- Migrate [VMware VMs](tutorial-migrate-vmware.md), [Hyper-V VMs](tutorial-migrate-hyper-v.md), and [physical servers](tutorial-migrate-physical-virtual-machines.md).