Quick answer. If you key paper forms, choose by where documents live and who maintains the model: SharePoint Premium in SharePoint libraries, AI Builder in Power Platform, Document Intelligence in your developers’ Azure code. Under CUI the cloud decides first; under HIPAA, confirm Microsoft’s BAA scope before PHI enters the service.
If your team still types paper forms and scanned documents into a system of record, Microsoft sells three services that can read them for you. SharePoint Premium (now document processing for Microsoft 365, formerly Syntex) runs on SharePoint libraries; Microsoft’s overview says “The pay-as-you-go services previously offered under Microsoft Syntex are now referred to as document processing services.” AI Builder document processing runs inside Power Platform. Azure Document Intelligence, which Microsoft’s pricing page lists as Azure Document Intelligence in Foundry Tools, is an Azure resource. Each is described here from Microsoft’s own documentation, read on September 29, 2026, in no order of preference. A passenger rail operator took a different route, moving its health compliance form onto touch-enabled handheld devices so compliance data no longer arrived by fax to be entered a second time by hand, as Reducing Administrative Costs Through Wireless Automation describes.
| Question | SharePoint Premium | AI Builder | Azure Document Intelligence |
|---|---|---|---|
| Where it runs | On files in the SharePoint libraries its models are applied to | Inside Power Automate flows and Power Apps apps, in the region of the Power Platform environment | In the Azure region where the resource was created |
| Who builds the model | Content owners, without code | Makers in a Power Platform environment | Developers, from code |
| Model types | Prebuilt; structured and freeform; unstructured | Fixed template documents; general documents; invoices | Prebuilt; custom extraction (template and neural); custom classification |
| Licensing basis | Pay-as-you-go through an Azure subscription, per transaction | AI Builder credits, giving way to Copilot Credits | Pay-as-you-go per page, with a free tier and commitment tiers |
| Government cloud line on Microsoft’s page | Pay-as-you-go not yet available for GCC | Document processing generally available in GCC and GCC High, not in DoD | Azure Government: FedRAMP High, DoD IL2, IL4 and IL5 (workload isolation); not IL6 |
| Named on Microsoft’s HIPAA page | SharePoint Online is named; SharePoint Premium is not | Power Automate and Power Apps are named; AI Builder is not | “Azure and Azure Government” is named; Document Intelligence is not named |
How Much Do Your Forms Vary From One Copy to the Next?
If every copy of a form puts the same field in the same place, a template model can read it; if the documents vary, you need a model built for variation. Each service draws that line in its own terms.
- Azure Document Intelligence. Microsoft’s model overview lists prebuilt models for documents such as invoices, receipts, ID documents and US health insurance cards, and says “Custom models are broadly classified into two types.” Those are custom classification models, which sort documents by type, and custom extraction models, which pull a defined set of fields. It adds: “The custom extraction model comes in two types: custom template and custom neural.”
- SharePoint Premium. Microsoft’s pay-as-you-go page bills prebuilt document processing, structured and freeform document processing, and unstructured document processing as separate services. Its overview describes prebuilt models for documents such as contracts, invoices and receipts, structured and freeform models for documents “where the information can appear anywhere in the document”, and unstructured models for documents “that vary in composition”.
- AI Builder. When a maker creates a document processing model, Microsoft offers three options: fixed template documents, general documents and invoices. It describes the fixed template option as “ideal when, for a given layout, the fields, tables, checkboxes, signatures, and other items can be found in similar places.”
Sort your own inbound documents into fixed layouts, varied layouts and free text before you compare anything else. A service whose model types do not match the documents you actually receive is the wrong service, whatever it costs.
Where Each Service Sits Against a CUI or HIPAA Boundary
If the forms carry CUI, the cloud decides before any feature does. Microsoft’s documentation draws a different line for each service:
- Azure Document Intelligence. Microsoft’s Azure Government audit scope table, last updated February 2026 on a page last updated September 21, 2026, marks Document Intelligence as authorized for FedRAMP High, DoD IL2, DoD IL4 and DoD IL5 through workload isolation, and does not mark it for DoD IL6. For workload isolation, Microsoft’s Azure Government services by audit scope table says services “require extra configuration to meet DoD IL5 compute and storage isolation requirements”.
- AI Builder. Microsoft’s AI Builder availability page, last updated January 14, 2026, lists document processing for fixed-template documents and for general documents as generally available in GCC and GCC High, and not available in DoD. The same page says “Document Automation isn’t available in GCC and GCC High”, which is a different feature from document processing.
- SharePoint Premium. Microsoft’s licensing page for document processing, last updated April 23, 2026, carries one government note: “For Government Community Cloud (GCC) organizations, pay-as-you-go licensing-and the services that require pay-as-you-go licensing-aren’t yet available.” The government purchase route and what it costs are covered in How Much Does SharePoint Premium (Formerly Syntex) Cost?
If CUI means your tenant moves to GCC High before any capture service is chosen, that decision comes first: GCC vs GCC High vs Commercial Microsoft 365 for CUI: An Evaluation Matrix. Whether a given contract’s data is CUI, and at what impact level, is a question for your contracting officer, not for a product page.
For forms that carry PHI, start with what Microsoft’s HIPAA and HITECH page, last updated July 29, 2025, names. It lists “Azure and Azure Government”, the Power Automate and Power Apps cloud services, and SharePoint Online among in-scope services. It does not name AI Builder, Document Intelligence, SharePoint Premium or document processing. For Azure services one by one, Microsoft’s audit scope page says: “See Appendices A and B in Microsoft Azure Compliance Offerings for detailed insight into which cloud services are in scope”. So before PHI enters any of the three, confirm in Microsoft’s business associate agreement (BAA) and those appendices that the service you chose is in scope, and ask counsel whether the data is PHI at all. The HIPAA page is plain about the rest: “using Microsoft services doesn’t on its own achieve HIPAA compliance.”
Data location differs too. Microsoft’s Document Intelligence data, privacy and security page, last updated July 28, 2026, says “The incoming data is processed in the same region where the Document Intelligence resource was created.” It also says “The service stores submitted input data and analyze results for 24 hours after an analysis operation completes.” For AI Builder, the availability page says “Your AI Builder models are deployed in the region that hosts your Microsoft Power Platform environment.” SharePoint Premium runs its models on the files in the libraries where they are applied; confirm with Microsoft where that processing runs before regulated content goes through it.
Who Will Retrain the Model When the Form Changes?
If a form’s layout changes next year, someone retrains the model, and each service gives that job to a different team.
- Azure Document Intelligence is an Azure resource your developers work with through its API and client libraries. Microsoft’s data page says custom models are built from training data the customer keeps in its own Azure blob storage, so retraining is a development task with a release process.
- SharePoint Premium puts the model in the hands of content owners. Microsoft’s SharePoint Syntex features description, last updated October 7, 2024, says its form processing engine is “based on AI Builder” and that “These models are built without code”.
- AI Builder puts the model in a Power Platform environment, where makers train and publish it and then use it in a flow or an app. Whoever owns that environment owns the retraining.
Name that team before you choose. A model that only a departed contractor can retrain is a gap in your control record, whichever service holds it. The same code versus low-code split, applied to agents rather than documents, is weighed in Copilot Studio vs Azure AI Foundry: Which One Fits Your Compliance Posture?
How Each Service Is Licensed
If procurement asks how each one is billed, the answers differ in kind, not only in amount. This page describes the basis only; prices change and are covered elsewhere.
- Azure Document Intelligence is billed pay-as-you-go per 1,000 pages on Microsoft’s pricing page, which also lists a free tier and commitment tiers with an upfront monthly fee.
- SharePoint Premium is billed per transaction through the Azure subscription you connect. Microsoft’s pay-as-you-go page, last updated June 1, 2026, says the services “do not apply to the Microsoft Azure Consumption Commitment (MACC) that your organization might have.” For structured and freeform processing it adds: “If you have AI Builder credits allocated to the environment, these credits are used first.”
- AI Builder runs on AI Builder credits, and those are ending. Microsoft’s End of AI Builder credits page, last updated September 9, 2026, says “Existing seeded AI Builder credits will be honored through to end of contract term.” Microsoft’s AI Builder credit page, last updated January 14, 2026, says “New customers can’t purchase AI Builder capacity add-on anymore, and must purchase Copilot Credits.” For the dates and the sizing, see AI Builder Credits After November 1, 2026: A Guide to Keeping Power Automate Document Flows Running on Copilot Credits.
The flow that carries each record after capture has its own license. For that side, see What Is the Total Cost of Power Automate Premium for 100 Users Annually?
Who Checks a Field Before It Becomes a Record?
If an extracted value goes straight into a system of record, a wrong read becomes a wrong record. Every one of the three services returns results that a person should be able to check first, and where that check sits is a design decision you own.
- Azure Document Intelligence returns a confidence score with its results. Microsoft’s accuracy and confidence page, last updated April 8, 2026, says “confidence can be used to determine whether to automatically accept the prediction or flag it for human review.”
- AI Builder returns a confidence score for each extracted field when its model runs in a flow; Microsoft’s Power Automate page for the model, last updated January 14, 2026, describes it as “How confident the model is in its prediction”.
- SharePoint Premium review belongs in the library’s own process: a named person checks the extracted values before anything downstream uses them.
Set the rule in writing: which fields always get a human check, what score sends a field to review, and who signs off. Where the checked record then lives is its own decision, covered in SharePoint Online vs a Dedicated DMS: How to Decide.
When these criteria point different ways, the boundary wins. A service that Microsoft does not document for your cloud is out, however well its model types, team fit and licensing match.
When Not to Buy a Capture Service at All
If the form can be born digital, replace it instead of reading it. A form your staff or customers fill in on screen needs no extraction model and no review step; the choice between the two usual Microsoft tools for that is in Microsoft Forms vs Power Apps: Which Should an Enterprise Use for a Business-Critical Form?
Keying by hand can also cost less than building a model, maintaining it and staffing the review step, when volume is low. And if the documents must stay in a cloud where Microsoft does not document the service, the answer is not that service, whatever its features.
Where i3solutions Fits After Capture
If the capture service is chosen, the next piece is the workflow that carries each checked record to where it belongs, and that is where i3solutions works. i3solutions builds client workflow automation on Power Automate cloud flows, Power Automate desktop flows for RPA, and Azure Logic Apps in both the Standard and Consumption tiers. i3solutions designs Azure integration architecture and builds and operates Azure Logic Apps workflows for enterprise clients, including running them on an ongoing basis rather than only building them. i3solutions governs client Power Platform tenants with the Center of Excellence Starter Kit, tenant-level and environment-level DLP policies, and managed environment controls. i3solutions delivers workflow automation and development inside customers’ SOC 2-audited environments, operating under the customer’s own controls, and knows how to operate in those regulated environments. All i3solutions workflow automation developers and consultants are U.S.-based.
i3solutions runs comparative platform-selection evaluations for clients, recommending among IAM platforms for hybrid estates and among workflow automation platforms against SOC 2 and HIPAA, rather than only implementing the Microsoft option. That platform choice is set out in Workflow Automation Platforms for SOC 2 and HIPAA: How to Select One, and the wider service in Workflow Automation Services Built for Enterprise IT Environments.
If CUI means a move to GCC High first: We manage GCC High migrations end-to-end: from eligibility validation and licensing coordination with your AOS-G supplier through identity architecture, data migration, security baseline configuration, and post-migration governance. i3solutions plans and runs these migrations for regulated defense organizations, structuring each phase around the compliance evidence assessors expect.
Key Takeaways
- If you remember one rule: choose the capture service by where the documents must live and who will retrain the model, then check that Microsoft documents it for your cloud.
- Microsoft’s Azure Government table marks Document Intelligence for FedRAMP High, DoD IL2, IL4 and IL5 through workload isolation; its AI Builder page lists document processing as generally available in GCC and GCC High, not DoD.
- Microsoft’s HIPAA page names Azure, Power Automate, Power Apps and SharePoint Online, but not AI Builder, Document Intelligence or SharePoint Premium by name; confirm BAA scope before PHI enters any of them.
- Seeded AI Builder credits are honored through to the end of the contract term, and new customers buy Copilot Credits instead.
Frequently Asked Questions
Is Azure AI Document Intelligence available in Azure Government for CUI workloads?
If your CUI workload runs in Azure Government, Microsoft’s audit scope table for Azure Government, last updated February 2026, marks Document Intelligence as authorized for FedRAMP High, DoD IL2, DoD IL4 and DoD IL5 through workload isolation, which Microsoft says needs extra configuration, and does not mark it for DoD IL6. Whether your contract’s data needs a given impact level is a question for your contracting officer.
Can AI Builder document processing run in GCC High?
If your tenant is in GCC High, Microsoft’s AI Builder availability page, last updated January 14, 2026, lists document processing for fixed-template documents and for general documents as generally available in GCC and GCC High, and not available in DoD. Document Automation, a separate AI Builder feature, is not available in GCC or GCC High.
Is SharePoint Premium document processing covered by Microsoft’s HIPAA BAA?
If PHI would pass through it, do not assume so. Microsoft’s HIPAA and HITECH page, last updated July 29, 2025, names SharePoint Online among in-scope services but does not name SharePoint Premium, Syntex or document processing. Confirm the service’s scope in Microsoft’s business associate agreement and the documents it points to before PHI enters it.
What happens to AI Builder credits in November 2026?
If your document flows run on seeded AI Builder credits, Microsoft’s End of AI Builder credits page, last updated September 9, 2026, says “Existing seeded AI Builder credits will be honored through to end of contract term.” Microsoft’s AI Builder credit page, last updated January 14, 2026, also says “New customers can’t purchase AI Builder capacity add-on anymore, and must purchase Copilot Credits.” Size the capacity for any AI Builder document flow in Copilot Credits before your licenses renew.
Bring Your Intake Boundary to a Workflow Architect
If you own the intake decision, bring the form types you receive, the cloud your tenant runs in, whether PHI or CUI is on the page, and the system each record lands in. A workflow architect uses those facts to map the flow after capture with you. Contact a senior workflow architect
Sources
- Microsoft Learn: Overview of document processing for Microsoft 365, last updated August 4, 2025; Licensing for document processing for Microsoft 365, last updated April 23, 2026; Pay-as-you-go pricing for document processing for Microsoft 365, last updated June 1, 2026; SharePoint Syntex features, last updated October 7, 2024.
- Microsoft Learn: AI Builder feature availability by region, Create a document processing custom model in AI Builder, Use the document processing model in Power Automate and Licensing and AI Builder credits, each last updated January 14, 2026.
- Microsoft Learn: End of AI Builder credits, last updated September 9, 2026.
- Microsoft Learn: Document Intelligence document processing models, last updated June 5, 2026; Data, privacy, and security for Document Intelligence, last updated July 28, 2026; Interpret and improve model accuracy and confidence scores, last updated April 8, 2026; Microsoft Azure, Azure Document Intelligence in Foundry Tools pricing (no date shown).
- Microsoft Learn: Azure, Dynamics 365, Microsoft 365, and Power Platform services compliance scope, last updated September 21, 2026 (tables last updated February 2026); HIPAA and HITECH Act, last updated July 29, 2025; Azure and other Microsoft cloud services in compliance audit scope, last updated April 5, 2023. Each read September 29, 2026. Microsoft revises these pages; confirm the current wording before you rely on it.