Microsoft 365 Document Processing: Setup, Policies, and Admin Configuration Guide 2026
Why Microsoft 365 Document Processing Configuration Breaks (And Why the Error Messages Are Useless)
I've worked through Microsoft 365 document processing setups on dozens of tenants , and the single most common frustration I hear from admins is this: "I followed the steps in the admin center, and now nothing works and I have no idea why." The errors you get are vague. The portal just spins. Your users ping you saying autofill columns aren't populating, or that the document translation button is greyed out, or that eSignature requests aren't going through.
Here's the thing: Microsoft 365 document processing , the suite of AI-powered content services that most organizations knew under the old "Microsoft Syntex" branding, is not a single product you toggle on. It's a collection of individual pay-as-you-go services, each with its own provisioning state, its own Azure billing meter, and its own set of admin prerequisites. When one piece is misconfigured, the whole experience falls apart. And Microsoft's error messages rarely tell you which piece it actually is.
The most common root causes I see in the field break down like this:
- Azure subscription not linked: This is the number-one culprit. Microsoft 365 document processing billing runs through Azure. If your Azure subscription isn't correctly attached to your Microsoft 365 tenant, or if the subscription has lapsed, every pay-as-you-go service will silently fail to activate.
- Tenant-level pay-as-you-go not enabled: Even if Azure billing is set up, pay-as-you-go must be explicitly enabled in the SharePoint admin center before individual services go live. A lot of admins skip this step because they assume billing setup is enough.
- AI Builder credit confusion: If you migrated from the old per-user license model or were relying on AI Builder credits, you need to know that Microsoft announced the progressive end of AI Builder credits in October 2025. Tenants that haven't switched to pay-as-you-go billing are finding services deactivated with no clear warning.
- GCC tenant limitations: If your organization is on Government Community Cloud, pay-as-you-go licensing is not yet available for document processing. You must continue on per-user licenses until Microsoft makes this available. Trying to activate pay-as-you-go on a GCC tenant produces confusing failures that admins often mistake for a configuration error on their end.
- Per-user license expiry: Per-user licenses for document processing can no longer be purchased. If yours have expired and you haven't set up pay-as-you-go, your users are locked out, full stop.
I know how frustrating this is, especially when these services are blocking real business workflows, contracts sitting unsigned, invoices unprocessed, translations delayed. The guide below walks you through every layer of this, from the fastest fix to the deepest enterprise configuration. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you spend an hour in the admin portal, run through this single check. In my experience, about 60% of Microsoft 365 document processing setup failures trace back to one thing: pay-as-you-go billing is not turned on at the tenant level, even though everything else looks correct.
Here's exactly what to do right now:
- Open the SharePoint admin center, go to
admin.microsoft.com, then navigate to Admin centers > SharePoint. - In the left navigation, look for Settings. Scroll down and find the Document processing section (it may still appear as "Microsoft Syntex" on some tenants during the transition period).
- Click into document processing settings. You should see a page that lets you manage individual services, autofill columns, document translation, eSignature, optical character recognition, and the rest.
- Now look at the top of that page for a banner or status indicator showing Billing status. If it says "Not configured" or shows an Azure subscription warning, that is your problem right there.
- Click Set up billing (or the equivalent link shown). You'll be prompted to select an active Azure subscription. Select the correct subscription and confirm.
- Wait 5–10 minutes, then reload the page. Your services should now show as available to activate.
Once billing is active, you still need to turn on each service individually. They don't auto-enable. Go back to the document processing settings page, find each service you want (for example, Autofill columns or Document translation), and toggle it on. Save your changes.
If all of this is already configured and services are still not working for your users, move on to the step-by-step section below, there are a few layers deeper this can go.
This is the foundation everything else depends on. Microsoft 365 document processing uses Azure-based billing, meaning the cost of every autofill column run, every OCR extraction, every document translation flows out through an Azure subscription meter. No valid Azure subscription, no services.
Navigate to the SharePoint admin center: admin.microsoft.com > Admin centers > SharePoint > Settings > Document processing.
On the billing configuration page, confirm you see:
- An active Azure subscription name listed
- A resource group assigned
- A region selected (this should match your tenant's primary data region where possible)
If any of these fields are blank or showing an error, use the Set up pay-as-you-go billing flow to re-link. The PowerShell equivalent, for admins who prefer scripting this across multiple tenants, is available through the SharePoint Online Management Shell:
Connect-SPOService -Url https://<yourtenant>-admin.sharepoint.com
Get-SPOSyntexBillingSettingsThis command returns your current billing configuration. If BillingAzureSubscriptionId is empty, billing is not set up and nothing will work regardless of what's toggled in the UI.
After correctly linking your Azure subscription, you should see the billing status change to Active within the admin center within about 10 minutes. If it stays in a pending state beyond 30 minutes, check that your Azure subscription itself is not suspended or over its spending limit in the Azure portal at portal.azure.com > Subscriptions.
A billing subscription being active does not automatically switch on any of the document processing services. Each one has to be explicitly enabled. I've seen plenty of admins set up billing, assume everything is live, and then spend two hours debugging why autofill columns aren't appearing in SharePoint libraries, only to realize they never toggled the service on.
In the SharePoint admin center document processing settings page, you'll find the full list of available pay-as-you-go services. Work through each one you need:
- Autofill columns, uses large language models to extract or generate content automatically for document library columns. Toggle on if you want AI-driven metadata population.
- Document translation, creates translated copies of documents in SharePoint libraries while preserving original formatting. Supports all Microsoft-supported languages and dialects.
- eSignature, enables electronic signing workflows while keeping documents inside Microsoft 365. Toggle this on if your team needs to send contracts or agreements for signing.
- Optical character recognition (OCR), extracts printed or handwritten text from images in your document libraries.
- Content assembly, auto-generates standard business documents like contracts, service agreements, and letters of consent from templates.
- Image tagging, automatically tags images in SharePoint libraries for easier search and filtering.
- Taxonomy tagging, applies term sets to files in SharePoint libraries automatically.
For prebuilt, structured/freeform, and unstructured document processing models, enable those as well if your use case requires extracting information from invoices, receipts, contracts, or variable-format documents.
After enabling each service, save and wait a few minutes. Your users should then see the relevant options appear inside their SharePoint document libraries under the Automate or library settings menus.
One of the genuinely nice things about the pay-as-you-go model is how open it is: any user in your Microsoft 365 tenant can use document processing services, provided they hold a valid Microsoft 365 license. There's no per-user add-on to buy or assign. That said, I still see permission-related failures all the time, and they almost always come down to one of three things.
First: the user doesn't have a Microsoft 365 license at all, perhaps they're on a Teams Essentials plan or a standalone Exchange plan. These users can't access SharePoint document processing features regardless of billing setup.
Second: SharePoint site permissions are too restrictive. Document processing features surface inside SharePoint document libraries, and if a user only has read access to a library, they won't see options like autofill, translation, or model application. They need at minimum Contribute permissions on the library.
Third: for creating or managing document processing models (prebuilt, structured/freeform, or unstructured), the user needs to be a site owner on the content center site. Regular contributors can apply models that already exist, but they can't build new ones without elevated access. Check the content center site permissions at Site settings > Site permissions and confirm model-building users are listed as owners.
To audit which users in your tenant have valid Microsoft 365 licenses, use the Microsoft 365 admin center: admin.microsoft.com > Users > Active users, then filter by license type. Export this list and cross-reference against users reporting issues.
If your organization was using AI Builder credits to power document processing workflows, particularly for Power Automate-integrated document extraction, this step is urgent. Microsoft announced in October 2025 the progressive end of AI Builder credits. If you haven't already transitioned to pay-as-you-go billing, some of your document processing automations may already be failing silently.
Here's how to check your AI Builder credit status and understand the impact:
- Go to the Power Platform admin center:
admin.powerplatform.microsoft.com - Navigate to Resources > Capacity and look for the AI Builder section
- If you see a warning about credits being deprecated or a zero-balance alert, your AI Builder-dependent flows are at risk
Flows and automations that used AI Builder credits for document intelligence tasks, things like extracting fields from invoices or reading form data, need to be reviewed. The Microsoft 365 document processing pay-as-you-go model covers many of the same capabilities through prebuilt models, structured/freeform models, and unstructured models, so migration is usually straightforward conceptually. The practical work is reconnecting your Power Automate flows to the updated document processing actions and ensuring billing meters are correctly attached.
For organizations that relied heavily on AI Builder for their document workflows, I'd recommend auditing your Power Automate environment now. Pull a list of flows using AI Builder connectors:
# In Power Automate, go to:
My Flows > All flows > Filter by: AI Builder connectorFor each affected flow, identify whether the equivalent capability exists in the pay-as-you-go document processing services and update accordingly. Don't wait on this, the transition window is not indefinite.
Once billing is active and services are enabled, the actual end-user experience lives inside SharePoint document libraries. Getting a model applied correctly to a library is where a lot of admins trip up, especially with the different model types behaving differently.
Here's the practical breakdown of how to apply each model type:
For prebuilt models (invoices, receipts, contracts): Go to the SharePoint document library where you want processing applied. Click Automate > Apply a document processing model. You'll see a panel listing available prebuilt models. Select the one that matches your document type and click Add. Documents uploaded to this library will now be automatically analyzed.
For structured and freeform models: These require training in the content center. Navigate to your content center site, create a new model, upload sample documents, label the fields you want extracted, and train the model. Once trained and published, apply it to target libraries using the same Automate menu.
For unstructured models: Built for documents that vary in composition, think legal correspondence or mixed-format reports. Same workflow through the content center: create, train with examples, publish, then apply to libraries.
After applying a model, test it immediately. Upload a sample document matching the expected type and wait 30–60 seconds. Check the library's columns, if extraction is working, you should see fields like vendor name, invoice total, or date populate automatically. If columns remain empty after a few minutes:
Verify:
1. Model is published (not just saved)
2. Library has the model correctly applied (Automate > Manage document processing models)
3. Azure billing meter is active
4. Document format is supported (PDFs and most Office formats work; some image-only PDFs may need OCR enabled first)For OCR specifically: if your documents are image-based PDFs or scanned files, OCR must be separately enabled in the admin center. Optical character recognition extracts the text layer first, which then allows other document processing models to work on the content. Without OCR turned on, scanned documents return empty extractions every time.
Advanced Microsoft 365 Document Processing Troubleshooting
If you've gone through every step above and things are still broken, you're in enterprise territory now. These are the configurations that don't show up in the standard admin documentation and that typically affect domain-joined machines, organizations with complex Azure tenancy, or environments with aggressive conditional access policies.
Group Policy and Conditional Access Conflicts
Document processing services, particularly eSignature and the content assembly features, use browser-based interactions that can be blocked by Conditional Access policies enforcing specific device compliance states. If users are accessing SharePoint from unmanaged devices or from browsers not enrolled in Intune, they may hit access blocks that look exactly like "the feature isn't enabled" but are actually policy denials.
Check your Conditional Access policies in Azure AD (now Microsoft Entra ID): portal.azure.com > Microsoft Entra ID > Security > Conditional Access > Policies. Look for any policies targeting SharePoint Online or "All cloud apps" that require device compliance or specific client app types. Temporarily exclude a test user from these policies and retest to confirm whether Conditional Access is the culprit.
Custom Power Platform Environments
If your organization uses structured or freeform document processing models in a custom Power Platform environment, meaning not the default environment, there's additional setup required. The content center and the Power Platform environment need to be explicitly linked. Check the Microsoft documentation on setting up a custom Power Platform environment for document processing if your models live in non-default environments and aren't triggering correctly.
Event Viewer Analysis for SharePoint Add-in Failures
For on-premises or hybrid SharePoint configurations that interact with Microsoft 365 document processing services, the Windows Event Viewer on the SharePoint server can reveal handshake failures. Look under:
Event Viewer > Applications and Services Logs > Microsoft > SharePoint Products > Shared > Operational
Key Event IDs to watch:
- Event ID 7043: App pool identity error
- Event ID 5214: Service application proxy failure
- Event ID 8306: Claims authentication token failureGCC Tenant, Stop Fighting the Portal
I want to be blunt about this because I've seen IT teams waste days on it: if you are on a Government Community Cloud tenant, pay-as-you-go document processing is not available to you yet. Full stop. The admin portal may show some of these features, and you may even get partway through the billing setup before hitting a wall. This is not a misconfiguration on your end, it's a feature availability limitation. GCC organizations should continue using per-user licenses and monitor Microsoft's roadmap announcements for GCC parity timelines. Attempting to force-activate pay-as-you-go on a GCC tenant will not work and may create billing artifacts in your Azure subscription you'll then have to clean up.
SharePoint Cost Calculator for Budget Planning
Before rolling out document processing at scale, use the SharePoint cost calculator Microsoft provides to model your expected costs. Feed in your estimated monthly document volumes per service type, OCR extractions, translation requests, autofill operations, and get a projected Azure spend. This is especially important before enabling these services across large document libraries or automating high-volume workflows, because pay-as-you-go meters run per-use with no spending cap by default.
Prevention & Best Practices for Microsoft 365 Document Processing
Once you've got your document processing setup working correctly, keeping it working is about building the right habits and guardrails into your admin process. Here's what I recommend to every organization after a successful deployment.
Set up Azure spending alerts immediately. Because document processing billing runs through Azure meters with no built-in cap, a misconfigured automation, say, a Power Automate flow triggering document translation on every single file upload in a busy library, can generate unexpected costs before anyone notices. In the Azure portal, go to your subscription and configure a budget alert at a comfortable threshold. Get an email when you hit 80% of your monthly budget. This is the single most important safeguard for pay-as-you-go services.
Document which services are enabled and why. I know this sounds obvious, but in practice almost no one does it. Maintain an internal configuration document that lists every document processing service you've enabled, the date it was enabled, which libraries or sites it's applied to, and the business owner for that workflow. When Microsoft releases changes or you rotate admins, this document becomes invaluable.
Monitor the AI Builder credits deprecation timeline. If your organization still has any Power Automate flows or apps using AI Builder, track the Microsoft announcements on the End of AI Builder credits page. Don't wait for services to fail, proactively migrate those workflows to the pay-as-you-go document processing equivalents before the deprecation deadline hits.
Test models in a non-production library first. Before applying any document processing model to a live business library, always test on a dedicated staging library with representative sample documents. Structured and freeform models especially need validation, an undertrained model applied to production data will extract wrong or empty values, and correcting that data after the fact is painful.
Review per-user license status for per-user license holdovers. If your organization still has active legacy per-user licenses, be aware they cannot be repurchased once they expire. Plan your transition to pay-as-you-go well ahead of expiry, don't let the deadline sneak up on you and leave users without access to the document processing capabilities they depend on.
- Set an Azure budget alert at 80% of your expected monthly document processing spend, takes 5 minutes and saves you from bill shock
- Enable OCR at the tenant level even if you don't think you need it yet, it's required for scanned PDFs and having it already on means you won't debug a mystery extraction failure later
- Create a dedicated SharePoint content center site and assign at least two site owners, single-owner content centers become a bottleneck when that person is out
- Check your Power Platform environment configuration quarterly, custom environment link settings for document processing can drift after Power Platform updates
Frequently Asked Questions
Do I still need Microsoft Syntex to use document processing in 2026?
No, "Microsoft Syntex" as a product name has been retired. The same services now live under the "Document processing for Microsoft 365" umbrella. You don't need a Syntex license specifically; you need pay-as-you-go billing configured through an active Azure subscription in the SharePoint admin center. The features themselves are unchanged, only the branding and licensing model shifted. If you see the Syntex name in your admin center, your tenant is still in the transition period but the functionality is identical.
Can anyone in my organization use document processing, or do I need to assign licenses per user?
With pay-as-you-go billing, any user who holds a valid Microsoft 365 license can use document processing services, no per-user add-on assignment needed. This is one of the genuine benefits of the new model over the old per-user licensing approach. The caveat is that users still need appropriate SharePoint permissions on the libraries where document processing is applied, and creating new models requires site owner access on the content center. Access is broad, but SharePoint permissions still govern what individual users can actually do.
My autofill columns stopped working after working fine for weeks, what changed?
The most common cause of a sudden autofill columns failure after working correctly is an Azure subscription state change, the subscription hit a spending limit, a credit card on file expired, or someone on the Azure team suspended it. Check your Azure subscription status at portal.azure.com immediately. The second most common cause is an admin accidentally toggling off the autofill columns service in the SharePoint admin center during unrelated configuration work. Check the document processing settings page and confirm the service is still enabled. If both of those are fine, check whether a recent SharePoint update changed library column configurations, autofill columns are tied to specific library columns and occasionally need to be re-associated after schema changes.
We're on a GCC tenant, when will document processing pay-as-you-go be available for us?
As of early 2026, pay-as-you-go document processing is not yet available for Government Community Cloud tenants. Microsoft's official guidance is to continue using per-user licenses until parity is announced. Per-user licenses can still be assigned to new users even though they can no longer be newly purchased, so if you have existing licenses, you can continue distributing them. Watch the Microsoft 365 Government roadmap at microsoft.com for GCC availability announcements, and plan your transition well in advance once a date is confirmed.
What's the difference between prebuilt, structured/freeform, and unstructured document processing models, and which one should I use?
Prebuilt models are Microsoft's ready-to-use extractors for common document types like invoices, receipts, and contracts, you apply them directly without training, and they work well for standard formats. Structured and freeform models are for documents where information appears in consistent or semi-consistent locations, like forms or templated agreements, you train them by labeling fields in sample documents. Unstructured models are for documents that vary widely in format and composition, like legal correspondence or research reports, they classify and extract from documents that don't follow a predictable structure. Start with a prebuilt model if one covers your use case; only build custom models when prebuilt options don't fit your document type.
How do I estimate what document processing will cost before rolling it out to the whole organization?
Microsoft provides a SharePoint cost calculator specifically for this purpose, it lets you input estimated monthly usage volumes for each document processing service and get projected Azure costs. Before you use it, gather some baseline numbers: how many documents your teams upload per month across active libraries, what types of processing you plan to run on them, and which services you'll enable. Run those numbers through the calculator and add a 20–30% buffer for unexpected usage spikes, especially if you're connecting document processing to automated Power Automate flows where volume can be hard to predict. Set Azure budget alerts at that buffered number before you go live.