Azure AI Content Understanding failed to analyze PDF with unexpected error

Varun Aditya 0 Reputation points
2026-06-18T10:40:01.4066667+00:00

I am using Azure AI Content Understanding to analyze a PDF file, but the analysis fails with an unexpected error.

File name: L2528366.pdf

Error shown:

Analysis failed Failed to analyze the file L2528366.pdf. An unexpected error occurred.

Request ID:

apim-request-id: 7a509c0e-39af-4e45-8f01-e98c77539615

The message says this might be a transient error and to try again later htis error appearing often, I still help understanding what caused the failure.

Could someone please help confirm whether this is:

a service-side issue,

a PDF-specific issue,

a limitation/unsupported PDF format issue,

or a configuration/API issue?

Also, can Microsoft support or the product team trace this failure using the apim-request-id?

I am not sharing the PDF publicly because it may contain private business data.

Azure Document Intelligence in Foundry Tools

2 answers

Sort by: Most helpful
  1. Anshika Varshney 14,095 Reputation points Microsoft External Staff Moderator
    2026-06-25T19:43:42.08+00:00

    Hello @Varun Aditya

    The error message alone does not provide enough information to determine whether the failure is caused by the PDF itself, the service, or the configuration. However, since the issue is occurring consistently for the same PDF rather than succeeding on retry, it may be helpful to perform a few validation checks.

    Could you please confirm:

    • Whether other PDF files can be analyzed successfully using the same analyzer and resource.
    • The approximate file size and page count of the PDF.
    • Whether the PDF is scanned, password-protected, encrypted, or generated from another application.
    • Whether the issue occurs both in the Content Understanding Studio and through the API (if you are using the API).

    The provided apim-request-id can be useful for backend investigation, but additional information such as the UTC timestamp, region, analyzer name, and whether the problem is reproducible with only this specific document would help narrow down the cause.

    Looking forward to your update.

    Thanks!

    Was this answer helpful?

    0 comments No comments

  2. Vinodh247-1375 43,426 Reputation points Volunteer Moderator
    2026-06-18T12:24:57.48+00:00

    Hi ,

    Thanks for reaching out to Microsoft Q&A.

    This is most likely not a simple transient error, given it is recurring. Based on the pattern, the failure typically falls into one of three buckets: PDF specific issues (most common), service side processing limits, or less commonly API/config issues. In practice, azure AI content understanding often throws generic “unexpected error” when it cannot parse the internal PDF structure, this happens with scanned PDFs without proper OCR layers, corrupted cross-reference tables, unsupported encodings, very large files, complex layouts (embedded fonts, vector layers), or encrypted/restricted PDFs. If the same file consistently fails while others succeed, it strongly indicates a document-level parsing limitation rather than your API setup.

    The apim-request-id is useful, and yes, microsoft support can trace it internally, but only if you raise a support ticket; it is not something you can self-debug further. Before escalating, validate quickly: try resaving the PDF (print-to-PDF), reduce size, remove encryption, or run it through OCR (for example, convert to a clean text-based PDF). If those fixes work, it confirms a format/structure incompatibility. If even simplified versions fail, then it is likely a service-side issue or regional backend instability, and you should escalate with the request ID and timestamp.

    Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

    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.