Skip to content

Commit 55bb38a

Browse files
Merge pull request #264183 from guywi-ms/ama-migration-update
Add MMA migration tool to azure-monitor-agent-migration.md
2 parents bea9fd0 + 4bd5986 commit 55bb38a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/azure-monitor/agents/azure-monitor-agent-migration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,8 +79,10 @@ Before you begin migrating from the Log Analytics agent to Azure Monitor Agent,
7979
1. Check your workbooks, dashboards, and alerts for variances from typical behavior following the migration.
8080
8181
1. Clean up: After you confirm that Azure Monitor Agent is collecting data properly, **disable or uninstall the legacy Log Analytics agents**.
82-
- If you have need to continue using both agents, [disable data collection with the Log Analytics agent](./agent-data-sources.md#configure-data-sources).
83-
- If you've migrated to Azure Monitor Agent for all your requirements, [uninstall the Log Analytics agent](./agent-manage.md#uninstall-agent) from monitored resources. Clean up any configuration files, workspace keys, or certificates that were used previously by the Log Analytics agent. Continue using the legacy Log Analytics for features and solutions that Azure Monitor Agent doesn't support.
82+
83+
- If you've migrated to Azure Monitor Agent for all your requirements, [uninstall the Log Analytics agent](./agent-manage.md#uninstall-agent) from monitored resources. Clean up any configuration files, workspace keys, or certificates that were used previously by the Log Analytics agent. Continue using the legacy Log Analytics for features and solutions that Azure Monitor Agent doesn't support.
84+
85+
Use the [MMA removal tool](../agents/azure-monitor-agent-mma-removal-tool.md) to discovery and remove the Log Analytics agent extension from all machines within your tenant.
8486
- Don't uninstall the legacy agent if you need to use it to upload data to System Center Operations Manager.
8587
8688
<sup>1</sup> The DCR generator only converts the configurations for Windows event logs, Linux syslog and performance counters. Support for more features and solutions will be available soon

0 commit comments

Comments
 (0)