Retirement Announcement - Start using the Azure Monitor agent instead of the Log Analytics agent before 31 August 2024

tbgangav-MSFT 10,416

On 31 August 2024, we'll retire the Log Analytics agent that you use in Azure Monitor. Before that date, you'll need to start using the Azure Monitor agent to monitor your VMs and servers in Azure. If you have a question, please post it in this thread.

Darpan Sachania (MINDTREE LIMITED) 1 Reputation point Microsoft Vendor

2021-08-26T08:01:41.853+00:00
Hi Team,

I received a notification for action on this ask.

Had a few queries relating to this.

As part of Security, we are advised to enable auto-provisioning of agents via the Azure security centre. This results in automatically deploying the agent on future VM deployments.

I noticed the log analytics workspace also picks up Backend VMs from PaaS services like Azure Databricks and Azure Kubernetes clusters. Are these PaaS VMs excluded from the ask?

The migration is only in relation to VMs monitored via MMA agent and not resulting in deprecating the Log analytics workspace altogether, does this apply to other services used like for monitoring WebApps, ADB via Log analytics?

Would love to get to know more about this perspective.

Thank you,
Darpan.Sachania
Philip Skov Knudsen 6 Reputation points

2021-09-01T08:48:28.887+00:00

What license is Azure Monitor agent released under? Is it Open Source? I can't find the source code on github, like the other agents we are using.
Mike Estes 6 Reputation points

2021-09-02T17:54:22.187+00:00

Is there a query that can be used in the Azure portal to determine which sources might be using this particular agent? I "think" I know which servers this might be but not 100% sure whether someone else installed it manually on a server or might be using it outside of the scope of the servers we maintain.

And perhaps list the installed application name we might find in Add/Remove Programs? Unfortunately the tools related to Azure Monitor and Azure Application Insights have many various names and it's hard to tell which one specifically is being referred to here and which one not to use.

I believe the installer was named something like "MMA*.exe" and the application name is called "Microsoft Monitoring Agent" in add/remove programs but want to be sure of what we're supposed to remove as it is called "Log Analytics agent" here.
Luke Kim 16 Reputation points Microsoft Employee

2021-09-02T22:15:36.873+00:00

The Agent being retired if the Log Analytics Agent, which has historically been referred to as MMA (Windows) and OMS (Linux). The Agent can be used to monitor different compute/node types - but all scenarios (not just basic VMs) apply to this retirement in 2024.
Luke Kim 16 Reputation points Microsoft Employee

2021-09-09T21:18:14.78+00:00

Within your workspace you can query to see if you have any heartbeat events. These are regularly sent by the agent to monitor agent health and connectivity. If you do see these events recently, it is most likely you have agents running and sending data to Azure.

The agents here are MMA (Windows) and OMS (Linux).
Luke Kim 16 Reputation points Microsoft Employee

2021-09-09T21:18:28.94+00:00

The Azure Monitor Agent is not open source.
Mike Estes 6 Reputation points

2021-09-10T22:55:47.683+00:00
Thank you, so none of the other agents send those, right?

It looks like we have some installed elsewhere when using this query.

Heartbeat | summarize arg_max(TimeGenerated, *) by SourceComputerId | sort by Computer | render table

We are trying to set up an agent to send metrics and other logs to Azure Monitor for our On Prem servers and the documentation isn't clear on which things will work for both Windows and Unix/Ubuntu servers. The one document I've found indicates that this component here that we're being asked to remove is the one it says to use.

https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agents-overview#windows-agents

We're not using Azure-Arc for managing our on prem servers and don't plan to, though perhaps I'm misunderstanding what that's for. "Diagnostics Extension (WAD) doesn't seem to mention on prem support. Log Analytics agent is the one being decommissioned here. And Dependency agent says it requires Log Analytics to work.

For some IIS instances we can use Azure Application Monitor, but it only sees to support IIS and obviously doesn't support unix.
https://learn.microsoft.com/en-us/azure/azure-monitor/app/status-monitor-v2-overview

We can use Application Insights SDK for other Windows Services and Windows Web Services, but again, that's not useful for unix and requires code changes to make work. We'll eventually get there but getting metrics and logs into Azure was a first step.
Sébastien Larivière 1 Reputation point

2022-04-12T17:23:27.3+00:00

We are using MMA agent on Windows 10/11 computers that are not virtual machine.
The Azure Monitor agent is only available as a virtual machine extension. On hybrid machines, i have read that we need to use Azure Arc to deploy the Azure Monitor agent but that software is not compatible with Windows 10/11.

What will be the replacement for us ?
Alex U 21 Reputation points

2022-07-07T14:26:46.08+00:00

We are using the MMA with Azure Automation Account Update Management and I cannot find any mention if Azure Monitoring Agent supports/or will support Update Management feature.

Do you have any information about support of the Update Management with Azure Automation Account feature by AMA?
If the feature of Update Management with Azure Automation Account is not in the roadmap, then what is the future supported scenario for this functionality when MMA is retired?
Ben Edmunds 5 Reputation points

2023-01-21T13:34:40.3833333+00:00

