HTTP Data Collector API - Hard Stop or End Support

Question

HTTP Data Collector API - Hard Stop or End Support

Babeu, Iain 1

I'm trying to clarify if the HTTP Data Collector API feature that is being deprecated will stop working completely on 14 September 2026, or if only support will end.

The learn page says support ends: https://learn.microsoft.com/en-us/previous-versions/azure/azure-monitor/logs/data-collector-api?tabs=powershell

The retirement announcement states that ingestion will stop working: https://azure.microsoft.com/en-us/updates/?id=azure-monitor-data-collection-api-retirement

I'm working under the assumption that ingestion stops completely, but I've had the question raised and I can't confirm it either way.

Suchitra Suregaunkar 14,425 Reputation points Microsoft External Staff Moderator

2026-06-05T23:13:12.3166667+00:00

Hello Babeu, Iain

Thank you for posting your query on Microsoft Q&A platform.

We are looking into this issue and will keep you posted updates.

Thanks,

Suchitra.
Suchitra Suregaunkar 14,425 Reputation points Microsoft External Staff Moderator

2026-06-05T23:25:14.3033333+00:00
Hello Babeu, Iain

The most definitive and recently updated source on this is the official migration guide, which clearly states:

"Support for the legacy Data Collector API ends September 14, 2026. Existing ingestion continues to work, but the API only receives critical security fixes."

It further clarifies:

"Two dates affect Data Collector API ingestion. On March 1, 2026, the API endpoint stopped accepting legacy TLS versions; clients that don't negotiate TLS 1.2 or later can't ingest data. On September 14, 2026, the API is deprecated but ingestion continues for TLS compliant clients."

So, to directly answer your question — September 14, 2026 is not a hard stop for ingestion. Data ingestion will continue to work for clients that are using TLS 1.2 or later. What ends on that date is official support, meaning no new features and no bug fixes only critical security patches.

That said, Microsoft is not committing to keeping the legacy endpoint running indefinitely beyond that date. Since the API will be unsupported with no SLA coverage, it's strongly recommended to migrate to the Logs Ingestion API with DCR-based ingestion as soon as possible to avoid any risk of disruption down the line.

Official documentation for reference:

Migrate from the HTTP Data Collector API to the Logs Ingestion API — this is the primary migration guide with the clearest language on what happens on September 14, 2026. [learn.microsoft.com]

Hope this clears things up. Please feel free to reach out if you have any further questions.

Thanks,

Suchitra.