AzureRetirement
Azure Monitor: Activity Logs legacy solution retirement
The Azure Activity Logs legacy solution is retired and replaced by Diagnostic settings. The source gives 15 March 2026 as the date the legacy flow stops working and all customers are auto migrated, and a manual move period through 15 Sep 2026.
Retired , 15 Sep 2026
What breaks
The Azure Activity logs solution, which forwarded Activity Logs to Azure Log Analytics, EventHub and storage, is retired and automatically converted to Diagnostic settings. The source gives 15 March 2026 as the deprecation date, when all customers are auto migrated and the legacy flow stops working, and a manual move period through 15 Sep 2026. Automation that enables or disables the connector using the Legacy API is not supported and has to be recreated using the new API.
What to do
- Move manually to Diagnostic settings as explained in the legacy collection methods documentation.
- If automation enables or disables the connector using the Legacy API, recreate it using the new API.
Replacement
Diagnostic settings
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
Last checked against the first source in this list on .
Related
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 14 Sep 2026Azure Monitor: Data Collector API retirementSource
- , 30 Sep 2026Azure Monitor SCOM Managed Instance retirementSource
- , 30 Sep 2026Azure Monitor: Container insights ContainerLog table retirementSource
- , 30 Sep 2026Azure Monitor: Container Insights legacy authentication retirementSource
- , 30 Sep 2026Azure Monitor: GetAlertSummary API retirementSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item