Merge pull request #267388 from SnehaSudhirG/27Feb-DiscoverVMwareConcept

Added zone pivots - Discover VMware Concept Article

Author: JamesJBarnett

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

@@ -6,8 +6,9 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 01/25/2024
-ms.custom: engagement-fy23
+ms.date: 02/27/2024
+ms.custom: engagement-fy24
+zone_pivot_groups: vmware-discovery-requirements
 ---
 
 # Support matrix for VMware discovery
@@ -21,15 +22,8 @@ To assess servers, first, create an Azure Migrate project. The Azure Migrate: Di
 
 As you plan your migration of VMware servers to Azure, see the [migration support matrix](migrate-support-matrix-vmware-migration.md).
 
-## Limitations
-
-Requirement | Details
---- | ---
-Project limits | You can create multiple Azure Migrate projects in an Azure subscription.<br /><br /> You can discover and assess up to 50,000 servers in a VMware environment in a single [project](migrate-support-matrix.md#project). A project can include physical servers and servers from a Hyper-V environment, up to the assessment limits.
-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 /> This amount is valid for Azure VMware Solution as well.
-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).
+::: zone pivot="vmware-requirements"
 
 ## VMware requirements
 
@@ -38,13 +32,21 @@ VMware | Details
 vCenter Server | Servers that you want to discover and assess must be managed by vCenter Server version 8.0, 7.0, 6.7, 6.5, 6.0, or 5.5.<br /><br /> Discovering servers by providing ESXi host details in the appliance currently isn't supported. <br /><br /> IPv6 addresses aren't supported for vCenter Server (for discovery and assessment of servers) and ESXi hosts (for replication of servers).
 Permissions | The Azure Migrate: Discovery and assessment tool requires a vCenter Server read-only account.<br /><br /> If you want to use the tool for software inventory, agentless dependency analysis, web apps, and SQL discovery, the account must have privileges for guest operations on VMware virtual machines (VMs).
 
+:::zone-end
+
+::: zone pivot="server-requirements"
+
 ## Server requirements
 
 VMware | Details
 --- | ---
 Operating systems | All Windows and Linux operating systems can be assessed for migration.
 Storage | Disks attached to SCSI, IDE, and SATA-based controllers are supported.
 
