How can I tell if I need to migrate to Azure Monitor Agent?

Question

How can I tell if I need to migrate to Azure Monitor Agent?

BB 45

How can I tell if i need to migrated to Azure Monitor Agent? And if so, what components need to be migrated and how?

Thank you

Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-19T00:34:46.6333333+00:00

Hello BB

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

We are looking into your issue and will keep you posted updates.

Thanks,

Suchitra,

Answer accepted by question author

0 additional answers

Your answer

Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-19T00:34:46.6333333+00:00

Hello BB

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

We are looking into your issue and will keep you posted updates.

Thanks,

Suchitra,

Answer 1

Suchitra Suregaunkar 11,815 Microsoft External Staff Moderator

Hello BB

You must migrate to Azure Monitor Agent if any of the following are true in your environment:

You are using the Log Analytics agent (MMA/OMS):

The Log Analytics agent (MMA/OMS) was retired on August 31, 2024
Microsoft has removed portal installation and no longer supports MMA
Cloud ingestion services for MMA can stop at any time after March 2, 2026

If your VMs or servers still have:

Microsoft Monitoring Agent (MMA) on Windows
OMS Agent on Linux

→ Migration to AMA is required.

Your machines send data to Log Analytics using legacy agents:

If logs or metrics are coming from:

Azure VMs
Azure Arc–enabled servers
On‑prem or other‑cloud servers

and they report via MMA/OMS, then those machines must be migrated to AMA.

Reference: https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-migration

You use services that now depend on AMA:

These Azure services no longer rely on MMA and require AMA instead:

Azure Monitor (Logs, Metrics, VM Insights)
Microsoft Sentinel
Defender for Cloud (Servers)
Change Tracking & Inventory (new version)
Azure Update Manager
Container insights (agent-based)

If any of these are in use → AMA is required.

Please have a look into below components need to be migrated:

When migrating, you are not just replacing an agent. The following components change:

Agent:

LegacyReplacementMMA / OMS agentAzure Monitor Agent (AMA)----------------MMA / OMS agent**Azure Monitor Agent (AMA)**AMA is installed as:

AzureMonitorWindowsAgent
AzureMonitorLinuxAgent

Data collection configuration:

Legacy agents used workspace‑level settings. AMA uses Data Collection Rules (DCRs).

You must migrate:

Windows Event Logs
Linux syslog
Performance counters
Custom logs
IIS / text-based logs

All are redefined using DCRs, not workspace settings. [learn.microsoft.com]

Non‑Azure / on‑prem servers:

For non‑Azure machines:

Azure Arc agent is mandatory
AMA is deployed after Arc onboarding

This is required for AMA to function on on‑prem or other‑cloud servers.

Please have a look into below shared steps:

Step 1: Identify legacy agents

Find machines with MMA/OMS installed
Check which Log Analytics workspaces they report to

Microsoft provides:

AMA Migration Helper Workbook
DCR Config Generator to assist with discovery and mapping.

Step 2: Create Data Collection Rules (DCRs):

Recreate existing data collection (events, counters, logs)
Point DCRs to the same Log Analytics workspace(s)
Validate that AMA supports each data source you collect.

Step 3: Deploy AMA:

Install AMA on Azure VMs, VMSS, and Arc-enabled servers
Use Azure Policy for scale and auto‑deployment
Associate machines with the correct DCRs. [learn.microsoft.com]

AMA and MMA can coexist temporarily, but duplicate ingestion must be avoided.

Step 4: Validate data:

Compare incoming data from AMA vs legacy agent
Confirm dashboards, alerts, and queries still work
Ensure no duplicate data ingestion occurs.

Step 5: Remove legacy agents:

Uninstall MMA/OMS once validation is complete
Microsoft provides an MMA removal tool for large environments.

Official Microsoft reference:

Migrate to Azure Monitor Agent from Log Analytics agent https://learn.microsoft.com/azure/azure-monitor/agents/azure-monitor-agent-migration.

