M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Dependency analysis

Concept

Dependency analysis observes which servers communicate with each other and groups them into applications, so connected workloads can be migrated together instead of being split by accident.

✦ CONCEPTDependency analysisM365.FM
Title graphic: Dependency analysis (Concept)

Also discussed

Episodes about Dependency analysis also cover Azure Migrate, Solution layers and GitHub Actions.

Description

Dependency analysis is a feature of Azure Migrate that identifies how discovered running servers depend on one another. It observes which servers communicate with each other and groups them into applications, so that connected workloads can be migrated together instead of being split by accident. The Microsoft Learn documentation describes it as applicable to on-premises servers in VMware and Hyper-V, physical servers, and servers in other public clouds.

The purpose is practical. Inspecting network dependencies makes it possible to group interdependent servers into applications and to find servers that have to be migrated together. This helps ensure that no component is overlooked and that outages after migration are avoided. Without such a view, a server that looks self-contained in an inventory may turn out to rely on another machine, and moving only one of the two can break the application once it is in the cloud.

Two options exist for collecting this information. The agentless option collects TCP connection data without installing agents on the servers. It relates a source server, process and port to a destination server, process and port as a logical dependency, and presents the result as a map view or as a CSV export. The Azure Migrate appliance polls the connection data, processes it locally and forwards it to the service in periodic batches. The agent-based option builds on the Service Map solution in Azure Monitor and needs an agent on every source server. According to the documentation, the agent-based option is only available in the classic experience, is not supported in Azure Government, and no new servers can be added to it.

The choice between the two therefore largely comes down to whether installing software on each source server is acceptable and which Azure Migrate experience is in use. The agentless approach avoids touching the servers themselves, while the agent-based approach depends on an older, restricted path. The M365.FM episode "Azure Migrate - Simply Explained" lists "Dependency Analysis" as one section of its walkthrough, next to discovery, assessment of readiness, sizing and cost, and a section on agentless versus agent-based approaches. The same outline also covers moving in waves and pitfalls to avoid. The episode's framing is that problems often arise before anyone opens the cloud portal, because nobody mapped what was connected to what.

That connection to wave planning is where dependency analysis typically feeds into decisions. Servers that belong to the same application are candidates for the same migration wave, while dependencies that cross wave boundaries are flagged for attention, for example regarding latency or connectivity during the transition. The grouping result becomes an input to assessment and scheduling rather than an end in itself.

The term also appears in a different context in the episode "Deploy Dynamics 365 Customizations with ALM Pipelines", where dependency analysis is named among tooling tips together with Solution Checker and configuration migration. There it is mentioned as one of the tools meant to prevent "works in dev, breaks in prod" problems during solution deployment. The episode excerpt does not elaborate on how it works in that setting, so the Azure Migrate meaning described above is the one documented in detail here.

In short, dependency analysis turns observed network traffic between servers into a map of relationships. That map supports grouping workloads into applications, deciding which servers must move together, and reducing the chance of post-migration outages caused by overlooked components.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeConcept

Key points about Dependency analysis

Key points about Dependency analysis from the episodes, each with its source episode:

Episodes about Dependency analysis

Episodes in which Dependency analysis is discussed:

Timeline of episodes about Dependency analysis

Articles about Dependency analysis (1)

Articles in which Dependency analysis is a topic:

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does dependency analysis do in Azure Migrate? (AI)

It identifies how discovered running servers depend on one another, groups interdependent servers into applications, and finds servers that have to be migrated together so that no component is overlooked.

What is the difference between agentless and agent-based dependency analysis? (AI)

The agentless option collects TCP connection data via the Azure Migrate appliance without installing agents and shows a map view or CSV export. The agent-based option uses the Service Map solution in Azure Monitor, needs an agent on every source server, is available only in the classic experience, and no new servers can be added to it.

Which environments does dependency analysis cover? (AI)

According to Microsoft Learn, it covers on-premises servers in VMware and Hyper-V, physical servers, and servers in other public clouds.

What does an Azure Migrate assessment cover?

An assessment covers readiness, sizing and cost: whether a workload is ready for the cloud, how it should be sized there and what it will cost. Dependency analysis, which maps what is connected to what, is a separate step. · From the episode: Azure Migrate - Simply Explained

Why is dependency analysis important in a migration?

Dependency analysis matters because the hard part of a migration usually comes from nobody having mapped what was connected to what. Seeing those connections before moving a server helps you avoid surprises, which is why the episode treats it as its own step. · From the episode: Azure Migrate - Simply Explained

Which tools support Dynamics 365 ALM pipelines?

Solution Checker and dependency analysis help find problems early, and Azure DevOps Pipelines or GitHub Actions run the automated deployments. Choose whichever suits your team's skills, since both support automation. · From the episode: Deploy Dynamics 365 Customizations with ALM Pipelines

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: