Skip to content

Commit 35241de

Browse files
Update azure-monitor-agent-migration.md
1 parent 6d5c60a commit 35241de

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,9 @@ ms.date: 08/13/2024
1818
Migration is a complex task. Start planning your migration to Azure Monitor Agent using the information in this article as a guide.
1919

2020
> [!IMPORTANT]
21-
> The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). You can expect the following when you use the MMA or OMS agent after this date.
21+
> The Log Analytics agent will be [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). The depreciation does not apply to MMA agent connected exclusively to an On-Prem SCOM installation.
22+
>
23+
> You can expect the following when you use the MMA or OMS agent after August 31, 2024.
2224
> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time. Ingestion for MMA will be unchanged until February 1 2025.
2325
> - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
2426
> - **Customer Support:** You will not be able to get support for legacy agent issues.

0 commit comments

Comments
 (0)