Fix Microsoft 365 Document Processing Issues
Why This Is Happening
I've helped dozens of IT admins and SharePoint owners who've run into the same wall: Microsoft 365 document processing just... stops. Or never starts. You set it up, you follow what feels like the right path, and then you're staring at a grayed-out button, a billing error, or a model that won't apply to your library. It's maddening , especially when the work your team depends on is sitting in a queue going nowhere.
Here's the honest answer on why this happens so often: Microsoft 365 document processing is built on a pay-as-you-go service layer tied directly to an Azure subscription. That means the failure point isn't always SharePoint itself , it's the billing pipeline underneath it. If your Azure subscription isn't active, isn't linked correctly, or has lapsed, every document processing feature from autofill columns to unstructured model processing will silently fail or show no option at all in your SharePoint admin center.
The second big culprit is the licensing transition. Microsoft officially ended the sale of per-user licenses for document processing services. If your organization was running on those old per-user licenses, previously sold under the Microsoft Syntex brand, you've been migrated (or need to migrate) to pay-as-you-go. If that migration didn't happen cleanly, you'll see services appear available in the interface but refuse to run when triggered. Your models exist. Your libraries are configured. But nothing processes.
A third scenario hits enterprise customers hard: AI Builder credits. In October 2025, Microsoft announced a progressive end to AI Builder credits. Teams that were relying on AI Builder credit consumption to power their document processing flows are now hitting hard stops. The credit pool is draining, and without switching to the metered Azure billing model, processing jobs queue up and never execute.
There's also the GCC (Government Community Cloud) factor. If your organization is on a GCC tenant, pay-as-you-go licensing is not yet available for document processing. That means certain services, like document translation, eSignature, and autofill columns, simply won't be accessible until Microsoft rolls out GCC support. This isn't a bug. It's a documented limitation that Microsoft support will confirm, but the error messages you see in the portal rarely spell it out that clearly.
Finally, there are plain configuration mistakes: Azure billing wasn't set up on the right subscription, the SharePoint admin didn't enable the specific service in the Microsoft 365 admin center, or a Power Platform environment was created without the proper document processing model support enabled.
Whatever your situation, this guide walks through every major fix path. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into logs or admin consoles, do this single check first. It resolves about 60% of Microsoft 365 document processing issues I see.
Go to the Microsoft 365 admin center at admin.microsoft.com. In the left navigation, expand Settings, then click Org settings. Scroll down to find SharePoint under the Services tab and verify that document processing services are enabled for your tenant.
Now navigate separately to the SharePoint admin center. Under Settings, look for Document processing. This is where pay-as-you-go billing gets linked to your Azure subscription. If you see a banner that says "Billing not configured" or "Set up pay-as-you-go to use this service," that's your answer right there. No billing link, no processing, it's that simple.
To link your Azure subscription: click Set up pay-as-you-go billing, sign in with your Azure credentials (you need to be an Owner or Contributor on the Azure subscription), select the correct subscription and resource group, then confirm. Once saved, give it 10–15 minutes to propagate. Refresh your SharePoint library and try applying your model again.
If billing was already linked and you're still seeing issues, check the Azure subscription status directly at portal.azure.com. Go to Subscriptions, select your subscription, and confirm the status shows Active. A disabled or suspended Azure subscription will silently block all document processing meters even though SharePoint shows no obvious error.
One more quick check: in the SharePoint admin center under document processing settings, confirm that the specific service you're trying to use, whether that's autofill columns, document translation, OCR, or eSignature, is toggled on. Each service has its own enable/disable switch. It's surprisingly easy to have pay-as-you-go billing set up but a specific service still turned off.
This is step one for a reason. Every document processing service in Microsoft 365, autofill columns, document translation, eSignature, optical character recognition, content assembly, image tagging, taxonomy tagging, and all three model types, runs on pay-as-you-go billing against an Azure subscription. If this link is broken or missing, nothing else matters.
Open the SharePoint admin center (yourtenant-admin.sharepoint.com) and sign in as a Global Administrator or SharePoint Administrator. In the left sidebar, select Settings. You'll see a section called Document processing, click it.
If billing isn't configured, you'll see a setup prompt. Click Set up billing. A side panel opens asking you to choose your Azure subscription. You need to be an Owner or Contributor on that Azure subscription, if you're not, coordinate with your Azure admin before proceeding.
Select your Azure subscription from the dropdown. Choose or create a resource group (creating a dedicated one like rg-sharepoint-docprocessing is ideal). Select your Azure region, choose the region closest to your Microsoft 365 tenant's data residency location for best performance. Click Save.
After saving, head to portal.azure.com and navigate to Cost Management + Billing → Cost analysis. Filter by your new resource group. Within 24 hours of first use, you'll start seeing meters appear here: one per service type used.
# PowerShell: Check your SharePoint tenant's current billing status
Connect-SPOService -Url https://yourtenant-admin.sharepoint.com
Get-SPOTenant | Select-Object -Property SyntexPayAsYouGoBillingEnabledIf SyntexPayAsYouGoBillingEnabled returns False, billing is not active regardless of what the UI shows. Repeat the setup steps above.
Pay-as-you-go billing being active doesn't automatically turn on every document processing service. Each service has its own toggle in the SharePoint admin center. This catches a lot of people off guard, they set up billing, go to their SharePoint library, and find the feature is still missing from the menu. The services aren't enabled by default.
In the SharePoint admin center, go to Settings → Document processing. You'll see a list of available services. The services available on pay-as-you-go include:
- Autofill columns, uses LLMs to extract or generate content for library columns automatically
- Document translation, creates translated copies of documents while preserving formatting
- eSignature, sends electronic signature requests keeping documents inside Microsoft 365
- Optical character recognition (OCR), extracts printed or handwritten text from images
- Content assembly, generates standard repetitive business documents from templates
- Image tagging, finds, sorts, and filters images in document libraries
- Taxonomy tagging, automatically tags terms and term sets to files
- Prebuilt models, processes contracts, invoices, receipts without training from scratch
- Structured and freeform models, extracts information from forms, letters, contracts
- Unstructured models, classifies documents that vary widely in structure
Toggle on each service you need. Changes take effect within a few minutes. After enabling, go to your SharePoint document library, click the top-level Automate menu, then Document processing. You should now see the newly enabled service options appear.
If you enable a service and it doesn't show up in the library menu after 10 minutes, do a hard browser refresh (Ctrl+Shift+R) and try in a private/incognito window to rule out a caching issue.
If your organization purchased per-user licenses for Microsoft Syntex (now document processing) before the licensing model changed, you're in a transitional state. Those per-user licenses are no longer sold, but existing licenses can still be assigned to users. Here's the catch: once they expire, you must be on pay-as-you-go to continue using any document processing service.
To check your current license status, go to the Microsoft 365 admin center, then Billing → Your products. Search for "Syntex" or "Document processing." Note the expiry date on any per-user licenses showing there.
With an active per-user license, users can still:
- Apply unstructured models to libraries
- Create prebuilt, structured, and freeform models
- Upload content to libraries with applied models
- Run models on demand
- Use content assembly and taxonomy services
- Use content query and annotations
- Use document library rules for automation
What you cannot do on a per-user license alone is access pay-as-you-go exclusive services like document translation, eSignature, and OCR as metered features. Those require billing to be set up.
To prepare for the transition before your per-user license expires, set up pay-as-you-go billing now (Step 1 above) so it runs in parallel. This ensures zero downtime when the per-user license lapses. Once pay-as-you-go is active, all services move to metered billing automatically.
# Check which users have Syntex per-user licenses assigned
Connect-MsolService
Get-MsolUser -All | Where-Object {$_.Licenses.AccountSkuId -like "*Syntex*"} |
Select-Object DisplayName, UserPrincipalNameDocument that list. When the license expires, those users shift to pay-as-you-go consumption automatically, assuming billing is configured.
If your document processing workflows were running on AI Builder credits and they've suddenly stopped or are running slower than normal, there's a direct cause: Microsoft announced in October 2025 that AI Builder credits are being progressively ended. This isn't a temporary glitch, it's a permanent platform change.
First, audit your current AI Builder credit status. Go to powerapps.microsoft.com, then navigate to Settings (gear icon) → Admin center → Resources → Capacity. Look under the AI Builder section. If your allocated credits are at zero or near-zero, your document processing jobs that were running through Power Automate flows connected to AI Builder models are now failing silently or queuing indefinitely.
The fix is to re-route those workflows to use the pay-as-you-go document processing services instead of AI Builder credit-consuming models. This involves:
- Opening your Power Automate flow that calls the AI Builder model
- Replacing the AI Builder → Process and save information from documents action with the equivalent SharePoint-native document processing model trigger
- Updating the output field mappings to match the new action's response schema
- Saving and testing the flow with a real document
For structured or freeform models running in a custom Power Platform environment, Microsoft requires a specific setup path. You need to configure the custom environment to connect to your pay-as-you-go billing setup. This is done in the Power Platform admin center under Environments → [your environment] → Settings → Product → Features, enabling the document processing integration toggle there.
# Check AI Builder capacity remaining via Power Platform admin
# Run this in Power Platform CLI (pac)
pac admin list --environment "YourEnvironmentName"If you're seeing Event ID errors in Power Automate run history, look for error code AiBuilderCapacityExceeded or CreditAllocationFailed in the run detail pane, these confirm the AI Builder credit exhaustion is the root cause.
Once billing is active and services are enabled, you may still hit service-specific errors. Here's what I've seen most often for each service:
Optical Character Recognition (OCR) not extracting text: OCR in SharePoint works on images uploaded to a document library. It does not retroactively process images that existed before OCR was enabled. After enabling OCR in the admin center, only newly uploaded images get processed. To process existing files, select them in the library, click Automate → Document processing → Run OCR manually. If that option is missing, confirm the file type is supported (JPEG, PNG, TIFF, BMP, not PDF pages directly).
Document translation producing no output file: Translation creates a copy of the document in the selected language, it doesn't overwrite the original. If you don't see the translated copy appear in the library, check whether the library has sufficient storage quota (go to Library settings → Storage metrics). Also confirm the target language you selected is in Microsoft's supported languages list; unsupported language codes silently fail without an error notification in most tenant configurations.
eSignature requests not sending: eSignature requires that the document is stored in a SharePoint document library, not OneDrive. Requests initiated from OneDrive personal storage will fail. Also ensure your tenant's external sharing settings allow the signature recipient's email domain, if external sharing is blocked at the tenant level, the eSignature invite email goes out but the recipient lands on an access-denied page.
Autofill columns returning empty values: Autofill uses LLMs to extract or generate content. If columns are coming back empty, the most common cause is a column prompt that's too vague. Go to the library column settings, select Edit autofill column, and review your prompt. Be specific: instead of "What is this document about?" use "Extract the vendor name from the invoice header. Return only the company name, no other text." Specificity dramatically improves extraction accuracy.
# PowerShell: Check if document processing models are applied to a library
$siteUrl = "https://yourtenant.sharepoint.com/sites/yoursite"
Connect-PnPOnline -Url $siteUrl -UseWebLogin
Get-PnPSyntexModel -List "Documents"A clean result here shows which models are applied and their processing status. If no models appear despite your configuration, the model wasn't successfully published, go back to Content center → Models and confirm the model status shows Published, not Draft.
Advanced Troubleshooting
If the step-by-step fixes above haven't resolved your Microsoft 365 document processing issue, you're likely dealing with an enterprise configuration problem, Group Policy interference, a complex Azure subscription hierarchy, a domain-joined device issue, or a Power Platform environment misconfiguration. Here's where to dig deeper.
Event Viewer analysis on the processing trigger machine: For document processing jobs triggered through Power Automate, check the Windows Event Viewer on the machine running the on-premises data gateway (if applicable). Navigate to Event Viewer → Applications and Services Logs → Microsoft → PowerPlatform. Look for Event IDs in the 1000–1099 range, these log gateway communication failures that prevent document processing actions from firing. Event ID 1005 specifically indicates a credential expiry on the gateway service account.
Azure subscription scope issues in large enterprises: In organizations with multiple Azure subscriptions under an Enterprise Agreement, the subscription linked in SharePoint's pay-as-you-go setup must be within a subscription that the SharePoint admin has at minimum Contributor access to at the subscription scope (not just resource group scope). If your Azure RBAC grants you Contributor only at the resource group level, the SharePoint admin center billing setup will fail with a nondescript "Unable to complete setup" error. Have your Azure subscription owner elevate your access temporarily to complete the link.
Conditional Access policy blocking document processing services: Azure AD Conditional Access policies that restrict access to Microsoft Azure Management (797f4846-ba00-4fd7-ba43-dac1f8f63013) can block the pay-as-you-go billing setup wizard from completing because it needs to call Azure Resource Manager APIs. If you're in a highly secured tenant with strict Conditional Access, your admin needs to create a Conditional Access exclusion for the billing setup process or use the Azure portal directly to create the resource group and then have the SharePoint admin reference that pre-created resource group during setup.
Custom Power Platform environments: If you're running document processing models in a custom Power Platform environment (not the default environment), that environment needs to be explicitly linked to pay-as-you-go billing. This is separate from the SharePoint admin center setup. In the Power Platform admin center, go to Environments → [your environment] → Settings → Features and enable the document processing billing integration. Without this step, models created in the custom environment won't meter correctly against your Azure subscription and will either fail or consume AI Builder credits instead.
SharePoint cost calculator for pre-migration planning: Before enabling services at scale, use the SharePoint cost calculator (available from the Microsoft 365 admin center) to model your expected monthly Azure spend. Upload your document processing volume estimates and it will project per-service meter costs. This prevents surprise Azure bills and helps you decide which services to enable first during a phased rollout.
# Advanced: Get document processing model metrics via PnP PowerShell
$siteUrl = "https://yourtenant.sharepoint.com/sites/contentcenter"
Connect-PnPOnline -Url $siteUrl -UseWebLogin
$models = Get-PnPSyntexModel
foreach ($model in $models) {
Write-Host "Model: $($model.Name) | Status: $($model.PublicationStatus) | Type: $($model.ModelType)"
}Prevention & Best Practices
Once your Microsoft 365 document processing setup is working, keeping it working requires a bit of proactive management. I've seen too many organizations go through the whole setup process, celebrate when it works, and then come back six months later wondering why everything broke again. Here's how to avoid that.
Monitor your Azure subscription health monthly. Document processing is completely dependent on your Azure subscription remaining active. Set up Azure Cost Management budget alerts at 80% and 100% of your expected monthly document processing spend. This catches unexpected volume spikes before they cause billing issues. Go to portal.azure.com → Cost Management + Billing → Budgets and create a budget scoped to your document processing resource group.
Don't rely on AI Builder credits for production workflows. With AI Builder credits being progressively ended from October 2025 onward, any production document processing workflow that depends on AI Builder credit consumption is living on borrowed time. Audit your Power Automate flows now. Any flow using AI Builder → Process and save information from documents actions should be migrated to the SharePoint-native document processing model triggers, which meter against pay-as-you-go Azure billing instead.
Keep track of per-user license expiry dates. If your organization still has active per-user Syntex licenses, note their expiry date in your IT calendar with a 60-day advance reminder. Set up pay-as-you-go billing at least 30 days before expiry to allow time for any issues to surface and be resolved before the license gap hits production.
Test models in a staging library before production rollout. Unstructured models, in particular, can behave differently across document populations than they did in training. Create a staging SharePoint document library with 50–100 representative documents and apply the model there first. Review extraction accuracy before enabling it on your main production library. This is especially important for prebuilt models processing contracts and invoices, field mapping errors in production can corrupt metadata at scale.
GCC tenants: watch for the pay-as-you-go rollout announcement. If you're on a Government Community Cloud tenant, pay-as-you-go services are not yet available. Keep an eye on the Microsoft 365 Message Center (in the admin center under Health → Message center) for MC posts announcing GCC pay-as-you-go availability. Subscribe to those Message Center notifications by email so you don't miss the rollout window.
- Set Azure Cost Management budget alerts at 80% threshold on your document processing resource group, catch billing surprises before they become service disruptions
- Audit all Power Automate flows using AI Builder actions and migrate them to SharePoint-native document processing triggers before your AI Builder credit pool expires
- Create a dedicated Azure resource group (e.g.,
rg-m365-docprocessing) for all document processing meters, makes cost reporting and troubleshooting dramatically easier - Test every new document processing model on a staging library with representative documents before applying to production, unstructured model accuracy varies significantly with document diversity
Frequently Asked Questions
Why can't I see document processing options in my SharePoint library even though I'm a site owner?
Being a site owner gives you permissions within that site, but document processing services are enabled at the tenant level by a SharePoint Administrator or Global Administrator. The options won't appear in any library until an admin has both set up pay-as-you-go billing in the SharePoint admin center AND toggled on the specific services you need. Contact your Microsoft 365 admin and ask them to check SharePoint admin center → Settings → Document processing. Once enabled at the tenant level, the options appear in your library's Automate menu within about 10 minutes.
How much does Microsoft 365 document processing actually cost per month?
There's no flat monthly fee, you pay only for what you use through Azure metered billing. Each service has its own per-transaction rate that Microsoft publishes on the document processing pricing page. For planning purposes, use the SharePoint cost calculator available in the Microsoft 365 admin center. It lets you input your estimated document volumes and see projected monthly costs by service type. During a trial period through December 2025, Microsoft offered included free capacity each month for selected services, but that offer has concluded and all usage is now billed from the first transaction.
My organization is on Government Community Cloud (GCC), why can't I set up pay-as-you-go document processing?
This is a known, documented limitation. Pay-as-you-go licensing for document processing is not yet available for GCC tenants. Microsoft's official guidance is that GCC organizations can continue to purchase and use per-user licenses until pay-as-you-go becomes available in the government cloud. Watch your Microsoft 365 Message Center for announcements about GCC availability. In the meantime, if you have existing per-user licenses, keep them active, you can still assign them to new users, create and run models, and use content assembly and taxonomy services under the per-user license model.
What happened to Microsoft Syntex? Is it the same as document processing?
Yes, functionally identical. Microsoft rebranded the pay-as-you-go services previously offered under the "Microsoft Syntex" name to "document processing services for Microsoft 365." The features, capabilities, and underlying technology are unchanged, Microsoft just updated the product name and the documentation references. If you've been searching for Syntex troubleshooting information and landing on older articles, the settings and steps still apply; just look for "document processing" in the admin center rather than "Syntex." Your existing Syntex models, content centers, and configurations are fully compatible.
My document translation created the file but it's in the wrong language, how do I fix that?
Document translation in SharePoint creates a translated copy in your selected target language while preserving the original file's format and structure. If the output language is wrong, the most likely cause is that you selected the wrong language code during the translation request, some language codes look similar (e.g., pt for Portuguese vs. pt-BR for Brazilian Portuguese, or zh-Hans for Simplified Chinese vs. zh-Hant for Traditional Chinese). Delete the incorrectly translated copy, go back to the original file, click Automate → Document processing → Translate document, and re-select your target language carefully. All supported languages and their dialect codes are listed in the official Microsoft document translation documentation.
Can I use document processing if I don't have an Azure subscription?
No, an active Azure subscription is a hard requirement for pay-as-you-go document processing services. There is no way to use these services without one. If your organization doesn't have an Azure subscription yet, you'll need to create one at portal.azure.com before you can set up billing in the SharePoint admin center. Microsoft offers a free Azure trial tier, but for production document processing use you'll want a paid subscription to avoid service interruptions when the free trial expires. Once you have an active Azure subscription, the setup in SharePoint admin center takes about 5 minutes.