new experience of Azure Migrate include Agent-based dependencies Analysis?

Hello nuage compte

Thank you for posting your query on Microsoft Q&A platform.

Agent-based dependency analysis is fully supported and integrated into the new Azure Migrate experience within the Discovery and assessment tool. It’s not deprecated; it just uses updated agents.

For agent-based analysis, Azure Migrate: Discovery and assessment uses the Service Map solution in Azure Monitor. You install the Microsoft Monitoring Agent/Log Analytics agent and the Dependency agent, on each server you want to analyze.

Reference: https://free.blessedness.top/en-us/azure/migrate/how-to-create-group-machine-dependencies?view=migrate

Thanks,

Suchitra.

Hi nuage compte, Thanks for your follow up

As we know Azure Migrate agent-based dependency analysis relies on Service Map in Azure Monitor, which collects data through:

• Log Analytics (MMA/OMS) agent
• Dependency agent

Service Map will be retired on September 30, 2025. To monitor connections between servers, processes, inbound and outbound connection latency, and ports across any TCP-connected architecture, make sure to migrate to Azure Monitor VM insights before this date.

Since Service Map is being retired:

• You can still use it until 30 Sept 2025 (if your subscription was already onboarded before Aug 31, 2024).
• You won't be able to onboard new subscriptions to service map after 31 August 2024. The Service Map UI won't be available after 30 September 2025
• But new Azure Migrate projects/subscriptions can’t enable agent-based dependency mapping anymore after that onboarding deadline.

Refer: Use the Service Map solution in Azure - Azure Monitor | Microsoft Learn

No agent-based dependency analysis no longer exists in the new Azure Migrate experience for new subscriptions. It used to be available through the Service Map integration (Log Analytics + Dependency Agent), but Microsoft has retired Service Map onboarding.

Referral documents:

• Migrate from Service Map to Azure Monitor VM insights - Azure Monitor | Microsoft Learn

Given the upcoming retirement of Service Map, the recommended approach for dependency analysis in Azure Migrate is to use the agentless method, which offers several advantages and continues to be supported in the new Azure Migrate experience.

Use the new Azure Migrate experience, which continues to support discovery, assessment, and agentless dependency analysis, while preparing to align with VM Insights for deeper visibility.

I hope this helps do let me know if you have any questions on this

Hello nuage compte, just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. 

Hi nuage compte, following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. 

Hi and thanks for your answer. So Contrary to the first answer of the other internaut, the agentless approach is only supported.

Understand that.

I still have another question please.

Before, when doing discovery. we see apps and SQL DB that Exists, in new experience, what Can I do to see apps and SQL DB in discovery phase? I am talking about the physical, the Vmware and the Hyper-V environement?