Fix Microsoft 365 Document Processing Problems
Why This Is Happening
I've seen this exact scenario play out hundreds of times: a SharePoint admin spends a morning enabling document processing services in the Microsoft 365 admin center, goes back to a document library to test autofill columns or kick off an OCR extraction , and absolutely nothing happens. No error. No processing. Just silence. That particular flavor of frustration is uniquely Microsoft 365.
Microsoft 365 document processing is a collection of pay-as-you-go AI services that live at the intersection of SharePoint, Azure, and Power Platform. Because it touches three separate product surfaces, there are three separate places things can break. The service was previously marketed under the Microsoft Syntex brand , you'll still see "Syntex" in plenty of admin consoles, error messages, and community threads even though the official name is now "document processing for Microsoft 365." That rename alone causes confusion, because people search for one name and find docs written under the other.
The second big source of pain is the billing model. Microsoft 365 document processing runs entirely on pay-as-you-go licensing tied to an Azure subscription. If that Azure subscription isn't linked correctly, or if the person who set it up didn't have the right Azure permissions, every downstream service silently fails. You won't get a clear "billing not configured" error in SharePoint; you'll just get nothing. Meanwhile, the old per-user license model (AI Builder credits) reached end-of-sale and Microsoft announced the progressive end of AI Builder credits in October 2025. If your tenant still relied on those credits, some services may have stopped processing entirely.
There's also the Government Community Cloud (GCC) situation. If your organization is on GCC, pay-as-you-go licensing is not yet available. The services that require it, including document translation, eSignature, and the optical character recognition service, are simply not accessible. This is documented, but the error messages in the admin center don't always make it obvious that the block is a compliance boundary, not a configuration mistake you made.
Finally, the range of services is wide, autofill columns, document translation, eSignature, OCR, content assembly, image tagging, taxonomy tagging, prebuilt models, structured and freeform models, unstructured models, and each one has its own prerequisites, capacity requirements, and SharePoint library settings. A fix that works for autofill columns won't necessarily fix a broken unstructured model pipeline.
I know this is frustrating, especially when it blocks a workflow your team was counting on. Let's work through it methodically. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you go deep into troubleshooting, run through this checklist. About 60% of Microsoft 365 document processing problems I see in the wild come down to one of these four things, and you can verify all of them in under five minutes.
Step 1, Confirm pay-as-you-go billing is actually active. Go to the Microsoft 365 admin center (admin.microsoft.com), expand Setup in the left rail, then select Use content AI with Microsoft Syntex (yes, the old Syntex name is still in the UI as of early 2026). On that page, look for the Azure subscription field. If it reads "Not configured" or shows a subscription in a "Disabled" state, that's your culprit. No Azure billing link = no processing, full stop.
Step 2, Check that the specific service you're using is enabled. Still in the admin center, click Go to Microsoft Syntex settings (or navigate to Settings > Org settings > Microsoft Syntex). Each service, autofill columns, document translation, OCR, etc., has its own individual toggle. They are not all turned on by default when you activate billing. If the toggle for "Optical character recognition" is off, OCR will not run on any library, no matter how your library is configured.
Step 3, Verify the user has a Microsoft 365 license. Any user in your tenant can use document processing services under pay-as-you-go, but they still need an active Microsoft 365 license assigned to their account. Check under Users > Active users in the admin center and confirm the affected user has a license that includes SharePoint access.
Step 4, Check the SharePoint library settings, not just the admin center. Document processing services need to be configured at the library level, not just tenant level. Open the document library, click the gear icon, select Library settings, then look under Intelligent document processing. If you've never applied a model or enabled a service for this specific library, that explains the silence.
This is the foundation. Microsoft 365 document processing services won't run a single transaction without an active Azure subscription connected to your tenant. Unlike traditional Microsoft 365 licensing, these charges flow through Azure billing, so even if your Microsoft 365 billing looks perfectly healthy, the document processing layer needs its own Azure tie-in.
To set this up, sign in to admin.microsoft.com with a Global Administrator or SharePoint Administrator account. In the left navigation, go to Setup, then find and click Use content AI with Microsoft Syntex. On the landing page, click Set up pay-as-you-go billing.
You'll be asked to select an Azure subscription and a resource group. Make sure the person doing this step has at least Contributor role on the Azure subscription, Owner works too, but Contributor is the minimum. If you try to complete this step with a user who only has Reader access to Azure, the form will appear to save but the subscription will never actually link. This is a silent failure that trips up a lot of admins.
Once saved, go back to Settings > Org settings > Microsoft Syntex and verify the subscription shows as Active next to a green status indicator. If it shows as "Pending," wait up to 15 minutes and refresh, Azure provisioning can take a few minutes. If it stays stuck on Pending after 30 minutes, the Azure subscription may have a spending limit set to zero or a policy that blocks new resource creation.
# Confirm the Azure subscription has no spending limit via Azure CLI
az account show --subscription "YOUR-SUBSCRIPTION-ID" --query "[name, state]"
When it works: the status field turns green and the individual service toggles on the Microsoft Syntex settings page become clickable rather than grayed out.
Once billing is linked, you still need to explicitly turn on each service you want to use. A common misconception is that setting up pay-as-you-go "unlocks everything." It doesn't, it enables you to unlock each service individually, which Microsoft does intentionally so organizations can control which AI services are active and therefore which ones they're billed for.
Navigate to Settings > Org settings > Microsoft Syntex in the admin center. You'll see a list of services that maps closely to the full document processing catalog: autofill columns, document translation, eSignature, optical character recognition, content assembly, image tagging, taxonomy tagging, prebuilt document processing, structured and freeform document processing, and unstructured document processing.
Each service has its own toggle. Click the service name to expand it and you'll usually see additional configuration options, for example, the document translation service lets you restrict which supported languages are available, and the eSignature service lets you specify whether external signers are permitted.
For autofill columns specifically, after enabling the toggle you'll also need to configure which SharePoint sites are allowed to use it. There's a "Select sites" option, you can set it to all sites or restrict it to specific site collections. If you forget this step and leave it on "No sites," the service will be "enabled" in the admin sense but completely inoperative at the library level.
After enabling what you need, save your changes and wait approximately 10–15 minutes for propagation across SharePoint Online. Then open a test document library and check whether the new options appear under Automate > Configure document library in the library toolbar.
Tenant-level activation only gets you halfway there. For most document processing services, particularly prebuilt models, structured models, freeform models, and unstructured models, you need to go into each individual SharePoint document library and apply the specific model you want to use there.
Open the target document library. In the top toolbar, click Automate, then select Apply a document understanding model (or the equivalent entry for the specific service you're configuring, the label varies slightly by service). If this menu option doesn't appear, the service hasn't propagated from the admin center yet, or the library's site is not included in the allowed sites list from Step 2.
From the model picker, you can choose from existing models in your tenant's content center or create a new one. If you're using a prebuilt model, for invoices, receipts, contracts, or similar structured document types, select the appropriate prebuilt template and it will be ready to apply immediately without training. These are the fastest way to get processing running because Microsoft has already trained the underlying model.
For structured and freeform models or unstructured models, you'll need to go to the SharePoint content center (the dedicated site created during Syntex setup, usually named something like "Content Center" at a URL like https://yourtenant.sharepoint.com/sites/contentcenter), build the model, train it with example documents, and then publish it before it appears in the library's model picker.
Once applied, upload a test document and watch the columns you mapped to extracted fields. If the fields populate within 2–5 minutes, processing is working. If nothing happens after 10 minutes, check the service health dashboard in the admin center for any SharePoint or AI service incidents.
If your organization had Microsoft Syntex per-user licenses or was using AI Builder credits before October 2025, you may be hitting a wall right now because of the announced end of AI Builder credits. Microsoft progressively wound down these credits starting October 2025, meaning any tenant that was running document processing workflows on the old credit system needs to actively migrate to pay-as-you-go to keep things running.
The symptoms are specific: models that used to work stop processing new documents, autofill columns stop populating, and the activity logs in the content center show no new processing events even though everything looks "configured." There's no big red warning saying "your credits are gone", the pipeline just quietly stops.
To check your current licensing state, go to admin.microsoft.com > Billing > Licenses and look for any Syntex or AI Builder licenses. If they show as expired or near expiry, that's your answer. Per-user licenses for these services are no longer available for purchase as of the current date, but existing licenses can still be assigned to users while active, they just can't be renewed once they expire.
The migration path is to complete the pay-as-you-go setup from Step 1. Once pay-as-you-go billing is active, users who previously held per-user licenses will automatically continue to have access, and users without licenses will also gain access (since any Microsoft 365 user in the tenant can use pay-as-you-go services). There's no manual migration of individual models required, the models themselves remain intact; it's purely a billing switch.
If you still have active per-user licenses, you can continue to apply unstructured models to libraries, create prebuilt, structured, and freeform models, run models on demand, and use content assembly and content query features until those licenses expire. Think of this transition window as your runway to get pay-as-you-go configured before the old system fully retires.
Three of the document processing services, document translation, optical character recognition, and eSignature, have service-specific failure modes worth knowing about separately from the general billing and setup issues.
Document translation not working: Document translation creates a translated copy of a file in the same SharePoint document library, preserving the original file's format and structure. The most common failure mode is that the translated file never appears. First, confirm the source document is in a supported file type, Word, PowerPoint, and PDF are supported; not all file extensions are. Second, check that the target language is one of the enabled languages in the admin center configuration you set during Step 2. Third, translation requires the document library to have versioning enabled, if versioning is off, the service can't create the translated copy safely. Go to Library settings > Versioning settings and confirm "Create a version each time you edit a file" is checked.
OCR not extracting text: Optical character recognition extracts printed or handwritten text from images so you can search, filter, and query that content in SharePoint. If OCR isn't running, the first thing to check is file size, very large image files or multi-hundred-page scanned PDFs may time out. Try a smaller test file first. Also confirm the OCR service toggle is enabled in admin settings, as it has a separate toggle from the model-based services.
eSignature requests failing: eSignature lets you send signing requests while keeping documents inside Microsoft 365 rather than exporting them to a third-party platform. If requests aren't sending, check that external sharing is enabled on the SharePoint site, eSignature needs to be able to generate a link accessible to the signer, which requires the site to allow sharing with people outside the organization if your signers are external. Navigate to SharePoint admin center > Sites > Active sites, find the site, and confirm the sharing setting is set to at least "New and existing guests."
# Check site external sharing level via PowerShell (SharePoint PnP module)
Get-PnPTenantSite -Url "https://yourtenant.sharepoint.com/sites/yoursite" | Select SharingCapability
When eSignature is working correctly, senders see a signing status column populate in the document library and signers receive an email with a secure link to the document.
Advanced Troubleshooting
If the step-by-step fixes above didn't resolve your problem, you're likely dealing with a tenant-level policy conflict, a Power Platform environment misconfiguration, or a service health incident. Here's how to dig deeper.
Check the Microsoft 365 Service Health Dashboard. Before spending hours investigating your own configuration, rule out a Microsoft-side incident. Go to admin.microsoft.com > Health > Service health. Look for incidents tagged under "SharePoint Online," "Microsoft 365 Apps," or "Power Platform." Document processing services run on a combination of these workloads, and a degraded SharePoint incident will knock out model processing even when your configuration is perfect.
Review SharePoint ULS logs or Unified Audit Log entries. If you have access to the Microsoft 365 compliance portal, go to compliance.microsoft.com > Audit and search for activities under the "SharePoint" workload filtered to the user and site in question. Look for events like SyntexModelApplied, SyntexModelProcessingFailed, or ContentProcessingError. These audit events give you the actual failure reason that the SharePoint UI never shows you.
Custom Power Platform environments for structured/freeform models. Structured and freeform document processing models use an underlying Power Platform AI Builder engine. By default, they run in your tenant's default Power Platform environment. But if your organization uses a custom Power Platform environment, common in enterprise scenarios where default environment access is locked down, you need to explicitly configure document processing to use that custom environment. Go to Microsoft Syntex admin settings, find the "Power Platform environment" section, and confirm the correct environment is selected. A mismatch here means models train and publish successfully but fail to process documents silently, because the processing engine is looking at a different Power Platform environment than where the model actually lives.
Network and firewall considerations for enterprise environments. If your organization routes SharePoint traffic through a proxy or has strict egress firewall rules, document processing service calls to Azure AI endpoints may be blocked. The processing doesn't happen locally, it calls out to Microsoft's AI infrastructure. Make sure your network allows outbound HTTPS traffic to *.microsoft.com, *.azure.com, and *.office.com without SSL inspection stripping the certificate chain, which can cause silent failures on the AI service calls.
Azure subscription policy blocks. Some organizations enforce Azure Policy rules that restrict which resource types can be deployed or which regions resources can be created in. Document processing services deploy resources in specific Azure regions. If your subscription has a policy requiring all resources to be in, say, West Europe, but the document processing service tries to deploy in East US, the provisioning fails silently from SharePoint's perspective. Check portal.azure.com > Policy > Compliance for your subscription and look for any non-compliant resource deployments tagged with "Syntex" or "Microsoft.SharePoint."
Prevention & Best Practices
Getting Microsoft 365 document processing working once is good. Keeping it working, and not getting surprised by unexpected charges or broken pipelines, requires a bit of ongoing housekeeping. Here's what I recommend based on real enterprise deployments.
Set Azure cost alerts before you scale up processing. Because document processing is pay-as-you-go, a misconfigured model applied to a high-volume library can generate significant Azure charges in a short time. Before you apply any model to a production library, go to portal.azure.com > Cost Management > Budgets and set a monthly budget alert for the subscription you linked to Microsoft 365 document processing. A threshold alert at 80% of your expected spend will catch runaway processing before it becomes a billing incident.
Use the SharePoint cost calculator for planning. Microsoft provides a SharePoint cost calculator in the admin center's pay-as-you-go billing section. Enter your estimated monthly document volumes by service type and it gives you a projected monthly cost. Run this before deploying document translation or OCR at scale, those two services in particular can add up quickly on large document libraries with frequent uploads.
Document which models are applied to which libraries. There's no native "inventory of applied models" view across your whole tenant in one place. Build a simple SharePoint list or Excel workbook that tracks: site URL, library name, model name, model type, date applied, and the person responsible. When something breaks or a new admin needs to troubleshoot, this record saves enormous amounts of time.
Monitor the AI Builder credits deprecation timeline. If your tenant still has active per-user licenses, track their expiration dates in admin.microsoft.com > Billing > Your products. Plan your migration to pay-as-you-go at least 30 days before those licenses expire, don't wait for expiry day to start the billing setup, because Azure subscription linking can take time and you don't want a gap in service.
- Set an Azure cost budget alert at 80% of expected monthly spend before enabling processing on production libraries
- Test every new model on a library with 5–10 sample documents before applying it to a full-scale library
- Keep a record of which SharePoint libraries have models applied and what type, a simple SharePoint list works fine
- Review the Microsoft 365 service health dashboard before troubleshooting any processing outage, at least 20% of "my model stopped working" cases turn out to be Microsoft-side incidents
Frequently Asked Questions
Why did my document processing models suddenly stop working after October 2025?
Microsoft announced a progressive end of AI Builder credits starting October 2025, this is the most likely cause. If your tenant was using AI Builder credits to power document processing (under the old Microsoft Syntex licensing model), those credits have been wound down. The fix is to set up pay-as-you-go billing in the Microsoft 365 admin center by linking an active Azure subscription. Once billing is active, your existing models continue to work and process documents as before, only the billing mechanism changes. Per-user Syntex licenses, if still active, continue to work until they expire but cannot be renewed.
Does Microsoft 365 document processing work for Government Community Cloud (GCC) tenants?
Not yet, as of early 2026. Microsoft has confirmed that pay-as-you-go licensing, and the document processing services that depend on it, are not available for GCC organizations. GCC tenants can continue purchasing and using per-user licenses in the interim. Microsoft has stated pay-as-you-go will become available for GCC in the future, but no specific date has been announced. If you're on GCC and running into errors trying to set up pay-as-you-go, this is the reason, it's a compliance boundary, not a configuration problem you can fix on your end.
How much does Microsoft 365 document processing cost? I'm worried about surprise charges.
Costs vary by service and volume, there's no single flat rate. Microsoft uses a pay-per-transaction model billed through your Azure subscription. For example, document translation, OCR, and AI model processing each have separate per-page or per-document meters. The best way to estimate your costs before committing is to use the SharePoint cost calculator, which is available from the pay-as-you-go billing setup page in the Microsoft 365 admin center. I strongly recommend setting up Azure budget alerts before enabling high-volume processing, a library with 100,000 documents and an autofill column configured to run on every upload can generate real charges very quickly.
What's the difference between prebuilt models, structured models, and unstructured models?
Prebuilt models are ready-made, pre-trained models for common document types like invoices, receipts, contracts, and business cards, you apply them directly to a library without any training effort. Structured and freeform models are for documents where the information you want appears in consistent or predictable locations (like a tax form or a standardized contract template), you train these by highlighting examples of the fields you want to extract. Unstructured models go further: they handle documents that vary widely in format and layout, classifying them into categories and extracting information even when the document structure is unpredictable. Prebuilt models are the fastest to deploy; unstructured models take the most training investment but handle the most complex real-world document variety.
Can any user in my organization use document processing, or do I need to assign licenses to each person?
Under pay-as-you-go, any user in your tenant can use document processing services as long as they have an active Microsoft 365 license, you don't need to assign a separate Syntex or document processing license to individuals. The pay-as-you-go model bills at the tenant level through Azure, not per user. The key requirement is that the user has a Microsoft 365 license that includes SharePoint access. If a user has no Microsoft 365 license at all, they won't be able to interact with SharePoint and therefore won't be able to trigger document processing workflows.
The "Apply a document understanding model" option doesn't show up in my SharePoint library, how do I fix it?
There are three common reasons this option is missing. First, the specific service may not be enabled in the Microsoft 365 admin center, go to Settings > Org settings > Microsoft Syntex and check that the relevant service toggle is on. Second, even if the service is enabled, you may need to explicitly add the current site to the "allowed sites" list in the service configuration, services like autofill columns have a site-selection setting that defaults to restricted. Third, there can be a propagation delay of up to 30 minutes after you make admin center changes before they appear in SharePoint libraries. If you've verified the first two and the option still isn't there after 30 minutes, try accessing the library from an InPrivate/Incognito browser window to rule out a cached permissions issue.