We also need to understand what is happening to the update management component provided within an automation account. We use this extensively and utilise the pre and post script options heavily for running updates across our estate withe the pre/post scripts taking care of graceful stops and starts to our services.

We have looked to the new update management preview but it does not allow the pre/post script options, What is the migration path for this use case as this is quite a large feature to drop when moving to the new agent offering

It would be great to know if this is on the road map?
Jordan W 5 Reputation points

2023-06-01T22:05:27.2266667+00:00

We are evaluating Azure Monitor for a network that does not have direct internet access. Some of my co-workers believe that log analytics gateway will be retired when log analytics agent is retired. Can anyone provide clarification on this?
Nowak, Jonathan (415) 5 Reputation points

2024-04-05T06:15:45.6366667+00:00

Are there any specific migration details for AKS?

I'm a bit confused, since the Terraform provider is still referring to "oms_agent" and there is no hint about an "Azure Monitor Agent".

https://registry.terraform.io/providers/hashicorp/azurerm/3.98.0/docs/resources/kubernetes_cluster
Hoeneveld, T.A. (Tim) 50 Reputation points

2024-04-12T09:17:47.3966667+00:00

Hi,

What will happen to VM's that are currently using the MMA after 31 August 2024?
Will the MMA no longer work? I am unable to find this anywhere on the MS documentation.
William Bradley 10 Reputation points Microsoft Employee

2024-06-25T15:16:13.6233333+00:00

I'm also unsure what action (if any) is needed for AKS clusters. I use Bicep to deploy AKS clusters and specify an "omsagent" add-on profile (https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#managedclusterpropertiesaddonprofiles).

However, my clusters appear to be using Azure Monitor Agent already - in my Log Analytics Workspace under "Agents", it says they are connected by Azure Monitor Agent. Also, if I list the pods on my cluster, there are pods starting with "ama-logs". Is there any action required on my part?

I can see the Bicep reference has an Azure Monitor profile (https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/managedclusters?pivots=deployment-language-bicep#managedclusterazuremonitorprofilecontainerinsights) - is this something we should use instead, or is the omsagent add-on profile still OK?
Kanduru, Krishnamurthy (ADM) 0 Reputation points

2024-08-29T10:19:40.0733333+00:00

Hi Team,
if I migrated the Log Analytics workspaces to Create an Azure Monitor workspace, does it impacts existing functionality that are associated with Log Analytics workspaces since we have many resource groups. Can we check the jobs/pipelines/activities running related to it in the resource groups available for client so that we can change them accordingly to azure monitor workspace migration.

Accepted answer

bharathn-msft 5,096 Reputation points Microsoft Employee

2021-08-25T05:36:52.493+00:00

Learn more from this migration document.

If you have any additional queries regarding this retirement, please use comments on this thread to ask your specific queries and we will try our best to answer those queries. Thank you
Please sign in to rate this answer.
Racheal 6 Reputation points

2024-02-27T08:28:10.2166667+00:00

Hi , Does this migration will affect only the logs collected through MMA and will not affect log analytics workspace ? we are using application insight which is log analytics workspace based to send logs to azure .. Will there be any impact on that side ?

Racheal 6 Reputation points

2024-02-27T08:30:52.65+00:00

Hi @bharathn-msft , Does this migration will affect only the logs collected through MMA and will not affect log analytics workspace ? we are using application insight which is log analytics workspace based to send logs to azure .. Will there be any impact on that side…

Radovan Drabik 0 Reputation points

2024-09-19T10:02:09.0266667+00:00

Hello. What improvements is brought with AMA compared with previous MMA?

I got such question from my customer.

Thanks for your response
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

3 additional answers

Racheal 236 Reputation points

2022-12-20T12:13:09.657+00:00

Hi,

we are using application insight as workspace based . what will happen to workspace based application insights if log analytics retired ?
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Firoz Basha 0 Reputation points

2024-03-06T13:49:01.5433333+00:00

Hello , is it only connected to/going to affect the VMs and Servers or else does it also affects the other resources such as Azure APIM , Application Gateways, App Services, Azure Front Door and Azure functions etc.?
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Wadih Rizk (Wunderman) 0 Reputation points Microsoft Vendor

2024-08-20T10:52:48.9733333+00:00
Hi,

We have received the below, we do not have a VM on this Subscription, what we have is a single SQL server, what are the steps to remediate? Thank you.

Start using the Azure Monitor agent instead of the Log Analytics agent before 31 August 2024

You're receiving this email because you use the Log Analytics agent to monitor your virtual machines (VMs) or servers.

On 31 August 2024, we'll retire the Log Analytics agent that you use in Azure Monitor. Before that date, you'll need to start using the Azure Monitor agent to monitor your VMs and servers in Azure. The Azure Monitor agent provides new features and capabilities, including:

Centralized configuration for multiple VMs.

Data limits and filters at the source.

Multiple destinations for data from a single agent.

Required action

Follow the migration instructions to start using the Azure Monitor agent to monitor your VMs and servers before 31 August 2024.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Retirement Announcement - Start using the Azure Monitor agent instead of the Log Analytics agent before 31 August 2024

3 additional answers

Your answer