🌐
Microsoft Learn
learn.microsoft.com › en-us › azure › ai-services › document-intelligence › model-overview
Document Processing Models - Document Intelligence - Foundry Tools | Microsoft Learn
Document processing models for OCR, document layout, invoices, identity, custom models, and more to extract text, structure, and key/value pairs.
🌐
Microsoft Azure
azure.microsoft.com › en-us › products › ai-foundry › tools › document-intelligence
Azure Document Intelligence (now part of Azure Content Understanding in Foundry Tools) | Microsoft Azure
Azure Document Intelligence (now part of Azure Content Understanding) is a Foundry Tool that applies advanced AI models to extract text, key-value pairs, tables, and structures from documents automatically and accurately.
Discussions

AI Document Extraction on Azure - Options, Comparison & Recommendations for Invoice/Contract Processing
I’m not familiar with the dev side but we use a hybrid approach, DI for as much as possible. But since some documents have stamps or notes on them we fallback to OAI for that. More on reddit.com
🌐 r/AZURE
17
4
December 18, 2025
On-premise AI solutions for document analysis
I don't know the details but someone at our company has set up a server with Open WebUI (Formerly Ollama WebUI). They have installed a few LLMs to it and it can be used internally for ingesting documents etc. More on reddit.com
🌐 r/sysadmin
7
0
June 27, 2024
Maintaining On-Premises IP's on the cloud. Is it possible in Azure ASR?
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-retain-ip-azure-vm-failover More on reddit.com
🌐 r/AZURE
15
2
August 2, 2024
Best way to get logon audit events for on-prem domain controllers using Azure?
Agents and a SIEM like sentinel. It ain’t cheap although it’s been a few years since I used Sentinel More on reddit.com
🌐 r/AZURE
4
0
June 3, 2024
🌐
Microsoft Learn
learn.microsoft.com › en-us › azure › ai-services › document-intelligence › concept › choose-model-feature
Choose the best Document Intelligence model for your applications and workflows. - Foundry Tools | Microsoft Learn
June 2, 2026 - The layout model is powered by the Read OCR engine to detect pages, tables, styles, text, lines, words, locations, and languages. Learn how to process your own forms and documents with the Document Intelligence Studio
🌐
Azure
ai.azure.com › catalog › models › Azure-AI-Document-Intelligence
Catalog / Models / Azure-AI-Document-Intelligence
Description: Prebuilt models enable you to add intelligent document processing to your apps and flows without having to train and build your own models.
🌐
Microsoft Learn
learn.microsoft.com › en-us › azure › ai-services › document-intelligence › train › custom-model
Custom document models - Document Intelligence - Foundry Tools | Microsoft Learn
To create a custom extraction model, label a dataset of documents with the values you want extracted and train the model on the labeled dataset. You only need five examples of the same form or document type to get started. ... Document Intelligence v4.0 2024-11-30 (GA) API supports custom neural model overlapping fields, signature detection and table, row and cell level confidence.
🌐
Azure
contentunderstanding.ai.azure.com › documentintelligence › studio
Document Intelligence Studio - Microsoft Azure
Train custom models to classify documents and extract text, structure and fields from your forms or documents.
🌐
Microsoft Learn
learn.microsoft.com › en-us › azure › ai-services › document-intelligence › overview
What Is Azure Document Intelligence in Foundry Tools? - Foundry Tools | Microsoft Learn
September 8, 2026 - Azure Document Intelligence applies optical character recognition (OCR) based on machine learning along with document understanding technologies to extract text, tables, structure, and key/value pairs from documents.
🌐
Microsoft Learn
learn.microsoft.com › en-us › azure › ai-services › document-intelligence
Document Intelligence documentation - Quickstarts, Tutorials, API Reference - Foundry Tools | Microsoft Learn
Azure Document Intelligence in Foundry Tools is a cloud-based Microsoft Foundry tool that uses machine-learning models to automate your data processing in applications and workflows.
Find elsewhere
🌐
Azure Docs
docs.azure.cn › en-us › ai-services › document-intelligence › studio-overview
Document Intelligence Studio - Azure AI services | Azure Docs
Layout: Try out the Document Intelligence layout feature with sample documents or your own documents. Extract text, tables, selection marks, and structure information. To learn more, see Layout overview. Prebuilt models: Use the Document Intelligence prebuilt models to add intelligent document processing to your apps and flows without having to train and build your own models.
🌐
Azure Docs
docs.azure.cn › en-us › ai-services › document-intelligence › concept › choose-model-feature
Choose the best Document Intelligence model for your applications and workflows. - Azure AI services | Azure Docs
June 22, 2026 - The layout model is powered by the Read OCR engine to detect pages, tables, styles, text, lines, words, locations, and languages. Learn how to process your own forms and documents with the Document Intelligence Studio
🌐
PyPI
pypi.org › project › azure-ai-documentintelligence
azure-ai-documentintelligence · PyPI
Extract fields from select document types such as receipts, invoices, business cards, identity documents, and U.S. W-2 tax documents using prebuilt models provided by the Document Intelligence service. For example, to analyze fields from a sales receipt, use the prebuilt receipt model provided by passing model_id="prebuilt-receipt" into the begin_analyze_document method: from azure.core.credentials import AzureKeyCredential from azure.ai.documentintelligence import DocumentIntelligenceClient from azure.ai.documentintelligence.models import AnalyzeResult def _format_price(price_dict): if price_
🌐
Azure Docs
docs.azure.cn › en-us › ai-services › document-intelligence › model-overview
Document Processing Models - Document Intelligence - Azure AI services | Azure Docs
Document processing models for OCR, document layout, invoices, identity, custom models, and more to extract text, structure, and key/value pairs.
🌐
Microsoft Azure
azure.microsoft.com › en-us › pricing › details › document-intelligence
Pricing - Azure Document Intelligence in Foundry Tools | Microsoft Azure
Prebuilt – Document Intelligence supports various prebuilt models for common document types. Detect and extract data from receipts, invoices, as well as tax forms, insurance, and health insurance cards using optical character recognition (OCR).
🌐
Reddit
reddit.com › r/azure › ai document extraction on azure - options, comparison & recommendations for invoice/contract processing
r/AZURE on Reddit: AI Document Extraction on Azure - Options, Comparison & Recommendations for Invoice/Contract Processing
December 18, 2025 -

