Content Understanding preview APIs (2024-12-01-preview, 2025-05-01-preview) returning HTTP 410 ApiVersionRetired ~4 weeks before the announced 15 July 2026 retirement date — is this a known early-retirement incident?

Jon Koh 40 Reputation points
2026-06-19T17:03:34.38+00:00

The official retirement notice (Service Health advisory, tracking ID LJB6-KHG) states that Azure

Content Understanding preview API versions 2024-12-01-preview and 2025-05-01-preview will be

retired on 15 July 2026, and: *"After 15 July 2026, these preview API versions will stop

functioning."*

As of 19 June 2026 — roughly four weeks before that date — both preview versions are already

returning HTTP 410 Gone:

GET https://<my-resource>.services.ai.azure.com/contentunderstanding/analyzers?api-version=2025-05-01-p

review

HTTP/2 410

x-ms-error-code: Gone

{
  "error": {
    "code": "Gone",
    "message": "The requested API version has been retired.",
    "innererror": {
      "code": "ApiVersionRetired",
      "message": "The requested API version has been retired. Please migrate to the latest GA version."
    }
  }
}

Confirmed:

  • Same 410 for api-version=2024-12-01-preview.
  • Same 410 on both the *.services.ai.azure.com and *.cognitiveservices.azure.com hosts.
  • GA api-version=2025-11-01 on the same resource returns HTTP 200 (so the resource itself is healthy — only the preview versions are gone).

This is a production outage for us — these preview APIs back a live document-processing pipeline,

and we were sequencing our GA migration against the published 15 July 2026 date.

Questions

  1. Is the early retirement (before 15 July 2026) a known incident? I'm aware GA 2025-11-01 is the

target — this question is specifically about the preview versions being pulled ahead of the committed

date, not how to migrate.

  1. Will the preview API versions be restored through the committed 15 July 2026 grace period per

advisory LJB6-KHG?

  1. If the retirement date was intentionally moved earlier, where is that change documented?
Azure Document Intelligence in Foundry Tools

Answer accepted by question author

Alex Burlachenko 23,575 Reputation points MVP Volunteer Moderator
2026-06-22T11:04:16.8033333+00:00

Hi

an early retirement or backend rollout issue rather than a problem with your resource. The fact that 2025-11-01 returns 200 OK on the same resource is the key detail. That tells me the resource, authentication, and endpoint are working. Only the preview API versions are returning 410 ApiVersionRetired.

Microsoft's migration guidance still says 2024-12-01-preview and 2025-05-01-preview retire on 15 July 2026 and recommends moving to 2025-11-01 GA https://learn.microsoft.com/en-us/azure/ai-services/content-understanding/how-to/migration-preview-to-ga since u are getting 410 almost four weeks before that date, I'd expect either an early rollout or a platform issue unless Microsoft published a newer retirement notice that supersedes LJB6-KHG.

I'd open a support case and reference the Service Health advisory ID, the resource ID, region, UTC timestamps, both preview API versions, and the ApiVersionRetired response. I'd specifically ask whether the preview versions were intentionally retired early, whether this is a known incident, and whether the published retirement date has changed.

& plan to move to 2025-11-01 as soon as possible, but I agree this is a separate question. If Microsoft committed to support the preview APIs until 15 July 2026, then returning 410 Gone on 19 June deserves an official explanation.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

Was this answer helpful?

1 person found this answer helpful.
0 comments

Answer accepted by question author

Anshika Varshney 14,095 Reputation points Microsoft External Staff Moderator
2026-06-19T17:39:45.6066667+00:00

Hello @Jon Koh

Thanks for reporting this, that 410 (ApiVersionRetired) appearing ~4 weeks before the announced July 15, 2026 retirement sounds like an unexpected early enforcement and could be either an accidental rollout or an intentional phased shutdown. MDN documents that 410 signals permanent removal, so clients should treat it as the API being unavailable until the service owner clarifies.

Please check Azure/Azure AI retirement notices or Service Health for any last-minute changes or phased retirements that can cause early 410 responses. [developer.mozilla]

What to do next:

  • Retry after clearing any caches and confirm the call is using the exact announced GA replacement version or a supported version; a 410 usually means the server has permanently disabled that API version.
  • Check the service’s retirement/what’s-new pages and the Azure REST specs for replacement endpoints or newer Content Understanding versions (the Content Understanding docs and specs list recent updates). [azure.github]
  • If you still see 410, open a support ticket or post an issue including request timestamps, full request URL (redact keys), and response headers so Microsoft can validate whether this was an accidental early disable or a staged retirement. Historical retirements have sometimes been phased or enforced early, so submitting telemetry helps Microsoft investigate and (if needed) roll back or provide guidance. [learn.microsoft]

I Hope this helps. Do let me know if you have any further queries.

Thankyou!

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.