Fixed all warnings

Author: SnehaSudhirG

articles/migrate/.openpublishing.redirection.migrate.json

@@ -150,11 +150,6 @@
             "redirect_url": "scale-hyper-v-assessment",
             "redirect_document_id": false
         },
-        {
-            "source_path_from_root": "/articles/migrate/scale-vmware-assessment.md",
-            "redirect_url": "/azure/migrate/vmware/scale-vmware-assessment",
-            "redirect_document_id": false
-        },
         {
             "source_path_from_root": "/articles/migrate/troubleshooting-general.md",
             "redirect_url": "troubleshoot-general",
@@ -215,11 +210,6 @@
             "redirect_url": "/azure/migrate/migrate-hyper-v-servers-to-azure-using-private-link",
             "redirect_document_id": false
         },
-        {
-            "source_path_from_root": "/articles/migrate/tutorial-assess-sql-vmware.md",
-            "redirect_url": "/azure/migrate/vmware/tutorial-assess-sql-vmware",
-            "redirect_document_id": false
-        },
         {
             "source_path_from_root": "/articles/migrate/tutorial-assess-webapps-hyper-v.md",
             "redirect_url": "tutorial-assess-webapps",

articles/migrate/breadcrumb/toc.yml

@@ -5,10 +5,6 @@
   - name: Migrate
     tocHref: /azure/migrate/
     topicHref: /azure/migrate/index
-    items:
-    - name: VMware
-      tocHref: /azure/migrate/vmware/
-      topicHref: /azure/migrate/vmware/start-here-vmware
 
 - name: Azure
   tocHref: /sql/

articles/migrate/how-to-set-up-appliance-vmware.md

@@ -78,13 +78,13 @@ Before you deploy the OVA file, verify that the file is secure:
 
     - For the Azure public cloud:
     
-      [!INCLUDE [public-cloud-vmware.md](../includes/public-cloud-vmware.md)]
+      [!INCLUDE [public-cloud-vmware.md](./includes/public-cloud-vmware.md)]
 
     - For Azure Government:
 
         **Algorithm** | **Download** | **SHA256**
         --- | --- | ---
-        VMware (85.8 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2191847) | [!INCLUDE [security-hash-value.md](../includes/security-hash-value.md)]
+        VMware (85.8 MB) | [Latest version](https://go.microsoft.com/fwlink/?linkid=2191847) | [!INCLUDE [security-hash-value.md](./includes/security-hash-value.md)]
 
 #### Create the appliance server
 

articles/migrate/how-to-test-replicating-virtual-machines.md

@@ -73,7 +73,7 @@ You can change the VNet and subnet of a replicating machine by following the ste
 
 2. Select **Compute and Network** option under **General**.
 
-    :::image type="content" source="../media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-2.png" alt-text="Screenshot shows the location of network and compute option on the details page of replicating machine.":::
+    :::image type="content" source="./media/how-to-test-replicating-virtual-machines/test-migration-subnet-selection-step-2.png" alt-text="Screenshot shows the location of network and compute option on the details page of replicating machine.":::
 
 3. Select the virtual network from the **Test migration** column. It's important to select the VNet in this drop down for test migration to be able to select subnet for each Network Interface Card (NIC) in the following steps.
 

articles/migrate/migrate-support-matrix-vmware-migration.md

@@ -215,7 +215,7 @@ Shared VHD | Not supported.
 FC disk | Not supported.
 BitLocker | Not supported.<br/><br/> BitLocker must be disabled before you migrate the machine.
 VM name | From 1 to 63 characters.<br/><br/> Restricted to letters, numbers, and hyphens.<br/><br/> The machine name must start and end with a letter or number.
-Connect after migration-Windows | To connect to Azure VMs running Windows after migration:<br/><br/> - Before migration, enable RDP on the on-premises VM.<br/><br/> Make sure that TCP and UDP rules are added for the **Public** profile, and that RDP is allowed in **Windows Firewall** > **Allowed Apps** for all profiles.<br/><br/> For site-to-site VPN access, enable RDP and allow RDP in **Windows Firewall** > **Allowed apps and features** for **Domain and Private** networks.<br/><br/> In addition, check that the operating system's SAN policy is set to **OnlineAll**. [Learn more](../prepare-for-migration.md).
+Connect after migration-Windows | To connect to Azure VMs running Windows after migration:<br/><br/> - Before migration, enable RDP on the on-premises VM.<br/><br/> Make sure that TCP and UDP rules are added for the **Public** profile, and that RDP is allowed in **Windows Firewall** > **Allowed Apps** for all profiles.<br/><br/> For site-to-site VPN access, enable RDP and allow RDP in **Windows Firewall** > **Allowed apps and features** for **Domain and Private** networks.<br/><br/> In addition, check that the operating system's SAN policy is set to **OnlineAll**. [Learn more](prepare-for-migration.md).
 Connect after migration-Linux | To connect to Azure VMs after migration using SSH:<br/><br/> Before migration, on the on-premises machine, check that the Secure Shell service is set to Start, and that firewall rules allow an SSH connection.<br/><br/> After failover, on the Azure VM, allow incoming connections to the SSH port for the network security group rules on the failed over VM, and for the Azure subnet to which it's connected.<br/><br/> In addition, add a public IP address for the VM.  
 
 

articles/migrate/migrate-support-matrix-vmware.md

@@ -56,7 +56,7 @@ Device | Connection
 --- | ---
 Azure Migrate appliance | Inbound connections on TCP port 3389 to allow remote desktop connections to the appliance.<br /><br /> Inbound connections on port 44368 to remotely access the appliance management app by using the URL `https://<appliance-ip-or-name>:44368`. <br /><br />Outbound connections on port 443 (HTTPS) to send discovery and performance metadata to Azure Migrate and Modernize.
 vCenter Server | Inbound connections on TCP port 443 to allow the appliance to collect configuration and performance metadata for assessments. <br /><br /> The appliance connects to vCenter on port 443 by default. If vCenter Server listens on a different port, you can modify the port when you set up discovery.
-ESXi hosts | For [discovery of software inventory](../how-to-discover-applications.md) or [agentless dependency analysis](../concepts-dependency-visualization.md#agentless-analysis), the appliance connects to ESXi hosts on TCP port 443 to discover software inventory and dependencies on the servers.
+ESXi hosts | For [discovery of software inventory](how-to-discover-applications.md) or [agentless dependency analysis](concepts-dependency-visualization.md#agentless-analysis), the appliance connects to ESXi hosts on TCP port 443 to discover software inventory and dependencies on the servers.
 
 
 ## Software inventory requirements
@@ -345,7 +345,7 @@ Project limits | You can create multiple Azure Migrate projects in an Azure subs
 Discovery | The Azure Migrate appliance can discover up to 10,000 servers running across multiple vCenter Servers.<br /><br /> The appliance supports adding multiple vCenter Servers. You can add up to 10 vCenter Servers per appliance.<br /><br />The scale is also valid to access discovered servers for Azure Migrate VMware Solution (AVS).<br /><br />The same vCenter can be discovered by multiple appliances within the same project, but it is not recommended to have same VM discovered by multiple appliances. More details on how to set [discovery scope](set-discovery-scope.md).
 Assessment | You can add up to 35,000 servers in a single group.<br /><br /> You can assess up to 35,000 servers in a single assessment.
 
-Learn more about [assessments](../concepts-assessment-calculation.md).
+Learn more about [assessments](concepts-assessment-calculation.md).
 
 
 ## Import servers using RVTools XLSX (preview)

articles/migrate/server-migrate-overview.md

@@ -47,7 +47,7 @@ After reviewing the limitations, understanding the steps involved in deploying e
 **Use the Migration tool** | Add the Migration and modernization tool in the Azure Migrate project. | Required | Required
 **Prepare VMware for migration** | Configure settings on VMware servers and VMs. | Required | Required
 **Install the Mobility service on VMs** | Mobility service runs on each VM you want to replicate | Not required | Required
-**Deploy the replication appliance** | The [replication appliance](../migrate-replication-appliance.md) is used for agent-based migration. It connects between the Mobility service running on VMs, and the Migration and modernization tool. | Not required | Required
+**Deploy the replication appliance** | The [replication appliance](migrate-replication-appliance.md) is used for agent-based migration. It connects between the Mobility service running on VMs, and the Migration and modernization tool. | Not required | Required
 **Replicate VMs**. Enable VM replication. | Configure replication settings and select VMs to replicate | Required | Required
 **Run a test migration** | Run a test migration to make sure everything's working as expected. | Required | Required
 **Run a full migration** | Migrate the VMs. | Required | Required

articles/migrate/tutorial-assess-vmware-azure-vmware-solution.md

@@ -177,7 +177,7 @@ Confidence ratings are as follows.
 61%-80% | 4 stars
 81%-100% | 5 stars
 
-[Learn more](../assessment-report.md#confidence-ratings-performance-based) about confidence ratings.
+[Learn more](assessment-report.md#confidence-ratings-performance-based) about confidence ratings.
 
 ## Next steps
 

articles/migrate/tutorial-assess-webapps-vmware.md

@@ -25,7 +25,7 @@ This article shows you how to assess discovered ASP.NET web apps running on IIS
 
 As part of your migration journey to Azure, assess your on-premises workloads to measure cloud readiness, identify risks, and estimate costs and complexity.
 
-This article shows you how to assess discovered Java web apps running on Tomcat servers in preparation for migration to Azure App Service Code and Azure App Service Containers, using the Azure Migrate: Discovery and assessment tool. [Learn more](app-service/overview.md) about Azure App Service.
+This article shows you how to assess discovered Java web apps running on Tomcat servers in preparation for migration to Azure App Service Code and Azure App Service Containers, using the Azure Migrate: Discovery and assessment tool. [Learn more](../app-service/overview.md) about Azure App Service.
 
 
 ::: zone-end

articles/migrate/tutorial-discover-vmware.md

@@ -39,8 +39,8 @@ Requirement | Details
 --- | ---
 **vCenter Server/ESXi host** | You need a server running vCenter Server version 8.0, 7.0, 6.7, 6.5, 6.0, or 5.5.<br /><br /> Servers must be hosted on an ESXi host running version 5.5 or later.<br /><br /> On the vCenter Server, allow inbound connections on TCP port 443 so that the appliance can collect configuration and performance metadata.<br /><br /> The appliance connects to vCenter Server on port 443 by default. If the server running vCenter Server listens on a different port, you can modify the port when you provide the vCenter Server details in the appliance configuration manager.<br /><br /> On the ESXi hosts, make sure that inbound access is allowed on TCP port 443 for discovery of installed applications and for agentless dependency analysis on servers.
 **Azure Migrate appliance** | vCenter Server must have these resources to allocate to a server that hosts the Azure Migrate appliance:<br /><br /> - 32 GB of RAM, 8 vCPUs, and approximately 80 GB of disk storage.<br /><br /> - An external virtual switch and internet access on the appliance server, directly or via a proxy.
-**Servers** | All Windows and Linux OS versions are supported for discovery of configuration and performance metadata. <br /><br /> For application discovery on servers, all Windows and Linux OS versions are supported. Check the [OS versions supported for agentless dependency analysis](/azure/migrate/vmware/migrate-support-matrix-vmware?pivots=dependency-analysis-agentless-requirements&tabs=businesscase).<br /><br /> For discovery of installed applications and for agentless dependency analysis, VMware Tools (version 10.2.1 or later) must be installed and running on servers. Windows servers must have PowerShell version 2.0 or later installed.<br /><br /> To discover SQL Server instances and databases, check [supported SQL Server and Windows OS versions and editions](/azure/migrate/vmware/migrate-support-matrix-vmware?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) and Windows authentication mechanisms.<br /><br /> To discover ASP.NET web apps running on IIS web server, check [supported Windows OS and IIS versions](/azure/migrate/vmware/migrate-support-matrix-vmware?pivots=web-apps-discovery&tabs=businesscase).<br /><br />  To discover Java web apps running on Apache Tomcat web server, check [supported Linux OS and Tomcat versions](/azure/migrate/vmware/migrate-support-matrix-vmware?pivots=web-apps-discovery&tabs=businesscase). 
-**SQL Server access** | To discover SQL Server instances and databases, the Windows account, or SQL Server account [requires these permissions](migrate-support-matrix-vmware?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) for each SQL Server instance. You can use the [account provisioning utility](./least-privilege-credentials.md) to create custom accounts or use any existing account that is a member of the sysadmin server role for simplicity.
+**Servers** | All Windows and Linux OS versions are supported for discovery of configuration and performance metadata. <br /><br /> For application discovery on servers, all Windows and Linux OS versions are supported. Check the [OS versions supported for agentless dependency analysis](migrate-support-matrix-vmware?pivots=dependency-analysis-agentless-requirements&tabs=businesscase).<br /><br /> For discovery of installed applications and for agentless dependency analysis, VMware Tools (version 10.2.1 or later) must be installed and running on servers. Windows servers must have PowerShell version 2.0 or later installed.<br /><br /> To discover SQL Server instances and databases, check [supported SQL Server and Windows OS versions and editions](migrate-support-matrix-vmware?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) and Windows authentication mechanisms.<br /><br /> To discover ASP.NET web apps running on IIS web server, check [supported Windows OS and IIS versions](migrate-support-matrix-vmware?pivots=web-apps-discovery&tabs=businesscase).<br /><br />  To discover Java web apps running on Apache Tomcat web server, check [supported Linux OS and Tomcat versions](migrate-support-matrix-vmware?pivots=web-apps-discovery&tabs=businesscase). 
+**SQL Server access** | To discover SQL Server instances and databases, the Windows account, or SQL Server account [requires these permissions](migrate-support-matrix-vmware?pivots=sql-server-instance-database-discovery-requirements&tabs=businesscase) for each SQL Server instance. You can use the [account provisioning utility](least-privilege-credentials.md) to create custom accounts or use any existing account that is a member of the sysadmin server role for simplicity.
 
 ## Prepare an Azure user account
 
@@ -309,7 +309,7 @@ To add server credentials:
     Select **Save**.
 
     If you choose to use domain credentials, you also must enter the FQDN for the domain. The FQDN is required to validate the authenticity of the credentials with the Active Directory instance in that domain.
-1. Review the [required permissions](../add-server-credentials.md#required-permissions) on the account for discovery of installed applications, agentless dependency analysis, and discovery of web apps and SQL Server instances and databases.
+1. Review the [required permissions](add-server-credentials.md#required-permissions) on the account for discovery of installed applications, agentless dependency analysis, and discovery of web apps and SQL Server instances and databases.
 1. To add multiple credentials at once, select **Add more** to save credentials, and then add more credentials.
     When you select **Save** or **Add more**, the appliance validates the domain credentials with the domain's Active Directory instance for authentication. Validation is made after each addition to avoid account lockouts as the appliance iterates to map credentials to respective servers.
 
@@ -319,7 +319,7 @@ In the configuration manager, in the credentials table, see the **Validation sta
 
 If validation fails, you can select a **Failed** status to see the validation error. Fix the issue, and then select **Revalidate credentials** to reattempt validation of the credentials.
 
-:::image type="content" source="../media/tutorial-discover-vmware/add-server-credentials-multiple.png" alt-text="Screenshot that shows providing and validating multiple credentials.":::
+:::image type="content" source="./media/tutorial-discover-vmware/add-server-credentials-multiple.png" alt-text="Screenshot that shows providing and validating multiple credentials.":::
 
 ### Start discovery