Tools for migrating from Log Analytics Agent to Azure Monitor Agent

Azure Monitor Agent (AMA) replaces the Log Analytics Agent (MMA/OMS) for Windows and Linux virtual machines, scale sets, and on premise and Arc-enabled servers. The benefits of migrating to Azure Monitor Agent include enhanced security, cost-effectiveness, performance, manageability and reliability. This article explains how to use the AMA Migration Helper and DCR Config Generator tools to help automate and track the migration from Log Analytics Agent to Azure Monitor Agent.

Flow diagram that shows the steps involved in agent migration and how the migration tools help in generating DCRs and tracking the entire migration process.


Do not remove the legacy agents if being used by other Azure solutions or services. Use the migration helper to discover which solutions/services you use today.


The legacy Log Analytics agent will be deprecated by August 2024. Migrate to Azure Monitor agent before August 2024 to continue ingesting data.

Using AMA Migration Helper (preview)

AMA Migration Helper is a workbook-based Azure Monitor solution that helps you discover what to migrate and track progress as you move from Log Analytics Agent to Azure Monitor Agent. Use this single pane of glass view to expedite and track the status of your agent migration journey.

You can access the workbook here, or find it on the Azure portal (preview) under Monitor > Workbooks > Public Templates > Azure Monitor essentials > AMA Migration Helper.

Screenshot of the Azure Monitor Agent Migration Helper workbook. The screenshot highlights the Subscription and Workspace dropdowns and shows the Azure Virtual Machines tab, on which you can track which agent is deployed on each virtual machine.

Installing and using DCR Config Generator (preview)

Azure Monitor Agent relies only on data collection rules (DCRs) for configuration, whereas Log Analytics Agent inherits its configuration from Log Analytics workspaces.

Use the DCR Config Generator tool to parse Log Analytics Agent configuration from your workspaces and generate corresponding data collection rules automatically. You can then associate the rules to machines running the new agent using built-in association policies.


DCR Config Generator does not currently support additional configuration for Azure solutions or services dependent on Log Analytics Agent.


To install DCR Config Generator, you need:

  1. PowerShell version 5.1 or higher. We recommend using PowerShell version 7.1.3 or higher.
  2. Read access for the specified workspace resources.
  3. The Az Powershell module to pull workspace agent configuration information.
  4. The Azure credentials for running Connect-AzAccount and Select-AzSubscription, which set the context for the script to run.

To install DCR Config Generator:

  1. Download the PowerShell script.

  2. Run the script:

    Option 1:

     .\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath

    Option 2 (if you just want the DCR payload JSON file):

     $dcrJson = Get-DCRJson -ResourceGroupName $rgName -WorkspaceName $workspaceName -PlatformType $platformType $dcrJson | ConvertTo-Json -Depth 10 | Out-File "<filepath>\OutputFiles\dcr_output.json"


    Parameter Required? Description
    SubscriptionId Yes ID of the subscription that contains the target workspace.
    ResourceGroupName Yes Resource group that contains the target workspace.
    WorkspaceName Yes Name of the target workspace.
    DCRName Yes Name of the new DCR.
    Location Yes Region location for the new DCR.
    FolderPath No Path in which to save the new data collection rules. By default, Azure Monitor uses the current directory.
  3. Review the output data collection rules. The script can produce two types of ARM template files, depending on the agent configuration in the target workspace:

    • Windows ARM template and parameter files - if the target workspace contains Windows performance counters or Windows events.
    • Linux ARM template and parameter files - if the target workspace contains Linux performance counters or Linux Syslog events.
  4. Use the built-in rule association policies to associate the generated data collection rules with virtual machines running the new agent.