Fix Microsoft 365 Document Processing Issues
Why Microsoft 365 Document Processing Stops Working
Picture this: your team just rolled out Microsoft 365 document processing across your SharePoint libraries. Autofill columns are supposed to be pulling contract values automatically, your OCR pipeline should be indexing scanned invoices, and eSignature requests should be flying out the door. Instead, you're staring at a grayed-out button, a billing error in the Microsoft 365 admin center, or , my personal favorite , a model that ran perfectly in testing and now silently does nothing in production.
I've seen this exact scenario on dozens of tenant deployments. And the reason Microsoft 365 document processing breaks in so many different ways comes down to one thing: it's not a traditional software feature you just turn on. It's a pay-as-you-go AI service suite running on top of an Azure billing subscription, SharePoint infrastructure, and Power Platform environments, all of which have to be correctly wired together before a single page gets processed.
The most common reasons Microsoft 365 document processing fails or becomes unavailable:
- No active Azure subscription linked, The entire pay-as-you-go pricing model bills through Azure. If that subscription lapses, expires, or was never connected, every document processing service goes dark immediately. No warning, no grace period message in the UI.
- Per-user Syntex licenses expired without transition, Microsoft rebranded these services away from the old "Microsoft Syntex" branding, and per-user licenses are no longer sold. Tenants coasting on legacy per-user licenses who didn't migrate to pay-as-you-go now find their models won't apply to new content.
- AI Builder credits exhausted or discontinued, In October 2025, Microsoft announced a progressive end to AI Builder credits. If your workflows were relying on those credits to process documents, that pipeline is now broken and needs to move to the Azure-billed pay-as-you-go model.
- Wrong Power Platform environment for custom models, Structured and freeform models built in a custom Power Platform environment have a completely separate setup requirement that catches teams off guard.
- Government Community Cloud (GCC) tenant, Pay-as-you-go billing is not yet available for GCC organizations. If you're in a GCC tenant, you're limited to per-user licenses until Microsoft rolls out support.
- Service region mismatch, The worldwide (WW18) service endpoint covers most commercial tenants, but mismatches between your tenant's home region and service routing can cause silent failures, especially after tenant migrations.
The frustrating part is that Microsoft's error messages in the admin center don't tell you which of these is the actual problem. You just see "Service unavailable" or the configuration options are missing entirely. That's why I wrote this guide, to work through each failure mode systematically. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you spend an hour diagnosing, run through this single check first. In roughly 60% of cases I've seen, Microsoft 365 document processing failures trace back to one root cause: the pay-as-you-go billing connection between your Microsoft 365 tenant and your Azure subscription is broken or was never completed.
Here's how to verify it in under five minutes:
- Sign in to the Microsoft 365 admin center at
admin.microsoft.comwith a Global Administrator account. - In the left navigation, expand Setup and select Files and content.
- Look for the Document processing section. If you see a banner that reads "Set up pay-as-you-go billing to use this service," that confirms billing isn't connected.
- Click Set up pay-as-you-go. You'll be asked to select an active Azure subscription, a Resource Group, and a Region.
- Select your Azure subscription from the dropdown. If no subscriptions appear, your admin account doesn't have Owner or Contributor rights on any Azure subscription, that needs to be fixed at the Azure portal level first.
- Complete the wizard. Once saved, return to the document processing settings and the service options should now appear fully enabled.
If billing was already set up and everything looks connected, check the Azure subscription status directly. Go to portal.azure.com → Subscriptions → find the one linked to document processing → confirm its status shows Active, not Disabled or Expired. A disabled subscription is an instant, silent kill switch for every Microsoft 365 document processing service in your tenant.
This is the foundation everything else depends on. Microsoft 365 document processing, including OCR, autofill columns, document translation, eSignature, content assembly, image tagging, taxonomy tagging, and all the AI models, requires an active Azure subscription wired to your tenant. No billing connection, no services. It's that binary.
To set up or repair the billing connection:
- Open the Microsoft 365 admin center (
admin.microsoft.com). - Navigate to Setup → Files and content.
- Under Document processing, click Manage document processing.
- If billing isn't configured, click Set up pay-as-you-go billing.
- In the panel that opens, select:
- Azure subscription, must be Active status
- Resource group, create a new one if needed, e.g.,
rg-m365-docprocessing - Region, match your tenant's primary data region
- Accept the terms and click Save.
If the Azure subscription dropdown is empty, your Microsoft 365 global admin account isn't linked to any Azure subscription with sufficient permissions. Fix this in the Azure portal: go to Subscriptions → select your subscription → Access control (IAM) → Add role assignment → assign Owner or Contributor to your admin account.
Once saved, refresh the admin center page. You should now see the full list of document processing services available for configuration. If you see them, billing is working.
If your organization purchased per-user licenses under the old Microsoft Syntex model, you're in a transition period. These licenses are no longer available for new purchases, but existing ones remain valid until they expire. The catch is that once they expire, you have to switch to pay-as-you-go, there's no renewal path.
To check your current license status:
- In the Microsoft 365 admin center, go to Billing → Your products.
- Search for "Syntex" or "document processing" in the product list.
- Note the expiration date on any per-user licenses shown.
If licenses are still active, you can continue to:
- Apply unstructured models to document libraries
- Create prebuilt, structured, and freeform models
- Upload content to libraries that have models applied
- Run models on demand
- Use content assembly and taxonomy services
- Use content query and annotations
- Use document library rules for automation
If your licenses have expired, those same features will stop working until you have pay-as-you-go billing set up. The transition is not automatic. Users will not get a clear error message, features simply stop being available in SharePoint.
My strong recommendation: set up pay-as-you-go billing before your per-user licenses expire. Run them in parallel during the overlap period so you can verify everything works under the new billing model without any service gap. Then let the old licenses expire gracefully.
Even with billing properly configured, each Microsoft 365 document processing service has to be individually enabled in the admin center before users can access it. I've seen admins set up billing, hand the keys to a department, and then spend two days troubleshooting why eSignature "isn't working", only to find it was never toggled on.
To enable specific document processing services:
- In the Microsoft 365 admin center, go to Setup → Files and content → Manage document processing.
- You'll see a list of all available services:
- Autofill columns
- Document translation
- eSignature
- Optical character recognition (OCR)
- Content assembly
- Image tagging
- Taxonomy tagging
- Prebuilt document processing
- Structured and freeform document processing
- Unstructured document processing
- Toggle on each service your organization needs.
- For services that require additional configuration (such as eSignature, which needs a site collection-level setup), follow the additional setup link that appears after enabling.
Keep in mind: enabling a service in the admin center doesn't automatically apply it to any SharePoint library. That's a second step done at the library level by a site owner or admin. Enabling in the admin center simply makes the feature available, not active.
After toggling services on, wait up to 15 minutes for provisioning to complete before testing. Changes don't take effect instantaneously across a global tenant.
Once billing and service enablement are correct, the next failure tier involves AI models not running on documents in SharePoint. This shows up as: files are uploaded to a library with a model applied, but columns remain blank, classification doesn't fire, or extracted fields aren't populated.
Walk through this diagnostic sequence:
Check that the model is actually applied to the library:
- Open the SharePoint document library.
- Click the gear icon → Library settings.
- Under Document processing models, confirm a model is listed and shows a green status.
Verify processing rules and triggers:
- In the library settings, check Content processing rules.
- Confirm the rule condition is set correctly (e.g., "When a file is created or modified").
- If using on-demand processing, confirm users know they need to right-click a file → Classify and extract manually.
Run an on-demand test:
- Upload a test file that matches your model's training data type.
- Right-click the file → Classify and extract.
- Wait 30–60 seconds and refresh. If columns populate, processing is working but your automatic trigger rule may be misconfigured.
If on-demand processing also fails, note any error messages. A "quota exceeded" error means your Azure subscription has hit a spending limit. A "permission denied" error usually means the service identity doesn't have the right SharePoint site permissions, something that happens after site permission audits or migrations.
In October 2025, Microsoft announced the progressive end of AI Builder credits. If your document processing workflows, particularly Power Automate flows that invoke document parsing, form processing, or prediction models, were built on AI Builder credits, those workflows are breaking or will break. This is not a bug. It's a platform transition, and it requires deliberate action on your part.
To identify affected flows:
- Open Power Automate at
make.powerautomate.com. - Click My flows → sort by Modified to find recently failing flows.
- Open each flow and look for any steps using AI Builder actions, these will have the AI Builder connector icon.
For each affected flow, you have two options:
Option A, Migrate to document processing native models: If the AI Builder action was doing document classification or extraction, rebuild it using a Prebuilt, Structured, or Unstructured document processing model in SharePoint directly. This eliminates the Power Automate dependency for the extraction step.
Option B, Re-license with pay-as-you-go: Certain AI Builder actions can continue to run under pay-as-you-go billing. Check the End of AI Builder credits article in the Microsoft docs for the specific list of actions that transition to Azure-billed consumption vs. those being fully discontinued.
# PowerShell: list all Power Platform solutions in an environment
# Run in Power Platform CLI (pac)
pac solution list --environment YOUR_ENVIRONMENT_IDThe sooner you audit your Power Automate flows for AI Builder dependencies, the less emergency scrambling you'll face. I've seen organizations get blindsided by this in production because a flow that ran daily for two years just quietly started failing.
Advanced Troubleshooting for Microsoft 365 Document Processing
GCC Tenant Limitations
If your organization is in a Government Community Cloud (GCC) environment, the pay-as-you-go model isn't available yet, full stop. Your only option is to continue with per-user licenses until Microsoft extends pay-as-you-go support to GCC tenants. Check the Microsoft 365 roadmap at aka.ms/m365roadmap and filter on "Syntex" or "document processing" to track when GCC support is coming. In the meantime, document what features your teams need now so you're ready to migrate the moment the service becomes available.
Custom Power Platform Environment Setup
If you're using structured or freeform document processing models in a custom Power Platform environment (not the default), there's an additional setup requirement that the main admin center wizard doesn't surface clearly. You must explicitly configure the custom environment for document processing:
- Go to
admin.powerplatform.microsoft.com. - Select your custom environment → Settings → Features.
- Under AI Builder, ensure document processing is enabled for this environment.
- Back in the Microsoft 365 admin center, under document processing settings, confirm the correct Power Platform environment is selected for model deployment.
Event Viewer and ULS Logs for SharePoint On-Premises Integration
For hybrid deployments that connect SharePoint on-premises content to cloud document processing services, failures often surface in the SharePoint on-premises ULS logs. On your SharePoint server, use the ULS Viewer tool and filter by correlation ID. Look for entries tagged with category Syntex or ContentUnderstanding. A log entry like Unauthorized: Bearer token validation failed means the hybrid connector's OAuth token has expired and needs re-authorization through the SharePoint Hybrid Configuration Wizard.
Tenant Geo and Service Routing
For multi-geo Microsoft 365 tenants, document processing services need to be enabled per satellite location. A document uploaded in a satellite geo location won't be processed by a model that was only enabled for the primary geo. In the admin center, go to Settings → Org settings → Services and check document processing configuration for each geo location you've provisioned.
SharePoint Cost Calculator
If you're seeing unexpectedly high Azure bills from document processing, use the SharePoint cost calculator (linked from the pay-as-you-go pricing page in Microsoft docs) to model your actual usage patterns against the service meters. Each service type (OCR pages processed, translation characters, eSignature requests, model transactions) bills on a separate Azure meter. Understanding which meter is driving cost lets you optimize, for example, batching OCR jobs during off-peak hours or capping daily model runs.
Prevention & Best Practices for Document Processing in Microsoft 365
After you've fixed the immediate problem, there are several things you should put in place to make sure document processing stays healthy in your tenant long-term. The pay-as-you-go model means the service is tied to infrastructure that needs ongoing monitoring, unlike traditional software licenses, you can't just "set and forget" it.
Monitor Azure subscription health actively. Your Azure subscription is the single point of failure for all Microsoft 365 document processing services. If it gets suspended, whether for non-payment, spending limit hit, or an admin accidentally disabling it, every service goes offline instantly. Set up Azure Monitor alerts for subscription state changes and assign at least two billing admins to avoid single-person dependency.
Document your model configurations before making changes. Before modifying a deployed document processing model, even minor training updates, export the model configuration. For structured and freeform models, screenshot every field definition and extraction zone. Models don't have a built-in version history that's easy to roll back from. If a training update makes a model less accurate, you'll wish you had that baseline documentation.
Test processing in a staging library before production rollout. Create a dedicated SharePoint document library for testing, something like DocProcessing-Test, and always validate model behavior there first with a representative sample of real documents. Production document libraries serving live business workflows are not the place to discover that your contract model misclassifies NDAs as MSAs.
Plan the AI Builder credit transition now if you haven't already. Any Power Automate workflow touching AI Builder needs to be audited and either migrated or decommissioned. Set a deadline for completing this audit, don't let it drift. The end of AI Builder credits is a hard deprecation, not a soft one.
Keep a record of which users and site owners have access to model creation. Document processing model creation should be governed, not open-ended. In large organizations, uncontrolled model proliferation leads to billing surprises, inconsistent classification results, and maintenance headaches. Restrict model creation rights in the admin center and require a lightweight approval process before new models go live.
- Set Azure budget alerts at 80% and 100% of your expected monthly document processing spend, go to Azure Portal → Cost Management + Billing → Budgets
- Review the SharePoint cost calculator quarterly to ensure your Azure budget matches actual usage growth
- Run a monthly audit of all document libraries with active models, remove models from libraries where they're no longer needed to avoid unnecessary processing charges
- Keep at least one Global Administrator and one Azure Owner/Contributor role assignment in separate user accounts, so a single account compromise or departure doesn't lock you out of billing administration
Frequently Asked Questions
Why are my document processing options completely missing from the SharePoint admin center?
This almost always means pay-as-you-go billing hasn't been configured for your tenant, or your Azure subscription was disabled. Sign in to the Microsoft 365 admin center as a Global Administrator, go to Setup → Files and content, and look for the document processing section. If you see a setup prompt instead of configuration options, follow the pay-as-you-go billing wizard to connect an active Azure subscription. Also double-check in the Azure portal that your subscription shows "Active" status, a disabled subscription makes every document processing option disappear without any clear error in the Microsoft 365 UI.
We had Microsoft Syntex licenses, do we need to do anything after the rebranding?
The rebranding from Microsoft Syntex to document processing for Microsoft 365 didn't change any features or break any existing configurations, your models and workflows remain intact. What you do need to act on is the license transition. Per-user Syntex licenses are no longer sold, and once your existing ones expire, there's no renewal path. Before expiration, set up pay-as-you-go billing in the admin center so you have uninterrupted service. Running both in parallel during the overlap period is the safest approach, it lets you confirm the new billing model works before the old licenses run out.
My autofill columns aren't extracting anything from uploaded files, they just stay blank. What's wrong?
Blank columns after upload usually mean either the model isn't configured to run automatically, or the uploaded file type isn't supported by the model. First, check your content processing rules in the library settings, make sure you have a rule set to trigger on file creation or modification. Second, verify the file type is supported: autofill columns work best with standard Office formats and PDFs, not custom formats or password-protected files. If rules are correct and the file type is valid, try running "Classify and extract" manually by right-clicking the file, if that works, your automatic trigger is the issue; if that also fails, check your Azure billing and model status in the admin center.
Can users in a GCC tenant use Microsoft 365 document processing?
Currently, no, not with pay-as-you-go billing. Government Community Cloud organizations are explicitly excluded from pay-as-you-go licensing as of now, which means they also can't access any of the services that require it. GCC organizations can continue using document processing services as long as they have valid per-user licenses. Since per-user licenses are no longer sold new, if your GCC organization doesn't already have them, you're in a holding pattern until Microsoft extends pay-as-you-go to GCC. Monitor the Microsoft 365 roadmap at aka.ms/m365roadmap for updates.
Our Power Automate flows that used AI Builder are now failing, what do we do?
Microsoft announced the end of AI Builder credits in October 2025, which is what's breaking your flows. You have two paths forward: migrate the document processing steps to native SharePoint document processing models (which bill through Azure under pay-as-you-go instead), or check whether the specific AI Builder actions you're using are transitioning to Azure-billed consumption rather than being fully discontinued, refer to the End of AI Builder credits article in Microsoft's official documentation for the definitive list. Either way, this requires deliberate migration work; the flows won't self-heal. Audit all flows with AI Builder steps immediately, prioritize the ones running in production, and schedule a migration sprint.
How much does Microsoft 365 document processing actually cost per month?
The answer varies significantly because each service type has its own Azure billing meter, there's no flat monthly fee. OCR bills per page processed, document translation bills per character, eSignature bills per request, and AI model transactions (for prebuilt, structured, freeform, and unstructured models) bill per transaction. Microsoft provides the SharePoint cost calculator (accessible from the pay-as-you-go pricing page in the official docs) specifically to help estimate costs based on your organization's document volumes. For rough planning: a mid-size organization processing a few thousand documents per month typically sees Azure charges in the tens to low hundreds of dollars range, but high-volume scenarios like invoice processing pipelines can run significantly higher. Set Azure budget alerts from day one rather than discovering the bill at month-end.