If any machine in your environment still uses the Log Analytics (MMA/OMS) agent, migration to Azure Monitor Agent is required. AMA replaces MMA, uses Data Collection Rules instead of workspace settings, and is mandatory for Azure Monitor, Defender for Cloud, and Microsoft Sentinel going forward. Migration involves identifying legacy agents, recreating data collection with DCRs, deploying AMA, validating telemetry, and then removing the legacy agents.

If the answer is helpful, could you please click "upvote" it .

If you’re still experiencing the problem or need further clarification, please feel free to share additional information so we can continue investigating and assist you further.

Thanks,

Suchitra.

Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-19T18:40:15.4533333+00:00

Hello BB

If the answer is helpful, could you please click "Accept Answer" & "upvote" it and this helps other community members who may encounter a similar issue in the future.

If you’re still experiencing the problem or need further clarification, please feel free to share additional information so we can continue investigating and assist you further.

Thanks,

Suchitra.
BB 45 Reputation points

2026-03-21T16:23:08.3933333+00:00
How can I tell the following:

I am using the Log Analytics agent (MMA/OMS)

My machine send data to Log Analytics using legacy agents

I am using services that now depend on AMA

As you can tell, I am a novice at this. Thank you.
BB 45 Reputation points

2026-03-21T16:25:20.96+00:00
How can I tell the following:

I am using the Log Analytics agent (MMA/OMS)

My machine send data to Log Analytics using legacy agents

I am using services that now depend on AMA

As you can tell, I am a novice at this. Thank you.
Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-23T20:56:04.8833333+00:00
Hello BB

Please have a look into below provided steps to get answer for your follow up questions:

How can I tell if I’m using the Log Analytics agent (MMA / OMS)?

Sign in to Azure Portal

Go to Virtual Machines

Open one VM

In the left menu, click Extensions + applications

If you see ANY of the following extensions, you are using the legacy agent:

Extension name you see:

MeaningMicrosoftMonitoringAgent-- Legacy MMA (Windows)

OmsAgentForLinux -- Legacy OMS (Linux)

If you see these → migration to AMA is required.

If instead you see AzureMonitorWindowsAgent or AzureMonitorLinuxAgent as shown in the below screenshot then it means VM is already using Azure Monitor Agent.

You can also verify using azure monitor.

Go to Azure monitor -> Logs -> Select your Logs Analytics Workspace or Scope it to your Subscription and run the below query as shown in the screenshot.

If you see:

Direct Agent → Legacy MMA/OMS

Azure Monitor Agent → AMA

Presence of Direct Agent means you are still using legacy agents, If it shows as Azure Monitor Agent then AMA is installed.

My machine send data to Log Analytics using legacy agents.

To verify this If both are true:

The VM has MicrosoftMonitoringAgent or OmsAgentForLinux

The VM reports to a Log Analytics workspace

Then the machine is sending data using legacy agents

Go to Log Analytics workspace

Click Agents → Virtual machines

You’ll see a list of machines connected via:

Log Analytics agent (legacy) or

Azure Monitor Agent

If the machine is listed under Log Analytics agent, it must be migrated.

Or If you see list of machines connected via AMA as shown in the below screenshot then it is already migrated to AMA.

How can I tell if I’m using services that now depend on AMA?

Check your workspace “Solutions” tab

Open your Log Analytics workspace

Click Legacy solutions or Solutions

If you see any of these, they now require AMA:

VMInsights

ContainerInsights

Microsoft Sentinel

ChangeTracking

UpdateManagement

Defender for Cloud

Check whether you are using any of the following services.

If the answer is yes to even one, AMA is required.

Check in the Azure portal:

VM Insights > VM → Insights

Azure Monitor (Logs/Metrics) > Log Analytics workspace in use

Microsoft Sentinel > Sentinel enabled on workspace

Defender for Cloud (Servers) > Defender for Cloud → Environment settings

Change Tracking & Inventory (new) Automation / Monitor

