Azure Document Intelligence version

Lin, Joe 0 Reputation points
2026-07-30T23:16:27.1133333+00:00

AzureDocIntelligence,code : 427 and exception message:(Gone) The requested API version has been retired.\nCode: Gone\nMessage: The requested API version has been retired.

Azure Document Intelligence in Foundry Tools

3 answers

Sort by: Most helpful
  1. Sean Leino 65 Reputation points
    2026-07-31T16:11:22.2+00:00

    We had a "410: model has been retired" error that started showing up in our 3 year old .NET application that was using the Azure.AI.FormRecognizer SDK. After much searching and trial/error, we finally realized that we had our application built using a beta/preview version of the latest FormRecognizer SDK (v 4.1.0)! Once we upgraded to the latest SDK package, the error went away. In our case, the error was not really about the model itself but rather the SDK version. The somewhat misleading error message delayed a resolution. Posting this in case you may be running into a similar issue.

    Was this answer helpful?

    0 comments No comments

  2. Anshika Varshney 15,625 Reputation points Microsoft External Staff Moderator
    2026-07-31T00:50:13.31+00:00

    Hello @Lin, Joe

    The error message:

    427 / Gone - The requested API version has been retired

    indicates that your application is sending requests to an Azure Document Intelligence API version that is no longer supported.

    Troubleshooting steps:

    1. Check the API version configured in your REST calls or SDK.
    • Verify the api-version parameter being sent in the request.
      • If you're using a preview API version such as 2024-07-31-preview, 2024-02-29-preview, or 2023-10-31-preview, these versions have been retired, and requests may return a "Gone" error.
    1. Migrate to the current GA version
      • Microsoft recommends using Document Intelligence v4.0 (2024-11-30 GA) for new and existing workloads.
    2. Verify SDK versions
    • Ensure your SDK version supports the current API version.
      • Older SDKs may continue sending retired API versions unless explicitly configured.
      Review application configuration
        - Search your code, app settings, environment variables, and deployment pipelines for hardcoded API versions.
        
        
           - Update all references to use the supported API version.
        
           
           **Test using the latest endpoint**
        
           
              - After updating the API version, validate your requests using a simple document analysis call to confirm the service responds successfully.
        ```If the issue persists after updating to the supported API version, please share:
      
      
    • The API version currently being used

    REST request sample (excluding keys/secrets) SDK language and version

    This will help further narrow down the cause.

    If you still face problems, share additional details and we’ll assist further.

    Follow the detailed migration guidance to move to Azure Document Intelligence API version v4.0

    Thankyou!

    Was this answer helpful?

    0 comments No comments

  3. AI answer

    2026-07-30T23:16:48.07+00:00

    HTTP 410 / Gone with The requested API version has been retired means the API version in the request is no longer supported by Azure Document Intelligence.

    For Azure Document Intelligence:

    • v2.1 end of support: September 15, 2027
    • v3.0 (2022-08-31) end of support: March 30, 2029
    • v4.0 (2024-11-30) is the current GA version

    Recommended action:

    1. Check the api-version value in the REST call or SDK configuration.
    2. If the request is using an older or retired version, update it to 2024-11-30 v4.0.
    3. If the application is on v3.0, it can move directly to v4.0 by using the current language-specific SDK and the 2024-11-30 REST API.
    4. If this started suddenly across a previously working deployment, also check for a service issue in Azure status or Azure Service Health.

    If Java SDK is being used, note that:

    • azure-ai-documentintelligence 1.0.0 supports 2024-11-30
    • version 1.0.7 of the Java library defaults to 2024-07-31-preview unless configured otherwise

    If .NET or Python SDK is being used and more detail is needed, enable SDK logging to capture the exact request version being sent:

    • .NET throws RequestFailedException with the service HTTP status code.
    • Python can enable logging / logging_enable for request details. Be careful with Python DEBUG logging because it can include unredacted headers.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.