How to Fix Microsoft 365 Document Processing
Why This Is Happening
I've seen this exact situation play out dozens of times across enterprise tenants: an admin logs into SharePoint, tries to set up Microsoft 365 document processing , whether that's autofill columns, optical character recognition, or one of the prebuilt AI models , and hits a wall. The error message is vague, the admin center surface looks fine, but nothing actually works. Sound familiar?
Microsoft 365 document processing is a suite of pay-as-you-go AI content services that lives inside SharePoint and hooks into Azure for billing. That sentence alone tells you where most of the pain comes from. You've got three systems, Microsoft 365, SharePoint, and Azure, that all have to agree with each other before a single document gets processed. When any one of those three handshakes fails, the experience breaks silently or with a completely unhelpful error.
The most common root causes I see are:
- Azure subscription not linked correctly, the pay-as-you-go billing model requires an active Azure subscription attached to your Microsoft 365 tenant. If that link is missing, expired, or tied to the wrong subscription, every document processing service fails at the point of use.
- AI Builder credits confusion, Microsoft announced in October 2025 that AI Builder credits are being progressively discontinued. Tenants that relied on AI Builder credit-based processing are hitting unexpected "capacity unavailable" errors because the old entitlement pipeline no longer works the same way.
- GCC tenant mismatches, Government Community Cloud organizations cannot use pay-as-you-go licensing yet. If you're in a GCC environment and someone set up workflows assuming standard commercial licensing, those workflows will simply not function.
- Per-user license expiry, per-user licenses for these services are no longer sold. Organizations whose licenses lapsed without switching to pay-as-you-go find that models stop running on libraries, content assembly stops generating documents, and OCR extraction just quietly dies.
- SharePoint library model deployment failures, even when billing is fine, pushing a trained model to a document library can fail because of permission mismatches between the SharePoint site collection admin role and the Power Platform environment the model lives in.
I know this is frustrating, especially when document processing failures block actual business workflows like contract generation, invoice extraction, or regulatory compliance pipelines. The good news is that almost every one of these failures has a clear fix once you know where to look. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into model configurations and Power Platform environments, check the most common culprit first: your Azure billing connection. Ninety percent of the time, Microsoft 365 document processing fails because pay-as-you-go billing either was never set up or broke silently after an Azure subscription change.
Here's what you do. Go to the Microsoft 365 admin center, then navigate to Setup > Files and content > Automate content processes with Syntex. That path will land you on the document processing billing configuration page. Look for the section that reads "Set up pay-as-you-go billing." If you see a red banner or a "Not configured" status, that's your answer right there.
To fix it:
- Click Set up pay-as-you-go billing inside the Microsoft 365 admin center.
- You'll be prompted to link an Azure subscription. If you already have one, select it from the dropdown. If you don't, you'll need to create one in the Azure portal first, go to portal.azure.com > Subscriptions > Add.
- Select the Azure resource group you want charges billed to.
- Select the Azure region closest to your SharePoint tenant's data region. Mismatched regions can cause service meter failures even when the subscription is technically linked.
- Click Save and wait 15–20 minutes for propagation before testing any document processing feature.
Once billing is confirmed active, go back to a SharePoint document library, upload a test file, and try running OCR or autofill columns manually. If it works, you're done. If it still fails, move into the step-by-step section below.
The Microsoft 365 document processing pay-as-you-go model runs entirely on Azure service meters. If your Azure subscription is suspended, expired, or attached to the wrong tenant, document processing will silently fail, often with no error shown to end users, just a spinner that never completes.
Open the Azure portal at portal.azure.com and navigate to Subscriptions. Check that your subscription shows a status of "Active", not "Disabled," "Warned," or "Deleted." If it shows anything other than Active, click into the subscription and look at the Billing section for the specific reason (often a lapsed credit card or spending limit hit).
Next, confirm the subscription is attached to the same Azure Active Directory tenant as your Microsoft 365 organization. In the Azure portal, click your profile icon in the top-right and select Switch directory. Your Microsoft 365 tenant and Azure subscription need to be in the same directory. If they're in different directories, you'll need to transfer the subscription, go to portal.azure.com > Subscriptions > [Your Sub] > Change directory.
Run this PowerShell check to confirm your tenant ID matches between the two services:
Connect-AzAccount
(Get-AzContext).Tenant.IdCompare the output against your Microsoft 365 tenant ID, which you can find at admin.microsoft.com > Settings > Org settings > Organization profile. If they match, your subscription link is good. If they don't, that's your problem.
Even with billing correctly configured, Microsoft 365 document processing services require specific role assignments before users can create models, apply them to libraries, or trigger processing. A common mistake I see is IT admins setting up billing themselves but forgetting to delegate permissions to the people who actually need to build and deploy the content AI models.
In the Microsoft 365 admin center, go to Setup > Files and content > Automate content processes with Syntex > Manage document processing. Inside this panel, you can control which users or groups have access to specific services. Make sure the relevant users are listed under each service they need, autofill columns, document translation, OCR, eSignature, and so on.
For model creation specifically, the user also needs to be a Site Collection Administrator on the SharePoint content center site. Go to the content center site > Site Settings > Site Collection Administrators and add the user there.
For organizations using structured, freeform, or unstructured models that run through Power Platform, also check the user's role in the Power Platform admin center at admin.powerplatform.microsoft.com > Environments > [Your Environment] > Settings > Users + permissions > Users. The user needs at minimum the Basic User role in that environment, or model deployment will fail with a permissions error.
After adjusting permissions, have the user sign out of all Microsoft sessions completely, including mobile apps, and sign back in. Permission changes in Microsoft 365 and Power Platform are cached aggressively, and a fresh token is required before they take effect.
If your document processing workflows were built before late 2025, there's a good chance they were running on AI Builder credits. Microsoft announced in October 2025 that AI Builder credits are being progressively wound down. If you're seeing errors like "AI Builder capacity unavailable" or models that were working six months ago suddenly stopped running, this is why.
The fix is to migrate those workflows to the pay-as-you-go billing model. Here's what that looks like in practice.
First, identify which models are currently consuming AI Builder credits. In the Power Platform admin center, go to Resources > Capacity > Add-ons and look at the AI Builder section. Any model showing active credit consumption is a candidate for migration.
Next, confirm that pay-as-you-go billing is active for your tenant (Step 1 above). Once it's active, go to the SharePoint content center, open each affected model, and republish it. When pay-as-you-go is properly configured, republishing the model switches its billing pathway from AI Builder credits to Azure service meters automatically. You don't need to retrain the model or reconfigure the library, just republish.
After republishing, test by uploading a new file to a library where the model is applied. Watch the Status column in the document library, it should show "Processed" within a few minutes. If it shows "Failed," go to Library Settings > Document processing and check the error details shown next to the model name.
Error: AI_BUILDER_CAPACITY_EXCEEDED
Resolution: Switch billing to pay-as-you-go in M365 Admin CenterAutofill columns use large language models to extract or generate metadata from files in a SharePoint library. When this breaks, you typically see the column exist in the library but show blank values even on freshly uploaded files. No error, just nothing happening.
The most common cause is that the autofill column configuration lost its prompt or its file association after a library schema change. Here's how to diagnose and fix it.
In the SharePoint document library, click the column header for the autofill column and select Column settings > Edit. In the edit panel, scroll down to the Autofill section. You should see a prompt, something like "Extract the vendor name from this invoice." If that field is blank, the prompt was cleared. Retype or paste the original prompt back in and click Save.
If the prompt is still there, the issue is more likely a service meter problem. Run this PowerShell to check if the SharePoint tenant has document processing enabled at the tenant level:
Connect-SPOService -Url https://[yourtenant]-admin.sharepoint.com
Get-SPOTenant | Select-Object SyntexEnabled, ContentAIEnabledBoth values should return True. If either returns False, run:
Set-SPOTenant -ContentAIEnabled $trueWait 30 minutes and re-test. Autofill column processing is near real-time once the tenant setting is properly enabled, so a fresh upload should populate within 2–5 minutes under normal conditions.
Document translation and eSignature are two of the pay-as-you-go services that users interact with most visibly, and both fail in ways that are confusing because the UI gives almost no useful diagnostic feedback.
For document translation failures, the most common issue is that the source file format isn't supported, or the target language code was entered incorrectly. Microsoft 365 document translation works by creating a translated copy of a document inside the same SharePoint library, it does not modify the original. If the translated copy never appears, first check that the original file is in a supported format (DOCX, PPTX, XLSX, PDF are supported; MSG and ZIP are not). Then confirm the target language is being specified using the correct BCP-47 language tag. For example, "pt-BR" for Brazilian Portuguese, not just "Portuguese."
If the format and language are both correct and translation still fails, check the Azure service meter for document translation specifically in the Azure portal under Cost Management + Billing > Usage + charges. Filter by the resource group you selected during billing setup. If you see zero meter hits even after triggering translation, your SharePoint-to-Azure billing path is broken, re-run the pay-as-you-go setup wizard from the Microsoft 365 admin center.
For eSignature delivery failures, the most common culprit is that the recipient's email domain is blocking the eSignature request email at the mail gateway. The eSignature service sends requests from a Microsoft-owned sending domain, not your organization's domain. Ask the recipient to check their spam or quarantine folder. On your side, confirm that eSignature is enabled for your tenant under Microsoft 365 admin center > Setup > eSignature > Status: On. If it's off, toggle it on, it can take up to 24 hours to activate for the first time.
Advanced Troubleshooting
If the step-by-step fixes above haven't resolved your Microsoft 365 document processing issues, you're likely dealing with a more complex environment, domain-joined machines, custom Power Platform environments, or tenant-level policy conflicts. Here's where to look.
Checking the Unified Audit Log for Document Processing Events
The Microsoft 365 compliance portal's Unified Audit Log captures document processing activity. Go to compliance.microsoft.com > Audit > New Search, set the Activity filter to "Syntex" or "Document processing", and run the search for the time window when failures occurred. Look for events with a ResultStatus of "Failed", these will give you the actual error code rather than the vague UI message.
Common error codes you'll find there:
- SYNTEX_BILLING_NOT_CONFIGURED, Azure billing link is missing or broken
- MODEL_APPLY_PERMISSION_DENIED, user lacks site collection admin on the content center
- OCR_METER_UNAVAILABLE, OCR service meter not active in your Azure region
- TRANSLATION_QUOTA_EXCEEDED, translation meter hit a spend cap; check Azure Cost Management
Custom Power Platform Environment Issues
If your organization uses structured or freeform models deployed in a custom Power Platform environment (not the default environment), the SharePoint content center needs to be pointed at that specific environment. Inside the content center site, go to Settings (gear icon) > SharePoint Document Processing settings and confirm the Power Platform environment URL matches your custom environment. A mismatch here causes models to appear in the content center but fail silently when applied to libraries.
SharePoint Tenant-Level Policy Blocks
Some organizations have SharePoint tenant policies that block third-party content connectors or restrict data leaving the tenant boundary. Microsoft 365 document processing routes data through Azure Cognitive Services in certain scenarios. If your tenant has Information Barriers or Microsoft Purview data residency controls enabled, those policies can intercept document processing requests. Check with your compliance team whether any active policies apply to SharePoint content AI services.
GCC Tenants: What You Can and Cannot Do Right Now
Government Community Cloud organizations cannot use pay-as-you-go licensing for document processing yet. If you're in a GCC environment, you can only use document processing features if you have an active per-user license still assigned. Per-user licenses can no longer be purchased new, but existing ones can still be assigned to new users within the tenant. GCC admins need to plan for the eventual availability of pay-as-you-go in their cloud and not attempt workarounds through commercial Azure subscriptions, those connections will fail at the tenant verification layer.
Prevention & Best Practices
Once you've got Microsoft 365 document processing working correctly, keeping it working takes a small amount of ongoing attention. The pay-as-you-go model is genuinely flexible, any user in your organization with a Microsoft 365 license can use these services, but that openness is also the risk. Without guardrails, you can end up with unexpected Azure charges, models applied to the wrong libraries, or processing failures that affect real business workflows before anyone notices.
The single best thing you can do is set up an Azure spending alert on the resource group used for document processing. In the Azure portal, go to Cost Management + Billing > Budgets > Add. Set a monthly budget that reflects your expected usage and configure email alerts at 80% and 100% of that budget. This gives you early warning before a misconfigured autofill column quietly processes 200,000 files and generates a bill nobody expected.
For model governance, I strongly recommend creating a dedicated SharePoint content center site (separate from the default one) for each major business unit that uses document processing. This isolates model management, makes permissions cleaner, and means a misconfigured model in Finance doesn't accidentally affect Legal's document library. Microsoft explicitly supports multiple content centers in a single tenant.
Keep an eye on the AI Builder credits deprecation timeline. Microsoft's official documentation confirms this is a progressive end, not an instant cutoff, but the timeline is moving. Any workflow still dependent on AI Builder credits should be treated as technical debt and migrated to pay-as-you-go as a priority action this year.
Finally, document your pay-as-you-go billing configuration in your organization's IT runbook. Specifically capture: which Azure subscription is linked, which resource group document processing charges go to, and which Azure region was selected. This information is painful to reconstruct after staff turnover, and it's the first thing Microsoft Support asks for when you open a ticket.
- Set an Azure budget alert on your document processing resource group to catch unexpected charges early
- Audit all libraries with applied models quarterly, unused models left on inactive libraries still consume processing capacity
- Migrate any remaining AI Builder credit-based workflows to pay-as-you-go before your next license renewal cycle
- Add at least two site collection admins to every SharePoint content center site so model management isn't blocked by a single person being unavailable
Frequently Asked Questions
Why did my document processing models stop working after October 2025?
Microsoft announced the progressive end of AI Builder credits in October 2025. If your models were running on AI Builder credit capacity, that entitlement is being wound down. The fix is to set up pay-as-you-go billing through the Microsoft 365 admin center, then republish your models so they switch to Azure service meter billing. You don't need to retrain anything, just republish and your models will resume processing against the new billing path.
Does every user need a separate license to use Microsoft 365 document processing?
No, that's one of the genuine advantages of the pay-as-you-go model. Any user in your Microsoft 365 tenant who has a standard Microsoft 365 license can use document processing services. You don't buy per-user document processing licenses anymore (they're no longer sold). You pay based on actual usage through your Azure subscription, and the cost is spread across your organization without per-seat overhead. The exception is GCC tenants, where pay-as-you-go isn't yet available and per-user licenses are still required.
Can I use Microsoft 365 document processing if I'm a Government Community Cloud (GCC) customer?
Not with pay-as-you-go billing yet. Microsoft's official documentation confirms that pay-as-you-go licensing for document processing services is not currently available for GCC organizations. GCC tenants can still use document processing features if they have active per-user licenses assigned, those licenses can still be assigned to new users even though they can no longer be purchased new. Microsoft has indicated that pay-as-you-go will come to GCC eventually, but no firm date has been published as of April 2026.
My autofill columns show a blank value on every new file, how do I get them to actually run?
Blank autofill column values almost always mean one of two things: the autofill prompt was cleared from the column configuration, or the tenant-level content AI setting is disabled. First, edit the column and check that the prompt is still filled in. If it is, run the PowerShell command Get-SPOTenant | Select-Object ContentAIEnabled and confirm it returns True. If it returns False, run Set-SPOTenant -ContentAIEnabled $true and wait 30 minutes. Then upload a fresh test file, don't test on existing files since autofill only triggers on new uploads unless you run the model on demand.
How do I know how much my organization is spending on Microsoft 365 document processing?
All document processing charges flow through the Azure subscription you linked during billing setup. In the Azure portal, go to Cost Management + Billing > Cost analysis and filter by the resource group you assigned to document processing. You'll see line items broken out by service meter, one for OCR, one for document translation, one for autofill columns, and so on. Microsoft also offers the SharePoint cost calculator tool inside the billing setup wizard, which estimates costs based on your expected usage volume before you commit to anything.
Can I still use document processing if my per-user license expired and I haven't set up pay-as-you-go yet?
Once your per-user license expires, you lose access to document processing services until pay-as-you-go billing is configured. There's no grace period. The good news is setup is relatively quick, link your Azure subscription in the Microsoft 365 admin center, select a resource group and region, and save. After 15–20 minutes propagation, services resume. If you still have time left on your per-user license, use that window to get pay-as-you-go set up so there's no service gap at expiry. Existing licenses can still be assigned to new users until they expire, but no new per-user licenses can be purchased.