Skip to content

Commit 4a2fa40

Browse files
Merge pull request #249208 from Karthigasree/24Aug-Visualization
Agentless visualization update
2 parents 7047542 + 9df71cd commit 4a2fa40

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/migrate/concepts-dependency-visualization.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ The differences between agentless visualization and agent-based visualization ar
6767

6868
**Requirement** | **Agentless** | **Agent-based**
6969
--- | --- | ---
70-
**Support** | Available for VMware VMs in general availability (GA). | In general availability (GA).
70+
**Support** | Generally Available for VMware VMs, Hyper-V VMs, Physical servers, or servers running on other public clouds like AWS and GCP. | In general availability (GA).
7171
**Agent** | No agents needed on servers you want to analyze. | Agents required on each on-premises server that you want to analyze.
7272
**Log Analytics** | Not required. | Azure Migrate uses the [Service Map](/previous-versions/azure/azure-monitor/vm/service-map) solution in [Azure Monitor logs](../azure-monitor/logs/log-query-overview.md) for dependency analysis.<br/><br/> You associate a Log Analytics workspace with a project. The workspace must reside in the East US, Southeast Asia, or West Europe regions. The workspace must be in a region in which [Service Map is supported](../azure-monitor/vm/vminsights-configure-workspace.md#supported-regions).
7373
**Process** | Captures TCP connection data. After discovery, it gathers data at intervals of five minutes. | Service Map agents installed on a server gather data about TCP processes, and inbound/outbound connections for each process.

0 commit comments

Comments
 (0)