Azure Update Manager > Update Manager blade

Container Insights (agent-based) > AKS / Monitor

All of these services no longer rely on MMA and require Azure Monitor Agent.

Thanks,
Suchitra.
BB 45 Reputation points

2026-03-24T17:03:39.73+00:00

Suchitra,

Looks like I need to migrate to AMA. Please confirm based on the following information.

Following your instructions, I found the following:

I see MiscrosoftMonitoringAgent in the Extensions:

I also see Direct Agent in the Logs Analytics Workspace:

I see this as well:

I see this in the Legacy Solutions:
Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-24T19:35:37.6666667+00:00
Hello BB

Thanks for responding back.

Based on the checks you performed, this environment is currently using the legacy Log Analytics agent (MMA/OMS) and therefore must be migrated to Azure Monitor Agent (AMA).

Here is what we confirmed:

The virtual machine has MicrosoftMonitoringAgent installed. This is the legacy Log Analytics agent, which Microsoft retired on August 31, 2024 and no longer supports.

The Log Analytics workspace shows data coming from a “Direct Agent”. This confirms that the machine is actively sending data using the legacy ingestion pipeline.

The workspace contains legacy solutions (for example Update Management / SecurityCenter / VM diagnostics), which have now moved to Azure Monitor Agent–based collection.

Because of the above, continuing to use the legacy agent is not supported, and data ingestion may stop without notice. Microsoft requires migration to Azure Monitor Agent to remain supported and to ensure monitoring and security features continue to function.

Microsoft has retired the Log Analytics agent and no longer supports it. Azure Monitor Agent is now the only supported agent for Azure Monitor, Defender for Cloud, and related services.

To remediate this, the following actions are required:

Deploy Azure Monitor Agent (AMA) on the affected machines

Create Data Collection Rules (DCRs) to define what logs and metrics are collected

Validate that data is successfully flowing via AMA

Remove the MicrosoftMonitoringAgent after validation to avoid duplicate data and charges

This is a supported, Microsoft‑recommended migration path and does not require rebuilding the virtual machines or Log Analytics workspace.

Please refer below document for detailed explanation on Migrate to Azure Monitor Agent from Log Analytics agent
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/azure-monitor-agent-migration

I hope the details shared above helped in addressing your concern.

If you’re still experiencing the problem or need further clarification, please feel free to share additional information so we can continue investigating and assist you further.

Thanks,

Suchitra.
Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-25T19:05:59.1833333+00:00

Hello BB

I hope the details shared above helped in addressing your concern.

If the suggested resolution resolved the issue, kindly consider marking the answer as "Accepted" and "Upvote" it. This helps other community members who may encounter a similar issue in the future.

If you’re still experiencing the problem or need further clarification, please feel free to share additional information so we can continue investigating and assist you further.

Thanks,

Suchitra.
BB 45 Reputation points

2026-03-25T20:03:26.4+00:00

Thank you for the assistance!
BB 45 Reputation points

2026-03-27T17:58:48.54+00:00

Also, what will happen if i do not migrate right away?
Suchitra Suregaunkar 11,815 Reputation points Microsoft External Staff Moderator

2026-03-27T19:06:28.3433333+00:00
Hello BB

The Log Analytics (MMA/OMS) agent is retired and no longer supported by Microsoft. If migration to Azure Monitor Agent is delayed, data ingestion may stop without notice, monitoring‑dependent services may degrade, and Microsoft Support may require migration before assisting. To remain supported and avoid monitoring gaps, migration to Azure Monitor Agent is strongly recommended.

Your VM will not shut down

Your existing data will not be deleted

You can migrate without downtime if done correctly.

However, monitoring reliability is no longer guaranteed, and failures may occur without recovery options.

Thanks,
Suchitra.
BB 45 Reputation points

2026-03-27T20:31:55.31+00:00

Thank you.

Share via

How can I tell if I need to migrate to Azure Monitor Agent?

0 additional answers

Your answer