Fix Microsoft 365 Document Processing Not Working
Why Microsoft 365 Document Processing Stops Working
You open a SharePoint document library, you're ready to run a model, extract data from invoices, or kick off a document translation , and nothing. The option is greyed out, the service throws a vague error, or the whole feature set just isn't there. I've seen this exact scenario on dozens of tenant configurations, and the root cause almost always comes down to one of three things: billing isn't wired up correctly, the licensing model changed under your organization's feet, or the service isn't enabled at the tenant level yet.
Here's the thing Microsoft's error messages won't tell you: the document processing services in Microsoft 365 , everything from autofill columns to unstructured AI models, all went through a significant architectural shift. What used to be called Microsoft Syntex is now document processing for Microsoft 365, and the entire billing model moved to pay-as-you-go. That sounds simple, but the migration caused real confusion for organizations worldwide. Per-user licenses stopped being sold. AI Builder credits, which powered many of these features behind the scenes, were officially announced as end-of-life in October 2025. If your tenant was running on any of those older mechanisms, things break silently.
The other issue I see constantly in enterprise environments: someone sets up the Azure subscription link at the billing level, but the wrong subscription gets selected, or the subscription is in a different tenant region. Microsoft 365 document processing billing flows through Azure, and if that connection is broken or misconfigured, every single AI-powered document service goes offline. No warning. Just grayed-out buttons and confused end users filing help desk tickets.
Who typically hits these problems? IT admins inheriting a tenant they didn't originally configure. Organizations that were on legacy Syntex per-user licenses and didn't realize those licenses expired. Teams running SharePoint Online who turned on document processing features during the free trial window (which ran through December 2025) and never set up real billing before it ended. And, frustratingly, Global Cloud Coverage (GCC) customers who discover that pay-as-you-go isn't available for their environment yet and don't know what that means for their setup.
I know this is frustrating, especially when it blocks real business workflows like contract review or invoice processing. Let's walk through every fix. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before diving into the full troubleshooting steps, run through this check. It resolves the majority of Microsoft 365 document processing issues in under five minutes.
Open the Microsoft 365 admin center at admin.microsoft.com. In the left-hand navigation, go to Settings > Org settings > Services and scroll until you see SharePoint. This won't directly show you document processing status, but it confirms your baseline SharePoint Online configuration is active.
Now navigate directly to the SharePoint admin center. In the left menu, find Settings, and look for Document processing or Content AI services. In current builds of the admin center (April 2026), this appears under the Premium features section. Click it.
What you're looking for is a green "Active" status next to each service you're trying to use, autofill columns, document translation, eSignature, optical character recognition, and so on. If any service shows as "Not configured" or "Billing required," that's your answer. Click the service name, then click Set up pay-as-you-go billing. You'll be redirected to the Azure portal to select your subscription.
If you see the services listed but they're stuck on "Setting up..." with a spinner, wait 24–48 hours. Initial provisioning for newly activated document processing services is asynchronous on Microsoft's side, and there's genuinely nothing to do but wait for the back-end to propagate. I've seen impatient admins re-configure the billing three times in a row, creating duplicate Azure meter registrations that are annoying to clean up later. Set it once, wait it out.
If your services show "Active" but document processing still isn't working for end users, skip to Step 3 in the full walkthrough below, you likely have a site-level permissions issue, not a billing issue.
This is the most common root cause of Microsoft 365 document processing failures worldwide. Every document processing service, autofill columns, document translation, eSignature, OCR, content assembly, image tagging, taxonomy tagging, prebuilt models, structured models, freeform models, and unstructured models, runs through pay-as-you-go billing on an Azure subscription. If that link is broken, nothing works.
Go to your SharePoint admin center, then navigate to Settings > Document processing. Look for the Azure subscription field. It should show a specific subscription name and subscription ID. If it says "No subscription linked" or shows a subscription with a yellow warning triangle, that's your problem.
To fix it, click Set up pay-as-you-go. You'll be taken to the Azure portal. Make sure you're logged in with an account that has Owner or Contributor access to the Azure subscription you want to use. Select the correct subscription, choose a resource group (create a new one called something like RG-SharePoint-DocProcessing if you don't have one), then select your Azure region. Click Save.
After saving, return to the SharePoint admin center. The billing status may take 10–30 minutes to reflect as active. You'll know it worked when the subscription ID appears in green with an "Active" status next to it. If you get an error during the Azure portal step, particularly anything mentioning "insufficient permissions", you'll need your Azure subscription Owner to complete this step, not just an M365 Global Admin. Those are separate permission systems.
If your organization was running Microsoft Syntex or document processing on per-user licenses, you need to understand where things stand right now. Per-user licenses for these services are no longer available for purchase. What that means in practice: when your existing per-user licenses expire, you're expected to transition to pay-as-you-go. Microsoft doesn't send a dramatic warning when this happens, the services simply stop working at expiration.
Check your license status in the Microsoft 365 admin center under Billing > Licenses. Search for "Syntex" or "document processing." If you see licenses with an expiration date that has passed, or a count showing 0 active licenses, that's why your services are down.
Separately, and this catches a lot of organizations off guard: in October 2025, Microsoft announced a progressive end to AI Builder credits. Many document processing features, particularly structured and freeform models, consumed AI Builder credits under the hood. If your organization was relying on those credits (check under Power Platform admin center > Capacity > Add-ons for your AI Builder credit balance), that capacity is being wound down. The replacement path is pay-as-you-go Azure billing, not a new credit purchase.
Here's what you can still do on an active per-user license before it expires: 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, and use document library rules for automation. Once expired, all of those require pay-as-you-go to continue.
After confirming the license situation, set up pay-as-you-go billing as described in Step 1. This is the only forward path.
Billing can be perfectly configured at the tenant level, yet document processing features still won't appear for users in a specific SharePoint site. That's because features like autofill columns, image tagging, and taxonomy tagging need to be enabled at the document library level, not just the tenant level.
Navigate to the SharePoint document library where you want document processing to work. Click the gear icon in the top-right, then select Library settings. In newer SharePoint Online builds, this is under Settings > Library settings > More library settings. Scroll down to the Document processing section.
If the section is missing entirely, that means the site collection doesn't have content AI features enabled. Go to the SharePoint admin center, select the site under Active sites, click the site name to open its properties panel, then under the Hub tab look for the AI features toggle. Turn it on and wait a few minutes for the settings to propagate back to the site.
For autofill columns specifically: once you're back in the library, you need to go to Automate > Autofill a column in the library command bar. The first time you access this, it will prompt you to confirm your pay-as-you-go billing is active. Walk through that confirmation wizard even if you've already set up billing at the admin level, it registers the library for billing in the Azure meter system.
You should see a confirmation banner saying "Autofill columns is ready to use in this library." That's your signal it worked.
Document translation and eSignature are two of the most-used Microsoft 365 document processing services, and they each have their own failure modes that are worth calling out specifically.
For document translation: if you click Automate > Translate a document in a SharePoint library and see "This feature isn't available" or a blank dialog box, the most common cause is that the document translation service isn't activated in your tenant's pay-as-you-go billing configuration. Go back to the SharePoint admin center and verify that Document Translation specifically is listed under active services, activating the billing umbrella doesn't always auto-enable every sub-service. Find Document Translation in the list and toggle it on.
Document translation works by creating a new translated copy in the same document library, preserving the original format. Supported languages include all currently available Azure Cognitive Services Translator languages. If translation completes but the output document is corrupted or the layout is broken, that's typically a complex document formatting issue, heavily formatted PDFs with tables, images, and custom fonts don't always survive translation cleanly. Try a simpler test document to confirm the service itself is working before debugging formatting.
For eSignature: the most common issue is that the eSignature feature requires your document to remain in Microsoft 365 storage while it's being reviewed and signed. If you try to use eSignature on a document stored somewhere outside SharePoint (OneDrive consumer, a local drive, a Teams chat attachment that hasn't been synced back), the feature will either refuse to launch or will fail mid-request. Make sure the document is properly stored in a SharePoint document library before initiating the eSignature workflow.
Also verify that eSignature is explicitly enabled in your SharePoint admin center. It's a separate toggle from other document processing services and can be accidentally left off.
If your AI document models, prebuilt, structured, freeform, or unstructured, were working previously and suddenly stopped, or if newly created models refuse to process documents, here's what to check.
First, go to Content center in SharePoint (if your tenant was set up with a content center site, typically at a URL like https://yourtenant.sharepoint.com/sites/ContentCenter). Navigate to Models and check the status column on your models. A model showing "Training" that has been stuck for more than 48 hours indicates a back-end provisioning issue on Microsoft's side, raise a support ticket. A model showing "Ready" but not processing new documents usually means the library association broke.
To re-associate a model with a library: open the model, click Apply model, select the document library from the dropdown, and click Add. If the library doesn't appear in the dropdown, the site may have lost its connection to the content center. Re-check the site's hub association in the SharePoint admin center.
For unstructured models specifically: these classify documents that vary in composition, think mixed document types arriving in a single intake library. If an unstructured model is misclassifying documents, check the training set. Unstructured models require a minimum of five example documents per content type. If the training sample was sparse or unrepresentative, retrain with at least 10 examples per type and re-publish the model.
For optical character recognition (OCR): OCR is used to extract printed and handwritten text from images, making scanned documents searchable. If OCR results are missing from a library, confirm OCR is enabled at the document library level under Library settings > Optical character recognition. OCR processes documents asynchronously, new uploads can take 15–30 minutes to process depending on queue depth. Check the file's metadata column for an "OCR Status" field to see its processing state.
Advanced Troubleshooting for Microsoft 365 Document Processing
If the standard steps above haven't resolved your document processing issue, it's time to go deeper. These scenarios come up in enterprise environments, domain-joined configurations, and tenants with complex Azure setups.
Azure Subscription Region Mismatch
Microsoft 365 document processing uses Azure-based billing and processing infrastructure. If you set up your pay-as-you-go billing pointing to an Azure subscription in a region that doesn't match your SharePoint tenant's region, you may see intermittent processing failures or services that activate but never process documents. To check: in the Azure portal, navigate to your resource group and verify the region of the resources created by the SharePoint document processing setup. Compare that to your SharePoint tenant's geographic location (visible in the Microsoft 365 admin center under Settings > Org settings > Organization profile > Data location). If they diverge significantly, for example, your SharePoint tenant is in Europe but your Azure resources are in East US, consider re-creating the billing setup with an Azure subscription in the matching geography.
GCC Organizations, What You Can and Can't Do Right Now
If your organization is in the Government Community Cloud, pay-as-you-go licensing is not yet available for your environment. The pay-as-you-go services, and everything that requires them, are currently off-limits for GCC tenants. You can continue purchasing and using per-user licenses until pay-as-you-go becomes available for GCC. Don't try to work around this by linking a commercial Azure subscription to a GCC tenant. It won't work and can create messy billing states.
Power Platform Custom Environment Issues
If you're using structured or freeform models in a custom Power Platform environment (rather than the default environment), you need to complete additional setup steps. The document processing service needs to be registered in that specific Power Platform environment. Go to Power Platform admin center > Environments > [Your custom environment] > Settings > Features and verify that AI Builder and document processing integration is enabled there. For detailed steps, reference the official guidance on setting up a custom Power Platform environment for document processing.
Checking the Unified Audit Log for Processing Errors
In the Microsoft Purview compliance portal, go to Audit > New Search. Set the date range to the last 24–48 hours. Under "Activities," search for "SyntexModel" or "ContentCenter" to surface document processing activity events. Any failed processing operations will appear here with specific error codes that are far more useful than what end users see. Common error codes to look for: ModelApplicationFailed (model-to-library association broke), BillingNotConfigured (pay-as-you-go not active for that service), and OCRProcessingTimeout (document too large for OCR, typically files over 50MB).
Tenant-Level Feature Propagation Delays
When you make changes to document processing billing or service configurations, those changes propagate across Microsoft's global infrastructure asynchronously. For worldwide commercial tenants, propagation typically takes 2–4 hours. For some configurations, I've personally seen it take up to 24 hours before a newly activated service became operational in all site collections. If everything looks correct in the admin center but features still aren't appearing for users, this is the most likely explanation. Document the time you made the configuration change and check again the following day before doing anything more drastic.
If your pay-as-you-go billing shows as "Active" in the SharePoint admin center, your Azure subscription is healthy, your services are enabled at the tenant and site levels, and document processing is still not working after 48 hours, that is a Microsoft back-end issue and you should escalate. Gather these details before calling: your tenant ID (from Microsoft 365 admin center > Settings > Org settings > Organization profile), the specific service that isn't working, the SharePoint site URL, and the time you first noticed the failure. Contact Microsoft Support and open a case under SharePoint Online > Document Processing. Request a service health check against your tenant's provisioning state.
Prevention & Best Practices for Document Processing
Once you've got Microsoft 365 document processing working correctly, keeping it working requires some deliberate maintenance. These aren't theoretical best practices, they're the things I've watched organizations skip and later regret.
Monitor your Azure spending actively. Document processing charges flow through Azure service meters, and it's genuinely easy to run up unexpected costs if a high-volume library runs an expensive model type on thousands of documents without anyone noticing. Set up an Azure budget alert in the Azure portal under Cost Management + Billing > Budgets. Configure an alert at 80% and 100% of your expected monthly cap. This won't stop processing, but it will send you an email before you're blindsided.
Plan your license transitions proactively. Per-user licenses for document processing services are no longer being sold. If your organization still has active per-user licenses, they will eventually expire. When they do, if you haven't set up pay-as-you-go billing, all document processing functionality stops. Don't wait for the expiration notice. Set up billing now, verify it works, and treat the expiring per-user licenses as a deadline rather than a surprise.
Test models on sample libraries before production deployment. Every time you publish a new model, prebuilt, structured, freeform, or unstructured, test it against a sample library with 20–30 representative documents before applying it to a production library. Model accuracy on edge cases only reveals itself at volume, and reprocessing thousands of incorrectly classified documents after the fact is painful and costly.
Keep a content center site healthy. If your tenant uses a SharePoint content center to manage models, treat it like production infrastructure. Don't let its storage fill up, don't delete training example documents from its libraries, and document which team owns it. I've seen content center sites get cleaned up by well-meaning admins who had no idea those documents were training data for live models.
- Run the SharePoint Cost Calculator before enabling document processing on any high-volume library, know your estimated bill before you commit.
- Set Azure budget alerts at 80% of expected monthly spend so you're never surprised by the invoice.
- Document the exact Azure subscription and resource group used for document processing billing in your IT runbook, you'll thank yourself the next time there's a billing audit.
- Keep at least one Global Admin and one Azure Subscription Owner in your org who both understand how Microsoft 365 document processing billing works, it spans two different admin surfaces.
Frequently Asked Questions
Why is the document processing option completely missing from my SharePoint library?
The most common reason is that pay-as-you-go billing isn't set up at the tenant level, so Microsoft hides document processing UI elements entirely rather than showing them in a broken state. Go to your SharePoint admin center, navigate to Settings > Document processing, and check whether a pay-as-you-go Azure subscription is linked. If the billing section shows "Not configured," that's your fix, set up billing and the options will appear in your libraries within a few hours. If billing looks fine but the options are still missing, check whether the specific site has AI features enabled in its site properties in the SharePoint admin center.
My organization has a GCC Microsoft 365 tenant, why can't I set up pay-as-you-go for document processing?
Pay-as-you-go licensing for document processing is not yet available for Government Community Cloud organizations. This is a current platform limitation, not a configuration issue you can work around. GCC tenants can continue to purchase and use per-user licenses until Microsoft makes pay-as-you-go available in the GCC environment. Keep an eye on the Microsoft 365 roadmap at roadmap.microsoft.com for updates on GCC pay-as-you-go availability, and continue using per-user licenses in the meantime.
We were using AI Builder credits for our document processing workflows and they've stopped working. What happened?
In October 2025, Microsoft announced the progressive end of AI Builder credits. These credits powered many document processing features under the hood, and as that wind-down progresses, workflows that depended on them will stop functioning. The replacement path is pay-as-you-go billing through an Azure subscription, there's no way to purchase additional AI Builder credits as a long-term solution. You'll need to set up pay-as-you-go billing in the SharePoint admin center and link it to an active Azure subscription to restore document processing functionality.
I set up pay-as-you-go billing but my document processing services still say "Setting up" after 48 hours, what do I do?
If a service genuinely stays in "Setting up" status for more than 48 hours, that points to a back-end provisioning failure on Microsoft's side, not something you can fix by reconfiguring. Before escalating, check the Microsoft 365 service health dashboard in your admin center under Health > Service health to see if there's a known incident affecting SharePoint or document processing. If there's no active incident, open a support ticket with Microsoft and provide your tenant ID, the specific service name stuck in "Setting up," and the exact timestamp when you first configured billing. Microsoft's support team can check your tenant's provisioning queue directly.
Does every user in my organization need a special license to use document processing features?
No, that's one of the actual advantages of the pay-as-you-go model. Any user in your tenant can use document processing services as long as they have a standard Microsoft 365 license (like Microsoft 365 Business Standard or E3/E5). There's no per-seat add-on needed. Billing happens at the organizational level through Azure meters, based on consumption, how many documents are processed, how many translations are run, and so on. The SharePoint admin sets up the billing once, and then any licensed user in the tenant can access the features in document libraries where they're enabled.
My prebuilt document processing model was extracting data from invoices and now it's stopped. How do I fix it?
Start in the content center site for your tenant, typically at https://yourtenant.sharepoint.com/sites/ContentCenter, and open the model in question. Check its status: if it shows "Ready," the model itself is fine and the issue is likely a broken library association. Open the model, click "Apply model," and re-add the target document library. If the model shows an error state, check your pay-as-you-go billing status first, prebuilt model processing consumes Azure billing meters per document, and if billing is disrupted the model will stop processing. Also check the Unified Audit Log in the Microsoft Purview compliance portal for ModelApplicationFailed events that will tell you the specific failure reason.