+:::zone-end
+
+::: zone pivot="migrate-appliance-requirements"
+
 ## Azure Migrate appliance requirements
 
 Azure Migrate and Modernize uses the [Azure Migrate appliance](migrate-appliance.md) for discovery and assessment. You can deploy the appliance as a server in your VMware environment by using a VMware Open Virtualization Appliance template imported into vCenter Server. You can also use a [PowerShell script](deploy-appliance-script.md). Learn more about [appliance requirements for VMware](migrate-appliance.md#appliance---vmware).
@@ -54,6 +56,11 @@ Here are more requirements for the appliance:
 - In Azure Government, you must deploy the appliance by using a [script](deploy-appliance-script-government.md).
 - The appliance must be able to access specific URLs in [public clouds](migrate-appliance.md#public-cloud-urls) and [government clouds](migrate-appliance.md#government-cloud-urls).
 
+:::zone-end
+
+
+::: zone pivot="port-access-requirements"
+
 ## Port access requirements
 
 Device | Connection
@@ -62,6 +69,11 @@ Azure Migrate appliance | Inbound connections on TCP port 3389 to allow remote d
 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.
 
+::: zone-end
+
+
+::: zone pivot="software-inventory-requirements"
+
 ## Software inventory requirements
 
 In addition to discovering servers, Azure Migrate: Discovery and assessment can perform software inventory on servers. Software inventory provides the list of applications, roles, and features running on Windows and Linux servers that are discovered by using Azure Migrate and Modernize. It allows you to identify and plan a migration path tailored for your on-premises workloads.
@@ -76,6 +88,10 @@ Server access | You can add multiple domain and nondomain (Windows/Linux) creden
 Port access | The Azure Migrate appliance must be able to connect to TCP port 443 on ESXi hosts running servers on which you want to perform software inventory. The server running vCenter Server returns an ESXi host connection to download the file that contains the details of the software inventory. <br /><br /> If you use domain credentials, the Azure Migrate appliance must be able to connect to the following TCP and UDP ports: <br /> <br />TCP 135 – RPC Endpoint<br />TCP 389 – LDAP<br />TCP 636 – LDAP SSL<br />TCP 445 – SMB<br />TCP/UDP 88 – Kerberos authentication<br />TCP/UDP 464 – Kerberos change operations
 Discovery | Software inventory is performed from vCenter Server by using VMware Tools installed on the servers.<br/><br/> The appliance gathers the information about the software inventory from the server running vCenter Server through vSphere APIs.<br/><br/> Software inventory is agentless. No agent is installed on the server, and the appliance doesn't connect directly to the servers.
 
+::: zone-end
+
+::: zone pivot="sql-server-instance-database-discovery-requirements"
+
 ## SQL Server instance and database discovery requirements
 
 [Software inventory](how-to-discover-applications.md) identifies SQL Server instances. The appliance attempts to connect to the respective SQL Server instances through the Windows authentication or SQL Server authentication credentials in the appliance configuration manager by using this information. The appliance can connect to only those SQL Server instances to which it has network line of sight. Software inventory by itself might not need network line of sight.
@@ -281,6 +297,10 @@ Use the following sample scripts to create a login and provision it with the nec
   --GO
    ```
 
+::: zone-end
+
+::: zone pivot="web-apps-discovery"
+
 ## Web apps discovery requirements
 
 [Software inventory](how-to-discover-applications.md) identifies the web server role existing on discovered servers. If a server has a web server installed, Azure Migrate and Modernize discovers web apps on the server.
@@ -300,6 +320,11 @@ Required privileges | Local admin. | Root or sudo user.
 > [!NOTE]
 > Data is always encrypted at rest and during transit.
 
+::: zone-end
+
+
+::: zone pivot="dependency-analysis-agentless-requirements"
+
 ## Dependency analysis requirements (agentless)
 
 [Dependency analysis](concepts-dependency-visualization.md) helps you analyze the dependencies between the discovered servers. You can easily visualize dependencies with a map view in an Azure Migrate project. You can use dependencies to group related servers for migration to Azure. The following table summarizes the requirements for setting up agentless dependency analysis.
@@ -316,6 +341,10 @@ Linux server access | A sudo user account with permissions to execute ls and net
 Port access | The Azure Migrate appliance must be able to connect to TCP port 443 on ESXi hosts running the servers that have dependencies you want to discover. The server running vCenter Server returns an ESXi host connection to download the file containing the dependency data.
 Discovery method |  Dependency information between servers is gathered by using VMware Tools installed on the server running vCenter Server.<br /><br /> The appliance gathers the information from the server by using vSphere APIs.<br /><br /> No agent is installed on the server, and the appliance doesn't connect directly to servers.
 
+::: zone-end
+
+::: zone pivot="dependency-analysis-agent-based-requirements"
+
 ## Dependency analysis requirements (agent-based)
 
 [Dependency analysis](concepts-dependency-visualization.md) helps you identify dependencies between on-premises servers that you want to assess and migrate to Azure. The following table summarizes the requirements for setting up agent-based dependency analysis.
@@ -332,6 +361,19 @@ Management | When you register agents to the workspace, use the ID and key provi
 Internet connectivity | If servers aren't connected to the internet, install the Log Analytics gateway on the servers.
 Azure Government | Agent-based dependency analysis isn't supported.
 
+::: zone-end
+
+## Limitations
+
+Requirement | Details
+--- | ---
+Project limits | You can create multiple Azure Migrate projects in an Azure subscription.<br /><br /> You can discover and assess up to 50,000 servers in a VMware environment in a single [project](migrate-support-matrix.md#project). A project can include physical servers and servers from a Hyper-V environment, up to the assessment limits.
+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 /> This amount is valid for Azure VMware Solution as well.
+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).
+
+
 ## Import servers by using RVTools XLSX (preview)
 
 As part of your migration journey to Azure by using the Azure Migrate appliance, you first discover servers, inventory, and workloads. However, for a quick assessment before you deploy the appliance, you can [import the servers by using the RVTools XLSX file (preview)](tutorial-import-vmware-using-rvtools-xlsx.md).
@@ -371,5 +413,5 @@ To get an accurate operating system suitability/readiness in Azure VM and Azure
 
 ## Next steps
 
-- Review [assessment best practices](best-practices-assessment.md).
-- Learn how to [prepare for a VMware assessment](./tutorial-discover-vmware.md).
+* Review [assessment best practices](best-practices-assessment.md).
+* Learn how to [prepare for a VMware assessment](./tutorial-discover-vmware.md).

articles/zone-pivot-groups.yml

@@ -3040,7 +3040,29 @@ groups:
     title: Chrome browser
   - id: firefox-browser
     title: Firefox browser
-
+# Owner: sudhirsneha
+- id: vmware-discovery-requirements
+  title: Requirements to discover and assess servers in VMware environment
+  prompt: Choose support requirements
+  pivots:
+  - id: vmware-requirements
+    title: VMware
+  - id: server-requirements
+    title: Server
+  - id: migrate-appliance-requirements
+    title: Azure Migrate appliance
+  - id: port-access-requirements
+    title: Port access
+  - id: software-inventory-requirements
+    title: Software inventory
+  - id: sql-server-instance-database-discovery-requirements
+    title: SQL Server instance and database discovery
+  - id: web-apps-discovery
+    title: Web apps discovery
+  - id: dependency-analysis-agentless-requirements
+    title: Dependency analysis Agentless
+  - id: dependency-analysis-agent-based-requirements
+    title: Dependency analysis Agent based
 # Owner: tejaswikolli-web
 - id: container-registry-zones
   title: Container registry ide
@@ -3049,4 +3071,4 @@ groups:
   - id: development-environment-azure-portal
     title: Portal 
   - id: development-environment-azure-cli
-    title: CLI
+    title: CLI