From a39d8ffa2ac745f57816893efd113c37013e9194 Mon Sep 17 00:00:00 2001 From: prijaisw <117013342+prijaisw@users.noreply.github.com> Date: Wed, 13 May 2026 09:38:58 +0530 Subject: [PATCH 1/2] Update migrate-support-matrix-physical.md --- .../migrate/migrate-support-matrix-physical.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/articles/migrate/migrate-support-matrix-physical.md b/articles/migrate/migrate-support-matrix-physical.md index 30bad672732a5..ea8cdc6f0c9d6 100644 --- a/articles/migrate/migrate-support-matrix-physical.md +++ b/articles/migrate/migrate-support-matrix-physical.md @@ -315,19 +315,9 @@ Discovery method | Agentless dependency analysis is performed by directly conne ## Agent-based dependency analysis requirements -[Dependency analysis](concepts-dependency-visualization.md) helps you to 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. Currently, only agent-based dependency analysis is supported for physical servers. +Azure Migrate recommends the use of agentless dependency analysis and no longer provides support for agent based dependency visualization. However, if you still want to use agent-based dependency visualization, you can directly install [Azure Monitor VM Insights](azure/azure-monitor/vm/monitor-vm) on each server that you want to analyze. -Requirement | Details ---- | --- -Before deployment | You should have a project in place with the Azure Migrate: Discovery and assessment tool added to the project.

You deploy dependency visualization after setting up an Azure Migrate appliance to discover your on-premises servers.

[Learn how](create-manage-projects.md) to create a project for the first time.
[Learn how](how-to-assess.md) to add an assessment tool to an existing project.
Learn how to set up the Azure Migrate appliance for assessment of [Hyper-V](how-to-set-up-appliance-hyper-v.md), [VMware](how-to-set-up-appliance-vmware.md), or physical servers. -Azure Government | Dependency visualization isn't available in Azure Government. -Log Analytics | Azure Migrate and Modernize uses the [Service Map](/previous-versions/azure/azure-monitor/vm/service-map) solution in [Azure Monitor logs](/azure/azure-monitor/logs/log-query-overview) for dependency visualization.

You associate a new or existing Log Analytics workspace with a project. You can't modify the workspace for a project after you add the workspace.

The workspace must be in the same subscription as the project.

The workspace must reside in the East US, Southeast Asia, or West Europe regions. Workspaces in other regions can't be associated with a project.
The workspace must be in a region in which [Service Map is supported](https://azure.microsoft.com/global-infrastructure/services/?products=monitor®ions=all). You can monitor Azure VMs in any region. The VMs themselves aren't limited to the regions supported by the Log Analytics workspace.

In Log Analytics, the workspace associated with Azure Migrate and Modernize is tagged with the Migration Project key and the project name. -Required agents | On each server that you want to analyze, install the following agents:
- [Microsoft Monitoring agent (MMA)](/azure/azure-monitor/agents/agent-windows)
- [Dependency agent](/azure/azure-monitor/vm/vminsights-dependency-agent-maintenance)

If on-premises servers aren't connected to the internet, you need to download and install the Log Analytics gateway on them.

Learn more about installing the [Dependency agent](how-to-create-group-machine-dependencies.md#install-the-dependency-agent) and [MMA](how-to-create-group-machine-dependencies.md#install-the-mma). -Log Analytics workspace | The workspace must be in the same subscription as a project.

Azure Migrate and Modernize supports workspaces residing in the East US, Southeast Asia, and West Europe regions.

The workspace must be in a region in which [Service Map is supported](https://azure.microsoft.com/global-infrastructure/services/?products=monitor®ions=all). You can monitor Azure VMs in any region. The VMs themselves aren't limited to the regions supported by the Log Analytics workspace.

You can't modify the workspace for a project after you add the workspace. -Costs | The Service Map solution doesn't incur any charges for the first 180 days. The count starts from the day that you associate the Log Analytics workspace with the project.

After 180 days, standard Log Analytics charges apply.

Using any solution other than Service Map in the associated Log Analytics workspace incurs [standard charges](https://azure.microsoft.com/pricing/details/log-analytics/) for Log Analytics.

When the project is deleted, the workspace isn't automatically deleted. After you delete the project, Service Map usage isn't free. Each node is charged according to the paid tier of the Log Analytics workspace.

If you have projects that you created before Azure Migrate general availability (GA on February 28, 2018), you might incur other Service Map charges. To ensure that you're charged only after 180 days, we recommend that you create a new project. Workspaces that were created before GA are still chargeable. -Management | When you register agents to the workspace, use the ID and key provided by the project.

You can use the Log Analytics workspace outside Azure Migrate and Modernize.

If you delete the associated project, the workspace isn't deleted automatically. [Delete it manually](/azure/azure-monitor/logs/manage-access).

Don't delete the workspace created by Azure Migrate and Modernize unless you delete the project. If you do, the dependency visualization functionality doesn't work as expected. -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. +Please note that agent-based dependency analysis is not free, and Log Analytics workspace usage charges will apply. For pricing details, see [Azure Monitor pricing](pricing/details/monitor/). ## Next steps From 20d7d6414bd76d29ca33d2f575d4c00d4073caa1 Mon Sep 17 00:00:00 2001 From: prijaisw <117013342+prijaisw@users.noreply.github.com> Date: Wed, 13 May 2026 14:47:31 +0530 Subject: [PATCH 2/2] Update migrate-support-matrix-physical.md --- articles/migrate/migrate-support-matrix-physical.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/migrate/migrate-support-matrix-physical.md b/articles/migrate/migrate-support-matrix-physical.md index ea8cdc6f0c9d6..dc097fdcfb3f4 100644 --- a/articles/migrate/migrate-support-matrix-physical.md +++ b/articles/migrate/migrate-support-matrix-physical.md @@ -315,9 +315,9 @@ Discovery method | Agentless dependency analysis is performed by directly conne ## Agent-based dependency analysis requirements -Azure Migrate recommends the use of agentless dependency analysis and no longer provides support for agent based dependency visualization. However, if you still want to use agent-based dependency visualization, you can directly install [Azure Monitor VM Insights](azure/azure-monitor/vm/monitor-vm) on each server that you want to analyze. +Azure Migrate recommends the use of agentless dependency analysis and no longer provides support for agent based dependency visualization. However, if you still want to use agent-based dependency visualization, you can directly install [Azure Monitor VM Insights](/azure/azure-monitor/vm/monitor-vm) on each server that you want to analyze. -Please note that agent-based dependency analysis is not free, and Log Analytics workspace usage charges will apply. For pricing details, see [Azure Monitor pricing](pricing/details/monitor/). +If you were using ServicMap for agent based dependency analysis, you should migrate from [Service Map](/azure/azure-monitor/vm/vminsights-migrate-from-service-map) to VM Insights as Service Map is retired. Note that agent-based dependency analysis is not free, and Log Analytics workspace usage charges will apply. For pricing details, see [Azure Monitor pricing](/pricing/details/monitor/). ## Next steps