AzureRetirement
Azure Monitor: Data Collector API retirement
Retirement date for the Data Collector API used to ingest custom logs into Azure Monitor logs: 14 Sep 2026. Microsoft names the Data Collection Rules based Log Ingestion API as the replacement.
Retired , 14 Sep 2026
What breaks
Clients that send custom logs to Azure Monitor logs through the Data Collector API are affected. Data Collector API endpoints become unavailable after the retirement date. The source warns of ingestion errors and data loss for clients that have not transitioned.
What to do
Transition to the DCR-based Log Ingestion API before the retirement date, using the Microsoft guide: transition to the DCR-based Log Ingestion API.
Replacement
DCR-based Log Ingestion API
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourceaka.msOfficial
Last checked against the first source in this list on .
Related
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 15 Sep 2026Azure Monitor: Activity Logs legacy solution 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