Share via

Azure Document Intelligence, API 2024-11-30 does not work

KYOUNGTAEK OH 0 Reputation points
2026-05-26T22:43:31.0666667+00:00

Suddenly, API version, 2024-11-30 does not work.

User's image

Azure Document Intelligence in Foundry Tools

2 answers

Sort by: Most helpful
  1. Alex Burlachenko 22,120 Reputation points MVP Volunteer Moderator
    2026-05-29T08:55:30.69+00:00

    hi KYOUNGTAEK OH & thanks for join me here at Q&A portal,

    2024-11-30 is still the GA v4.0 Document Intelligence API version, so it should work. If it suddenly fails, check endpoint path, SDK version, region, and Service Health before changing code. For v4.0 the REST path should look like

    {endpoint}/documentintelligence/documentModels/{modelId}:analyze?api-version=2024-11-30

    not the old Form Recognizer v3 path. REST docs https://learn.microsoft.com/en-us/rest/api/aiservices/document-models/analyze-document?view=rest-aiservices-v4.0%20(2024-11-30) ....

    Microsoft confirms the latest client libraries default to 2024-11-30

    https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/whats-new?view=doc-intel-4.0.0

    Update the SDK first if u are using code https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/versioning/migration-guide-overview?view=doc-intel-4.0.0

    If the same request worked before and now fails without code change, test with curl against the exact endpoint, capture request ID, region, timestamp, status code and response body. Then check Azure Service Health and open support if it still fails. Most common cause is old endpoint path or old SDK calling v4 API incorrectly.

    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 No comments

  2. Karnam Venkata Rajeswari 3,665 Reputation points Microsoft External Staff Moderator
    2026-05-26T22:51:37.04+00:00

    Hello @KYOUNGTAEK OH ,

    Welcome to Microsoft Q&A .Thank you for reaching out to us.

    The observed behavior is most consistent with a temporary backend processing condition, where requests are accepted but remain in a running state without completing. The issue is transient in nature and got mitigated.

    To confirm stability and proactively isolate similar scenarios, the following checks are recommended:

    1. Service Health Validation Please review current and historical service status: This helps determine whether the behavior aligns with any regional or platform-level degradation.
    2. API Version Isolation Please retry the same request using previous stable API versions:
      • 2024-07-31-preview
      • 2023-07-31
      1. If earlier versions succeed - indicates a potential API version-specific regression
      2. If all versions show similar behavior - suggests a broader backend condition
    3. Model Type Isolation Please test the same document using:
      • Prebuilt Invoice model
      • Prebuilt Read model
      1. Prebuilt succeeds - issue likely limited to the Custom Extraction pipeline
      2. Prebuilt also fails - indicates a wider service impact
    4. Endpoint and Connectivity Validation Please confirm the following:
      • Endpoint matches the deployed region (West US 2)
      • Correct API version is specified
      • Network allows outbound access to: *.cognitiveservices.azure.com

    Please note that configuration issues typically result in immediate HTTP errors (400/404), which differs from the observed “processing remains in running state” behavior.

    The following references might be helpful , please check them out

    Please let us know if the response was helpful

     

    Thank you

    Was this answer helpful?

    0 comments No comments

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.