VMware migrate context

Author: v-sreedevank

articles/migrate/add-server-credentials.md

@@ -66,6 +66,6 @@ Feature | Windows credentials | Linux credentials
 
 ## Next steps
 
-- [Steps to add credentials in VMware appliance](./tutorial-discover-vmware.md#provide-server-credentials).
+- [Steps to add credentials in VMware appliance](./tutorial-discover-vmware.md?context=/azure/migrate/context/migrate-context#provide-server-credentials).
 - [Steps to add credentials in Hyper-V appliance](tutorial-discover-hyper-v.md#provide-server-credentials).
 - [Steps to add credentials in physical appliance](tutorial-discover-physical.md#start-continuous-discovery). 

articles/migrate/common-questions-discovery-assessment.md

@@ -25,7 +25,7 @@ Review the supported geographies for [public](migrate-support-matrix.md#public-c
 
 ## How many servers can I discover with an appliance?
 
-You can discover up to 10,000 servers from VMware environment, up to 5,000 servers from Hyper-V environment, and up to 1000 physical servers by using a single appliance. If you have more servers, read about [scaling a Hyper-V assessment](scale-hyper-v-assessment.md), [scaling a VMware assessment](scale-vmware-assessment.md), or [scaling a physical server assessment](scale-physical-assessment.md).
+You can discover up to 10,000 servers from VMware environment, up to 5,000 servers from Hyper-V environment, and up to 1,000 physical servers by using a single appliance. If you have more servers, read about [scaling a Hyper-V assessment](scale-hyper-v-assessment.md), [scaling a VMware assessment](scale-vmware-assessment.md), or [scaling a physical server assessment](scale-physical-assessment.md).
 
 ## How do I choose the assessment type?
 
@@ -37,7 +37,7 @@ You can discover up to 10,000 servers from VMware environment, up to 5,000 serve
 
 ## Why is performance data missing for some/all servers in my Azure VM and/or AVS assessment report?
 
-For "Performance-based" assessment, the assessment report export says 'PercentageOfCoresUtilizedMissing' or 'PercentageOfMemoryUtilizedMissing' when the Azure Migrate appliance can't collect performance data for the on-premises servers. You can check the *Resolve issues* blade on the Azure Migrate hub page for detailed issues or check the following manually:
+For "Performance-based" assessment, the assessment report export says "PercentageOfCoresUtilizedMissing" or "PercentageOfMemoryUtilizedMissing" when the Azure Migrate appliance can't collect performance data for the on-premises servers. You can check the *Resolve issues* tab on the Azure Migrate hub page for detailed issues or check the following manually:
 
 - If the servers are powered on for the duration for which you're creating the assessment
 - If only memory counters are missing and you're trying to assess servers in Hyper-V environment. In this scenario, enable dynamic memory on the servers and 'Recalculate' the assessment to reflect the latest changes. The appliance can collect memory utilization values for severs in Hyper-V environment only when the server has dynamic memory enabled.
@@ -53,18 +53,18 @@ You can now understand what errors you need to remediate to resolve performance
 - Go to Azure Migrate > **Servers, databases and web apps** > **Migration goals**, select **Resolve issues** on the Discovery and assessment tool.
 - Select **Affected objects** next to the assessment and select the link in the error ID column to review the error details and remediation actions.
 
-You can also review these errors/issues while creating the assessment in the **Select servers to assess** step or in the readiness tab of an existing assessment. If you don't see any errors/issues in the assessment but see non-zero errors in the resolve issues blade, recalculate the assessment to see the issues within the assessment blade. 
+You can also review these errors/issues while creating the assessment in the **Select servers to assess** step or in the readiness tab of an existing assessment. If you don't see any errors/issues in the assessment but see non-zero errors in the Resolve issues tab, recalculate the assessment to see the issues within the Assessment tab. 
 
 ## Why is performance data missing for some/all SQL instances/databases in my Azure SQL assessment?
 
 To ensure performance data is collected, check:
 
 - If the SQL Servers are powered on for the duration for which you're creating the assessment.
-- If the connection status of the SQL agent in Azure Migrate is 'Connected', and check the last heartbeat. 
-- If Azure Migrate connection status for all SQL instances is 'Connected' in the discovered SQL instance section.
+- If the connection status of the SQL agent in Azure Migrate is "Connected", and check the last heartbeat. 
+- If Azure Migrate connection status for all SQL instances is "Connected" in the discovered SQL instance section.
 - If all of the performance counters are missing, ensure that outbound connections on ports 443 (HTTPS) are allowed.
 
-If any of the performance counters are missing, Azure SQL assessment falls back to As on-premises sizing and recommends an Azure SQL configuration based on the allocated cores, memory and total database size on-premises.
+If any of the performance counters are missing, Azure SQL assessment falls back to As on-premises sizing and recommends an Azure SQL configuration based on the allocated cores, memory, and total database size on-premises.
 
 ## Why is confidence rating not available for Azure App Service assessments?
 
@@ -79,17 +79,17 @@ The confidence rating is calculated for "Performance-based" assessments based on
     - Servers are powered on for the duration of the assessment
     - Outbound connections on ports 443 are allowed
     - For Hyper-V Servers, dynamic memory is enabled
-    - The connection status of agents in Azure Migrate are 'Connected' and check the last heartbeat
+    - The connection status of agents in Azure Migrate is "Connected" and check the last heartbeat
     - For Azure SQL assessments, Azure Migrate connection status for all SQL instances is "Connected" in the discovered SQL instance section.
 
     **Recalculate** the assessment to reflect the latest changes in confidence rating.
 
-- For Azure VM and AVS assessments, few servers were created after discovery had started. For example, if you're creating an assessment for the performance history of last one month, but few servers were created in the environment only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low. [Learn more](./concepts-assessment-calculation.md#confidence-ratings-performance-based).
-- For Azure SQL assessments, few SQL instances or databases were created after discovery had started. For example, if you're creating an assessment for the performance history of last one month, but few SQL instances or databases were created in the environment only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low. [Learn more](./concepts-azure-sql-assessment-calculation.md#confidence-ratings).
+- For Azure VM and AVS assessments, few servers were created after discovery started. For example, if you're creating an assessment for the performance history of last one month, but few servers were created in the environment only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low. [Learn more](./concepts-assessment-calculation.md#confidence-ratings-performance-based).
+- For Azure SQL assessments, few SQL instances or databases were created after discovery started. For example, if you're creating an assessment for the performance history of last one month, but few SQL instances or databases were created in the environment only a week ago. In this case, the performance data for the new servers won't be available for the entire duration and the confidence rating would be low. [Learn more](./concepts-azure-sql-assessment-calculation.md#confidence-ratings).
 
 ## Why is my RAM utilization greater than 100%?
 
-By design, in Hyper-V if maximum memory provisioned is less than what is required by the VM, Assessment will show memory utilization to be more than 100%.
+By design, in Hyper-V if maximum memory provisioned is less than what the VM requires, the Assessment will show memory utilization to be more than 100%.
 
 ## I see a banner on my assessment that the assessment now also considers processor parameters. What will be the impact of recalculating the assessment?
 
@@ -110,8 +110,8 @@ If you've selected all available options for your “VM Series” in your assess
 ## Why can't I see all Azure VM families in the Azure VM assessment properties?
 
 There could be two reasons:
-- You've chosen an Azure region where a particular series isn't supported. Azure VM families shown in Azure VM assessment properties are dependent on the availability of the VM series in the chosen Azure location, storage type and Reserved Instance. 
-- The VM series isn't support in the assessment and isn't in the consideration logic of the assessment. We currently don't support B-series burstable, accelerated and high performance SKU series. We're trying to keep the VM series updated, and the ones mentioned are on our roadmap. 
+- You've chosen an Azure region where a particular series isn't supported. Azure VM families shown in Azure VM assessment properties are dependent on the availability of the VM series in the chosen Azure location, storage type, and Reserved Instance. 
+- The VM series isn't support in the assessment and isn't in the consideration logic of the assessment. We currently don't support B-series burstable, accelerated, and high performance SKU series. We're trying to keep the VM series updated, and the ones mentioned are on our roadmap. 
 
 ## The number of Azure VM or AVS assessments on the Discovery and assessment tool are incorrect
 
@@ -125,13 +125,13 @@ Discovery and assessment of SQL Server instances and databases running in your V
 
 Discovery and assessment of .NET web apps running in your VMware environment is now in preview. Get started with [this tutorial](tutorial-discover-vmware.md). If you want to try out this feature in an existing project, ensure that you've completed the [prerequisites](how-to-discover-sql-existing-project.md) in this article.
 
-## I can't see some servers when I am creating an Azure SQL assessment
+## I can't see some servers when I'm creating an Azure SQL assessment
 
 - Azure SQL assessment can only be done on servers running where SQL instances were discovered. If you don't see the servers and SQL instances that you wish to assess, wait for some time for the discovery, and then create the assessment.
 - If you're not able to see a previously created group while creating the assessment, remove any server without a SQL instance from the group.
 - If you're running Azure SQL assessments in Azure Migrate for the first time, it's advisable to create a new group of servers.
 
-## I can't see some servers when I am creating an Azure App Service assessment
+## I can't see some servers when I'm creating an Azure App Service assessment
 
 - Azure App Service assessment can only be done on servers running where web server role was discovered. If you don't see the servers that you wish to assess, wait for some time for the discovery to get completed, and then create the assessment.
 - If you're not able to see a previously created group while creating the assessment, remove any non-VMware server or any server without a web app from the group.
@@ -205,13 +205,13 @@ The Azure SQL assessment only includes databases that are in online status. In c
 
 ## I want to compare costs for running my SQL instances on Azure VM vs Azure SQL Database/Azure SQL Managed Instance
 
-You can create a single **Azure SQL** assessment consisting of desired SQL servers across VMware, Microsoft Hyper-V and Physical/Bare metal environments as well as IaaS Servers of other public clouds such as AWS, GCP, etc. A single assessment covers readiness, SKUs, estimated costs and migration blockers for all the available SQL migration targets in Azure - Azure SQL Managed Instance, Azure SQL Database and SQL Server on Azure VM. You can then compare the assessment output for the desired targets. [Learn More](./concepts-azure-sql-assessment-calculation.md)
+You can create a single **Azure SQL** assessment consisting of desired SQL servers across VMware, Microsoft Hyper-V, and Physical/Bare metal environments as well as IaaS Servers of other public clouds such as AWS, GCP, etc. A single assessment covers readiness, SKUs, estimated costs, and migration blockers for all the available SQL migration targets in Azure - Azure SQL Managed Instance, Azure SQL Database, and SQL Server on Azure VM. You can then compare the assessment output for the desired targets. [Learn More](./concepts-azure-sql-assessment-calculation.md)
 
 ## The storage cost in my Azure SQL assessment is zero
 
 For Azure SQL Managed Instance, there's no storage cost added for the first 32 GB/instance/month storage and additional storage cost is added for storage in 32-GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql/sql-managed-instance/single/).
 
-## I can't see some groups when I am creating an Azure VMware Solution (AVS) assessment
+## I can't see some groups when I'm creating an Azure VMware Solution (AVS) assessment
 
 - AVS assessment can be done on groups that have only VMware machines. Remove any non-VMware machine from the group if you intend to perform an AVS assessment.
 - If you're running AVS assessments in Azure Migrate for the first time, it's advisable to create a new group of VMware machines.
@@ -266,8 +266,8 @@ For example, if an on-premises server has 4 cores and 8 GB of memory at 50% CPU
 
 Similarly, disk sizing depends on sizing criteria and storage type:
 
-- If the sizing criteria is "performance-based" and the storage type is automatic, Azure Migrate takes the IOPS and throughput values of the disk into account when it identifies the target disk type (Standard, Premium or Ultra disk).
-- If the sizing criteria is "as on premises" and the storage type is Premium, Azure Migrate recommends a Premium disk SKU based on the size of the on-premises disk. The same logic is applied to disk sizing when the sizing is as-on-premises and the storage type is Standard, Premium or Ultra disk.
+- If the sizing criteria are "performance-based" and the storage type is automatic, Azure Migrate takes the IOPS and throughput values of the disk into account when it identifies the target disk type (Standard, Premium, or Ultra disk).
+- If the sizing criteria are "as on premises" and the storage type is Premium, Azure Migrate recommends a Premium disk SKU based on the size of the on-premises disk. The same logic is applied to disk sizing when the sizing is as-on-premises and the storage type is Standard, Premium, or Ultra disk.
 
 ## Does performance history and utilization affect sizing in an Azure VM assessment?
 
@@ -294,7 +294,7 @@ Using the 95th percentile value ensures that outliers are ignored. Outliers migh
 
 Import-based Azure VM assessments are assessments created with machines that are imported into Azure Migrate using a CSV file. Only four fields are mandatory to import: Server name, cores, memory, and operating system. Here are some things to note:
 
- - The readiness criteria is less stringent in import-based assessments on the boot type parameter. If the boot type isn't provided, it's assumed the machine has BIOS boot type, and the machine isn't marked as **Conditionally Ready**. In assessments with discovery source as appliance, the readiness is marked as **Conditionally Ready** if the boot type is missing. This difference in readiness calculation is because users might not have all information on the machines in the early stages of migration planning when import-based assessments are done.
+ - The readiness criteria are less stringent in import-based assessments on the boot type parameter. If the boot type isn't provided, it's assumed the machine has BIOS boot type, and the machine isn't marked as **Conditionally Ready**. In assessments with discovery source as appliance, the readiness is marked as **Conditionally Ready** if the boot type is missing. This difference in readiness calculation is because users might not have all information on the machines in the early stages of migration planning when import-based assessments are done.
  - Performance-based import assessments use the utilization value provided by the user for right-sizing calculations. Since the utilization value is provided by the user, the **Performance history** and **Percentile utilization** options are disabled in the assessment properties. In assessments with discovery source as appliance, the chosen percentile value is picked from the performance data collected by the appliance.
 
 ## Why is the suggested migration tool in import-based AVS assessment marked as unknown?
@@ -303,4 +303,4 @@ For machines imported via a CSV file, the default migration tool in an AVS asses
 
 ## Next steps
 
-Learn more about discovering [VMware VMs](./vmware/tutorial-discover-vmware.md), [Hyper-V VMs](tutorial-discover-hyper-v.md), and [Physical servers](tutorial-discover-physical.md).
+Learn more about discovering [VMware VMs](./vmware/tutorial-discover-vmware.md?context=/azure/migrate/context/migrate-context), [Hyper-V VMs](tutorial-discover-hyper-v.md), and [Physical servers](tutorial-discover-physical.md).

articles/migrate/vmware/set-discovery-scope.md

@@ -20,7 +20,7 @@ When you set up the appliance, it connects to vCenter Server and starts discover
 
 ## Before you start
 
-If you haven't set up a vCenter Server user account that Azure Migrate uses for discovery, do that now for [assessment](./tutorial-discover-vmware.md#prepare-vmware) or [agentless migration](./migrate-support-matrix-vmware-migration.md#agentless-migration).
+If you haven't set up a vCenter Server user account that Azure Migrate uses for discovery, do that now for [assessment](./tutorial-discover-vmware.md?context=/azure/migrate/context/migrate-context#prepare-vmware) or [agentless migration](./migrate-support-matrix-vmware-migration.md?context=/azure/migrate/context/migrate-context#agentless-migration).
 
 
 ## Assign permissions and roles
@@ -39,7 +39,7 @@ You can assign permissions on VMware vSphere inventory objects using one of two
 
 ### Assign a role for agentless migration
 
-1. On the appliance vCenter Server account you're using for migration, apply a user-defined role that has the [permissions needed](migrate-support-matrix-vmware-migration.md#vmware-vsphere-requirements-agentless), to all parent objects that host servers you want to discover and migrate.
+1. On the appliance vCenter Server account you're using for migration, apply a user-defined role that has the [permissions needed](migrate-support-matrix-vmware-migration.md?context=/azure/migrate/context/migrate-context#vmware-vsphere-requirements-agentless), to all parent objects that host servers you want to discover and migrate.
 2. You can name the role with something that's easier to identify. For example, <em>Azure_Migrate</em>.
 
 ### Scoped discovery of VMs
@@ -54,4 +54,4 @@ You can assign permissions on VMware vSphere inventory objects using one of two
 
 ## Next steps
 
-[Set up the appliance](how-to-set-up-appliance-vmware.md)
+[Set up the appliance](how-to-set-up-appliance-vmware.md?context=/azure/migrate/context/migrate-context)