Hey everyone,

I'm working on an application that uses AI to extract structured data from commercial documents - invoices, contracts, purchase orders, that kind of stuff. I've been testing Claude and Google's multimodal models and they work really well for this use case.

However, I need to evaluate what Azure offers since that's our cloud environment or what other options could be considered. After digging into it, I found there are basically two main paths:

1. Azure Document Intelligence (formerly Form Recognizer)

This is their dedicated document processing service. It has prebuilt models for invoices, receipts, contracts, tax forms, etc. Pricing is around $10/1,000 pages for prebuilt models, $30/1,000 for custom extraction. Seems very accurate for structured documents and returns proper JSON with confidence scores and bounding boxes.

2. Azure OpenAI with GPT-4o Vision

Send document images directly to GPT-4o, use prompt engineering to define extraction schema, and use Structured Outputs for guaranteed JSON compliance. More flexible but apparently more expensive (~$0.05-0.07/page) and potentially less accurate on complex tables.

3. Hybrid approach

Microsoft's own samples show using Document Intelligence Layout model to convert PDFs to Markdown first, then feeding that to GPT-4o for the actual extraction. Supposedly gives you the best of both worlds - accurate OCR + flexible schema extraction.

My questions for those who've built similar systems:

  • If you're using Azure, which approach did you go with? How's the accuracy and cost working out in production?

  • For those using Document Intelligence prebuilt models - how well do they handle non-standard invoice formats or documents in multiple languages? Do you end up needing custom models anyway?

  • Anyone tried the hybrid approach (Doc Intelligence + GPT-4o)? Is the added complexity worth it vs just using GPT-4o directly on images?

  • How does Azure Document Intelligence compare to Claude or Google Document AI in your experience? I've had good results with Claude's vision capabilities but wondering if a specialized service like Document Intelligence would be more reliable at scale.

  • For high volume processing (let's say 50k+ pages/month) - what's been most cost-effective?

  • Any gotchas or lessons learned you wish you knew before starting?

Would really appreciate hearing about real-world experiences. Most of what I've found is marketing material or basic tutorials, not much on how these solutions hold up in production with messy real-world documents.

Thanks!

Top answer
1 of 5
2
I’m not familiar with the dev side but we use a hybrid approach, DI for as much as possible. But since some documents have stamps or notes on them we fallback to OAI for that.
2 of 5
2
We basically do #3, but use gpt-5.2 or whatever better model, not 4o. We're not overly concerned about cost because we're doing a one-time ingestion, not offering a service or something. Q&A... > If you're using Azure, which approach did you go with? How's the accuracy and cost working out in production? Like I said, #3. > For those using Document Intelligence prebuilt models - how well do they handle non-standard invoice formats or documents in multiple languages? Do you end up needing custom models anyway? We just use the layout model to get markdown and it does just fine. The second-phase OpenAI models do quite well at "figuring it out" from the markdown. When I did this with GPT-4o it did fine and the reasoning models just made it even better. No custom models. Our documents were in multiple languages, no issues. You can even answer in English if the documents are in another language. > Anyone tried the hybrid approach (Doc Intelligence + GPT-4o)? Is the added complexity worth it vs just using GPT-4o directly on images? I did extensive testing on this. DocIntel Layout + LLM was the best. The input file matters, see the last answer. > How does Azure Document Intelligence compare to Claude or Google Document AI in your experience? I've had good results with Claude's vision capabilities but wondering if a specialized service like Document Intelligence would be more reliable at scale. Haven't tried it, but I'll say DocIntel had no problem scaling to our ~2.6M pages of burst ingestion when we needed it. It did that in like 12 hours. We bought the pre-paid quantity for a discount on the first month to deal with the initial burst of pages. > For high volume processing (let's say 50k+ pages/month) - what's been most cost-effective? For us it's consistency and simplicity. I don't think you'll get cheaper than DocIntel + LLM if your documents are varied. I tried all kinds of other things like `docling` and `markitdown`, it just doesn't compare to DocIntel's Layout model. My cost modeling was even back with 4o that to process our documents it was an order of magnitude more expensive to just have the LLM do everything, versus use DocIntel to get Markdown, then the LLM to do the extraction. > Any gotchas or lessons learned you wish you knew before starting? So many... FLATTEN YOUR DOCUMENTS TO PDF BEFORE THEY GO TO DOCINTEL, IT MATTERS. We were ingesting a large quantity of Microsoft Word documents and what we quickly realized is Word features are invisible to DocIntel. Things like numbered bullets, table of contents, footnotes, header/footer, pretty much anything "dynamic" was apparently just a markup in the document that is rended when opened by Word. Like bullet "3.1.2" is really just a marker for "[Ordered List Bullet Level 3]", so the markdown output never had "3.1.2" in it, so if you need to understand "what step does XYZ happen in", you'd never get a step number. When DocIntel cracks the .docx open it just parses the XML and doesn't account for those things. When you take the same document and save it as a PDF using Word it "flattens" or "hard codes" everything. Taking that PDF to DocIntel you'll get much better results. Want to test yourself? Feed a docx through DocIntel save the markdown as "Test-Alpha.md", save the docx as a PDF, and feed that PDF through DocIntel and save the markdown as "Test-Beta.md" and then give them both to ChatGPT and ask it to "compare and contrast the files from a missing data or context standpoint that would be useful to have when having AI analyze these documents". It's going to tell you Test-Beta has way more formatting. So how do you do this flattening en masse? I wrote a janky python script that uses the Word COM-style calls to open the docx in an invisible window and save it as a PDF. There is another option to upload it to OneDrive and download the PDF, but I haven't tested if this is the same. If you think you will ever need to use that DocIntel output again, save the .json somewhere and save yourself the cost of a repeated conversion. There's a lot of cool stuff in there with bounding boxes and image figures and stuff.
🌐
GitHub
github.com › MicrosoftDocs › azure-ai-docs › blob › main › articles › ai-services › document-intelligence › overview.md
azure-ai-docs/articles/ai-services/document-intelligence/overview.md at main · MicrosoftDocs/azure-ai-docs
Azure Document Intelligence applies optical character recognition (OCR) based on machine learning along with document understanding technologies to extract text, tables, structure, and key/value pairs from documents.
Author: MicrosoftDocs
🌐
Medium
medium.com › @sujathamudadla1213 › which-azure-document-intelligence-model-should-you-use-for-different-document-types-f2d239bfe8c3
Which Azure Document Intelligence model should you use for different document types? | by Sujatha Mudadla | Medium
April 15, 2026 - Choose this when your primary goal is text extraction without needing to understand the document’s layout or key-value relationships. Layout Model: Builds on the Read model to extract structure. It detects tables, selection marks (checkboxes), paragraphs, titles, headings, and subheadings from a document.
🌐
GitHub
github.com › Azure-Samples › document-intelligence-code-samples
GitHub - Azure-Samples/document-intelligence-code-samples: Sample site for Document Intelligence code samples and associated media. · GitHub
Note: For more samples, see Azure SDK for Python and Async Samples. ... Select the link of the model name to reach the corresponding topic page for more details. Select v3.1 (2023-07-31-GA) to view earlier versions. Read model: Extract printed and handwritten text. ... Layout model: Extract and anlayze text, tables, and document structure. ... Prebuilt models: Add intelligent document processing to your apps and flows without having to train and build your own models.
🌐
Medium
medium.com › @dr.booma19 › microsoft-azure-ai-document-intelligence-with-custom-build-models-a-beginners-guide-37ca6b16c7a9
Microsoft Azure AI Document Intelligence with Custom build Models: A Beginners Guide | by Dr Booma | Medium
March 20, 2024 - Azure Document Intelligence custom model provides two potent custom model options: Custom Neural Models and Custom Template Models. The former harnesses deep learning to adeptly handle generally unstructured documents, where field placements ...