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.
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!
azure document-intelligence or Form-Recognizer package
Azure Document Intelligence and Content Understanding
Is there a better OCR service than Azure Document Intelligence for text extraction?
How to read the output of Document Intelligence Prebuilt Layout Model?
Are Azure Document Intelligence and Azure Document Intelligence the same service?
Yes.
Azure Document Intelligence and Azure Document Intelligence are the same service. The service was renamed from Azure Document Intelligence to Azure Document Intelligence in July 2023. The service provides the same capabilities and features as before the renaming.
Pricing changes: There are no changes to pricing. The names Cognitive Services and Applied AI Services continue to be used in Azure billing, cost analysis, price lists, and price APIs.
Breaking changes: There are no breaking changes to APIs or client libraries.
Are Azure Document Intelligence and Azure Document Intelligence in Foundry Tools the same service?
Yes.
Azure Document Intelligence and Azure Document Intelligence in Foundry Tools are the same service. The service was renamed from Azure Document Intelligence in Foundry Tools to Azure Document Intelligence in July 2023. The service provides the same capabilities and features as before the renaming.
Pricing changes: There are no changes to pricing. The names Cognitive Services and Applied AI Services continue to be used in Azure billing, cost analysis, price lists, and price APIs.
Breaking changes: There are no breaking changes to APIs or client libraries.