🌐
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
Recognize forms at the edge, on-premises, and in the cloud with container support. The portable architecture can be deployed directly to Azure Kubernetes Service (AKS) or Azure Container Instances, or to a Kubernetes cluster deployed to Azure Stack.
🌐
Microsoft Learn
learn.microsoft.com › en-us › connectors › formrecognizer
Azure AI Document Intelligence (form recognizer) - Connectors | Microsoft Learn
The Azure AI Document Intelligence (formerly Form Recognizer) connector provide integration to Azure AI Document Intelligence.
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
azure document-intelligence or Form-Recognizer package
Dear all, I've just realized that for my existing system I am using form-recognizer package in Python. However, azure-ai-documentintelligence seems to be the right approach for the future. Do you know if there is any plan that the form-recognizer package… More on learn.microsoft.com
🌐 learn.microsoft.com
1
0
February 19, 2025
Azure AI Form Recogniser Accuracy l
Have been using it for almost 6 months. The more documents you can get to train the model The more accurate your answers would be More on reddit.com
🌐 r/AZURE
2
2
July 28, 2024
Is AI Builder the right tool?
To clarify, are the pdfs a single vendor sends consistent each time? So you’re seeing variations between vendors only? If yes to both, AI Builder is what you’ll need and of course you’ll need to train a model for each vendor. You’ll probably need something in your flow that can identify which email is coming from where and create a switch case to handle them appropriately in each branched case. Otherwise, you might create separate flows to handle each vendor if you wish. More on reddit.com
🌐 r/MicrosoftFlow
25
7
July 3, 2024
🌐
Microsoft Learn
learn.microsoft.com › en-us › dotnet › api › overview › azure › ai.formrecognizer-readme
Azure Form Recognizer client library for .NET - Azure for .NET Developers | Microsoft Learn
Create a Cognitive Services resource if you plan to access multiple cognitive services under a single endpoint/key. For Document Intelligence access only, create a Form Recognizer resource. Please note that you will need a single-service resource if you intend to use Azure Active Directory authentication.
🌐
Azure
contentunderstanding.ai.azure.com
Azure AI | Content Understanding Studio
We cannot provide a description for this page right now
🌐
Microsoft Azure
azure.microsoft.com › en-us › pricing › details › document-intelligence
Pricing - Azure Document Intelligence in Foundry Tools | Microsoft Azure
Detect and extract data from receipts, invoices, as well as tax forms, insurance, and health insurance cards using optical character recognition (OCR). Prebuilt models extract information to a defined schema.
🌐
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 in Foundry Tools is a machine-learning based OCR and intelligent document processing service to automate extraction of key data from forms and documents.
Find elsewhere
🌐
Analytics Vidhya
analyticsvidhya.com › home › intelligent document processing with azure form recognizer
Intelligent Document Processing with Azure Forms Recognizer
December 9, 2024 - First, log in to your Azure portal (portal.azure.com). Once you’re logged in, click on the “Create a resource” button on the left-hand side of the screen. In the “New” pane, type “Form Recognizer” into the search box and press enter.
🌐
Beyond Key
beyondkey.com › home › ocr › azure form recognizer and its benefits
Azure Form Recognizer: What are it & Benefits
April 7, 2026 - Azure Form Recognizer is an artificial intelligence service that lets you analyze PDFs and forms using pre-built models that can be changed. Form Recognizer has built-in models that work with standard forms like W-2s, invoices, receipts, business ...
🌐
Azure Docs
docs.azure.cn › en-us › ai-services › document-intelligence › faq
Azure Document Intelligence (formerly Azure AI Form Recognizer) FAQ | Azure Docs
You can then choose to retrieve ... an active Azure account and subscription with at least a Reader role to access Document Intelligence Studio....
🌐
Medium
rupalyadav.medium.com › azure-document-intelligence-form-recognizer-0b5e18c56d29
Azure Document Intelligence ( Form Recognizer ) | by Rupal Yadav | Medium
March 19, 2024 - Azure Document Intelligence utilizes Optical Character Recognition (OCR) technology as a fundamental component to extract text from various types of documents such as invoices, receipts, forms, and contracts.
🌐
ExamCollection
examcollection.com › home › certifications › all certifications › demystifying azure ai document intelligence: a new paradigm in document automation
Demystifying Azure AI Document Intelligence: A New Paradigm in Document Automation - ExamCollection
May 19, 2026 - Azure AI Document Intelligence, previously known as Azure Form Recognizer, is a cloud-based service from Microsoft that applies machine learning to extract structured data from documents at scale. Organizations across virtually every industry generate enormous volumes of documents daily, ranging ...
🌐
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.
Top answer
1 of 1
1

Hi Mariana Logvinenko,

The transition from the form-recognizer package to the azure-ai-document intelligence package reflects significant changes in Azure's approach to document analysis. Here’s a detailed overview of both services.

  • The form-recognizer package is being phased out, with the latest versions of Azure services focusing on azure-ai-document intelligence. Specifically, Form Recognizer v2.0-preview has already been deprecated, and users are encouraged to upgrade to the latest General Availability (GA) version of Document Intelligence.
  • While there is no explicit announcement regarding the complete deprecation of all Form Recognizer functionalities, the shift towards Document Intelligence indicates that future developments and support will primarily focus on this newer package. Users should consider migrating as new features and updates will likely be limited for the older service.
  • The azure-ai-document intelligence package introduces several new capabilities not available in Form Recognizer:
  • Improved machine learning models for analyzing text and structured data.
  • More robust APIs designed for better performance and ease of use.
  • New prebuilt models and enhanced customization options for document analysis.
  • The SDK versions for Document Intelligence are aligned with newer API versions, ensuring access to the latest features:
    • For instance, SDK version 3.3.X supports API versions up to 2023-07-31, while older versions of Form Recognizer only support up to 2.12
    • Migration guides are available to help transition applications from older SDKs to the new Document Intelligence SDK
  • Use The interface and user experience have been improved in Document Intelligence, making it easier for developers to integrate and use these services in their applications. This includes clearer documentation and more intuitive API calls.

Hope this helps. Do let us know if you any further queries.


If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

🌐
Medium
tech-depth-and-breadth.medium.com › azure-ai-document-intelligence-for-rag-use-cases-4e242b0ba7de
Azure AI Document Intelligence for RAG use cases | by Anurag Chatterjee | Medium
December 18, 2025 - Microsoft Azure’s AI Document Intelligence (previously Azure Form Recognizer) can extract “rich” content from multiple file formats including PDFs and Microsoft Office files.
🌐
Medium
medium.com › codenx › azure-ai-document-intelligence-b7538ab977a8
Azure Form Recognizer: Document Data Extraction | CodeNx
November 10, 2023 - Automate data extraction from documents with Azure Form Recognizer, a cloud-based AI service for structured and unstructured data processing.
🌐
Medium
officegarageitpro.medium.com › automate-document-analysis-with-azure-form-recognizer-using-ai-and-ocr-2ac39136d00b
Automate document analysis with Azure Form Recognizer using AI and OCR | by Mechanics Team | Medium
April 12, 2023 - Extract text automatically from forms, structured or unstructured documents, and text-based images at scale with AI and OCR using Azure’s Form Recognizer service and the Form Recognizer Studio. Build intelligent document processing apps using Azure AI services.