Fix Microsoft 365 Document Processing Issues
Why This Is Happening
Picture this: your team just rolled out Microsoft 365 document processing across your SharePoint libraries. Someone tries to run an autofill column model on a batch of contracts , nothing happens. No error, no progress bar, just silence. Or worse, they get a vague "service unavailable" message with zero guidance on what went wrong. I've seen this exact scenario on dozens of tenant deployments, and nine times out of ten it comes down to one of three things: billing isn't wired up correctly, the wrong license state is assumed, or a service configuration step got skipped during setup.
Microsoft 365 document processing , the suite formerly known as Microsoft Syntex pay-as-you-go services, is a genuinely powerful set of AI-driven content tools. We're talking autofill columns, document translation, eSignature, optical character recognition (OCR), content assembly, image tagging, taxonomy tagging, and multiple model types (prebuilt, structured, freeform, and unstructured). But all of these services share a common dependency: they are strictly pay-as-you-go, billed through an Azure subscription. If that subscription link breaks, or if it was never set up properly in the first place, every single one of these services goes dark with virtually no helpful error messaging to explain why.
The naming change itself has caused confusion. Microsoft officially retired the "Syntex" pay-as-you-go branding in favor of "document processing for Microsoft 365", but plenty of admin documentation, SharePoint admin center labels, and third-party guides still use the old Syntex terminology. If you're searching help docs using the old name and landing on outdated instructions, you're going to waste a lot of time chasing solutions that no longer apply.
There's also the AI Builder credits transition to be aware of. Microsoft announced in October 2025 that AI Builder credits are being progressively phased out. If your document processing workflows previously consumed AI Builder credits, they may now be failing silently because that credit pool has been reduced or eliminated. The replacement path is pay-as-you-go billing through Azure, and unless someone in your organization made that migration deliberately, it probably didn't happen automatically.
Government Community Cloud (GCC) tenants face a separate, frustrating constraint: pay-as-you-go licensing is not yet available for GCC. That means if you're on a GCC tenant, the per-user license path is still your only option, and many of the fixes below won't apply to you until Microsoft extends pay-as-you-go availability to GCC. Worth knowing before you spend an afternoon troubleshooting billing settings that can't work in your environment yet.
The bottom line is that Microsoft 365 document processing issues almost always trace back to billing, licensing state, or setup, not to the AI models themselves being broken. Understanding which of those three categories your problem falls into is the key to fixing it fast. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you dig into individual service settings, the single most common root cause of Microsoft 365 document processing not working is a missing or broken pay-as-you-go billing connection. Here's how to check and fix it in under five minutes.
Open the SharePoint admin center by navigating to https://<your-tenant>-admin.sharepoint.com. In the left navigation, look for Settings, then scroll down to find Document processing (you might still see it labeled as "Microsoft Syntex" depending on when your admin center was last updated). Click it.
On the Document processing settings page, look at the top section, it should show your connected Azure subscription. If it says "Not configured," "No subscription connected," or if the billing status shows as inactive, that's your problem right there. Every single document processing service, autofill columns, document translation, OCR, eSignature, all of them, requires this Azure billing connection to function. None of them will work without it, and Microsoft's error messages rarely tell you that clearly.
To fix it, click Set up pay-as-you-go billing. You'll need to sign in with an account that has both SharePoint admin rights and Azure subscription owner or contributor permissions. Select your Azure subscription from the dropdown, choose a resource group (create a new one called something like rg-m365-docprocessing if you don't have one), select your Azure region, and click Save. The connection usually activates within a few minutes.
Once billing is connected, go back to your SharePoint library, click the library Settings gear, choose Library settings, and look for the Document processing section. If the services you need are now listed and available, you're done. If specific services are still greyed out or missing, move on to the step-by-step section below for per-service troubleshooting.
Even if pay-as-you-go billing was set up previously, Azure subscriptions can expire, get disabled, or hit spending limits, all of which silently break document processing services. Start here before anything else.
Go to the Azure portal at portal.azure.com and sign in with your admin account. In the top search bar, type Subscriptions and select it. Find the subscription you linked to document processing and check the Status column. It must show Active. If it shows Disabled, Expired, or Past Due, that's your root cause.
For a disabled subscription, click on the subscription name, then click Reactivate in the top toolbar. You may need to update your payment method first under Billing → Payment methods. For a subscription that hit a spending limit, go to Billing → Budgets and either raise the limit or remove it temporarily while you sort out capacity planning.
Once the subscription is active again, return to the SharePoint admin center under Settings → Document processing and verify the billing status updates to show your active subscription. It can take up to 15 minutes for the status to refresh, you can speed this up by disconnecting and re-connecting the subscription using the settings page.
If the subscription looks fine but document processing is still broken, check that the account that originally set up billing still has the appropriate Azure role. You need at minimum Contributor access on the subscription or resource group. If that user left the organization and their account was deprovisioned, the billing link may have silently broken. Reassign the role to an active admin account and re-save the billing settings.
What success looks like: The Document processing settings page in SharePoint admin center shows your subscription name, resource group, and a green "Active" or "Connected" billing status.
Connecting Azure billing doesn't automatically turn on every service. Each individual Microsoft 365 document processing capability, autofill columns, document translation, eSignature, OCR, content assembly, image tagging, taxonomy tagging, and the various model types, needs to be individually enabled by a SharePoint admin. This trips people up constantly.
Back in the SharePoint admin center, go to Settings → Document processing. You'll see a list of all available services, each with its own toggle. Scroll through the full list and enable the services your organization needs. Key services and what to know about each:
- Autofill columns, uses large language models to extract or generate metadata from document content and populate SharePoint list columns automatically. Enable this if users are complaining that columns aren't populating.
- Document translation, creates a translated copy of a document in a SharePoint library while preserving the original file's format and structure. Users need to trigger this from within the document library.
- eSignature, sends documents for electronic signature without the content leaving Microsoft 365. If users report the eSignature option is missing from document menus, this toggle is likely off.
- Optical character recognition (OCR), extracts text from image-based files so that content becomes searchable in SharePoint. Very useful for scanned PDFs and image uploads.
After enabling services, save your changes. The changes propagate to all SharePoint sites in your tenant, but it can take up to 30 minutes for them to appear in document library menus for end users. Have your users do a hard refresh (Ctrl+Shift+R) in their browser if the options don't appear quickly.
What success looks like: Users can see the enabled service options in their document library menus and command bars.
So billing is set up, services are enabled, but your document processing models still aren't running on library content. This is frustrating, and it usually comes down to how the model is applied to the library, not the model itself.
Navigate to the document library where processing should be happening. Click the Settings gear in the top-right corner of the library, then select Library settings. Scroll down until you see the Document processing section. If it's not there, the service may not have propagated yet, wait the full 30 minutes and try again.
If you see the Document processing section but your model isn't listed under Applied models, the model hasn't been applied to this library yet. You can apply it directly from here by clicking Apply a model, or you can navigate to the content center site where your models are managed and apply the model from there. The content center approach gives you more control over which libraries a model runs against.
If a model is listed but showing a Processing paused or Error status, click on the model name. Look for a Run now option to trigger an on-demand processing run, this can unstick models that got into a failed state. If the model was previously working under a per-user license and you've transitioned to pay-as-you-go, you may need to remove and re-apply the model to force it to run under the new billing context.
For prebuilt models (invoices, receipts, contracts), structured models, and freeform models, ensure the model was created and trained in a content center site that has the appropriate pay-as-you-go services enabled. Models created under old per-user licensing can still be used and run on demand, per the official documentation, existing per-user license holders can continue to create and run models until their licenses expire.
What success looks like: The model shows as Applied in library settings with a status of Active, and newly uploaded documents trigger processing automatically.
Two of the most-reported Microsoft 365 document processing issues are eSignature being missing from document menus, and the document translation option not showing up when right-clicking files. Both have specific prerequisites beyond just enabling the service toggle in admin settings.
For eSignature: The option to send a document for electronic signature appears in the document library command bar and in the file context menu, but only when a user selects a supported file type (primarily PDF and Word documents). If users are trying to eSign an unsupported file type, the option won't appear at all. Also confirm that the user has at minimum Contribute permissions on the library. Read-only users cannot initiate eSignature requests. Additionally, check that the eSignature service toggle is enabled in the SharePoint admin center for the specific site, some organizations enable services globally but then override them at the site level, accidentally leaving eSignature off.
For Document Translation: First, the file must be in a supported format, Word documents (.docx), PDFs, and several other common formats are supported, but not every file type. Second, the translation happens within SharePoint itself, creating a new translated copy in the same library, the original file is never modified. If users expect an in-place translation and don't see a new file appearing, they may be looking in the wrong place. The translated copy appears in the same library folder with the target language appended to the filename.
Both services require that the user accessing them has a valid Microsoft 365 license assigned. Any user in the tenant can use pay-as-you-go services, but they must have a base Microsoft 365 license. Unlicensed guest accounts or external sharing users cannot trigger document processing services.
# Check user's M365 license via PowerShell (Exchange Online / M365 module)
Get-MgUserLicenseDetail -UserId "user@yourdomain.com" | Select-Object SkuPartNumberWhat success looks like: A licensed user right-clicks a supported Word or PDF file in SharePoint and sees both "Translate" and "Request signatures" as available options in the context menu.
Autofill columns and optical character recognition (OCR) are the two document processing services I see people struggle with most after billing is sorted out, because even when they're working technically, they can produce unexpected results if the underlying configuration isn't right.
For Autofill Columns: These use large language models to extract or generate content for SharePoint list columns based on document content. If a column isn't populating after a file is uploaded, first check that the column is actually configured for autofill. Go to Library settings → Columns, click the column name, and look for the Autofill settings section. If it's not there, the column hasn't been configured for autofill yet. You'll need to set up the autofill instruction, the prompt that tells the LLM what information to extract, from the column settings page.
Autofill only runs on files uploaded after the column is configured unless you manually trigger processing on existing files. To run autofill on existing documents, select the files in the library, click the Automate menu in the command bar, and choose Run document processing. This triggers an on-demand processing run against your selected files.
For OCR: OCR works on image-based files and scanned PDFs to make their content searchable in SharePoint. The most common issue is that OCR has been enabled as a service but hasn't been configured to run on a specific library. Go to Library settings → Document processing and check whether OCR is listed and active for that library. If not, you'll need to apply OCR to the library the same way you'd apply a model.
Bear in mind that OCR processing isn't instantaneous. After enabling it on a library, expect existing files to be processed in a queue, large libraries with thousands of files can take hours or even days to fully process. New uploads are prioritized and typically processed within a few minutes.
# SharePoint PnP PowerShell: check document processing status on a library
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/yoursite" -Interactive
Get-PnPList -Identity "Documents" | Select-Object Title, EnableSyntexWhat success looks like: Newly uploaded image PDFs become searchable in SharePoint full-text search within 5–10 minutes, and autofill columns populate within a minute or two of upload.
Advanced Troubleshooting
When the standard fixes don't resolve the problem, or when you're dealing with an enterprise environment with Group Policy, custom Power Platform environments, or complex Azure subscription topologies, you need to dig deeper.
Custom Power Platform Environments for Structured/Freeform Models
If your organization uses structured or freeform document processing models inside a custom Power Platform environment (rather than the default environment), there's an extra configuration step that catches a lot of enterprise admins off guard. You need to explicitly configure the custom Power Platform environment to work with document processing. The official documentation calls this out specifically, models in a custom Power Platform environment will not process documents using the standard setup path. You have to go through the dedicated setup flow in both the Power Platform admin center and the SharePoint admin center, linking the custom environment to your pay-as-you-go billing configuration.
AI Builder Credits Phase-Out Impact
If your document processing workflows were built before October 2025 and previously relied on AI Builder credits, those workflows may now be failing without obvious error messages. Microsoft began a progressive end of AI Builder credits starting October 2025. Check your Power Platform admin center for any flows or models showing "Insufficient credits" or "Credits expired" errors. The fix is to migrate these workflows to the pay-as-you-go billing model. In practice, that means unlinking any AI Builder credit-based connectors and reconfiguring those steps to run through the SharePoint document processing interface instead.
Tenant-Level SharePoint Feature Flags
Some document processing features are controlled by SharePoint tenant-level feature flags that can be accidentally disabled during tenant migrations, SharePoint Framework (SPFx) updates, or admin center reconfigurations. If a specific service like content assembly or taxonomy tagging isn't appearing even though it's enabled in admin settings, check these flags via PowerShell:
# Connect to SharePoint Online Management Shell
Connect-SPOService -Url "https://yourtenant-admin.sharepoint.com"
# Check tenant-level settings related to document processing
Get-SPOTenant | Select-Object SyntexEnabled, EnableSyntexFeatures, AllowEditingEvent Viewer and ULS Log Analysis
For on-premises SharePoint hybrid setups or when you need to trace exactly where a processing request is failing, SharePoint's Unified Logging Service (ULS) logs are your best diagnostic tool. In the SharePoint admin center, navigate to Reports → Usage for high-level processing telemetry, or use the Microsoft Purview compliance portal audit logs to trace document processing activity at the individual file level. Filter audit logs by the activity type "Applied document processing model" to see a history of every processing event across your tenant.
Network Proxy and Firewall Rules
In tightly controlled enterprise networks, document processing services communicate with Azure-hosted AI endpoints. If your organization uses a proxy or firewall, ensure that outbound HTTPS traffic to *.microsoft.com, *.microsoftonline.com, and *.sharepoint.com is allowed. Document translation in particular calls Azure AI Translator endpoints that may be on a separate IP range from standard Microsoft 365 traffic. Check with your network team and cross-reference with Microsoft's published Office 365 IP and URL endpoints.
Prevention & Best Practices
Once you've got Microsoft 365 document processing working, keeping it working requires a bit of proactive management, especially since the pay-as-you-go billing model means unexpected usage can generate unexpected costs, and any disruption to the Azure subscription immediately affects all document processing services.
Set up Azure cost alerts on the resource group you created for document processing. In the Azure portal, navigate to your resource group, click Budgets, and create a budget with email alerts at 80% and 100% of your expected monthly spend. This gives you early warning before you hit a spending limit that would disable the services. I'd also recommend reviewing your Azure subscription's Cost analysis monthly, the SharePoint cost calculator referenced in Microsoft's documentation is a useful tool for modeling expected usage before you scale up to additional libraries or services.
Document which account owns the Azure billing connection to SharePoint. This is critically important for IT succession planning. When the account that set up pay-as-you-go billing leaves the organization and gets deprovisioned, you can end up in a situation where the billing link is broken and nobody knows how to fix it. Create a runbook entry in your IT documentation that identifies the Azure subscription, resource group, and admin account used for document processing setup.
For organizations still on per-user licenses, start planning your migration to pay-as-you-go now. Per-user licenses are no longer available for purchase, and once existing licenses expire, pay-as-you-go is the only path forward. The transition isn't automatic, you need to actively set up billing. Waiting until licenses expire means a service outage while you scramble to set up Azure billing under pressure.
Monitor for the GCC pay-as-you-go availability announcement if you're on a Government Community Cloud tenant. Microsoft has not announced a specific timeline, but when pay-as-you-go becomes available for GCC, plan to migrate promptly, per-user license support will likely wind down for GCC tenants as well once the alternative is available.
- Set Azure cost alerts at 80% and 100% of your monthly document processing budget to avoid surprise spending limit shutdowns
- Document the Azure subscription ID and resource group used for document processing billing in your IT runbook, losing this info after a staff change is a very common support scenario
- Run a quarterly audit of which document processing services are enabled and which libraries have models applied, unused services that are left enabled still count toward your pay-as-you-go metering when triggered
- Test a complete document processing workflow end-to-end after any major Microsoft 365 tenant update or Azure subscription change, these are the two most common trigger events for silent processing failures
Frequently Asked Questions
Why did document processing stop working after we renewed our Microsoft 365 licenses?
License renewals themselves don't directly affect document processing, but if your organization had per-user Syntex licenses that weren't renewed, those services now require pay-as-you-go billing to continue functioning. Per-user licenses for document processing services are no longer available for new purchases. Once existing per-user licenses expire, you must set up Azure pay-as-you-go billing in the SharePoint admin center under Settings → Document processing. The good news is that any models you created under the old per-user licenses can still be used, you won't lose your trained models, you just need the billing connection active to run them.
Can guest users or external collaborators use document processing features?
No, external guest users and unlicensed accounts cannot trigger Microsoft 365 document processing services. The official documentation is clear that any user who uses these services must have a valid Microsoft 365 license in your tenant. This includes initiating document translation, sending eSignature requests, or triggering autofill columns manually. However, the processing that runs automatically in the background, like OCR indexing newly uploaded files, runs as a service-level operation and doesn't require the uploading user to have specific document processing permissions.
We're a GCC tenant, why can't we access pay-as-you-go document processing?
Government Community Cloud (GCC) tenants are currently excluded from pay-as-you-go licensing for document processing services. Microsoft has confirmed this limitation in their official documentation and notes that GCC organizations can continue using per-user licenses until pay-as-you-go becomes available for the government cloud. There's no announced timeline for GCC availability as of April 2026. Your best path right now is to continue using per-user licenses and watch the Microsoft 365 roadmap at the Microsoft Tech Community blog for GCC pay-as-you-go announcements.
What happened to AI Builder credits? Our document processing flows just broke.
Microsoft announced in October 2025 that AI Builder credits are being progressively ended. If your Power Automate flows or Power Apps were consuming AI Builder credits to drive document processing functionality, those flows are likely failing now due to zero or insufficient credit balance. The fix is to migrate those flows to use the Microsoft 365 document processing services directly through SharePoint, billing through your Azure pay-as-you-go subscription. This is a breaking change for anyone who built document processing automation on top of AI Builder credits before October 2025, it requires deliberate reconfiguration, not just a settings toggle.
How long does it take for document translation to complete in SharePoint?
Document translation processing time depends on the size of the file, the source and target languages, and current service load. For a typical Word document under 50 pages, translation usually completes within two to five minutes. Larger documents, especially PDFs with complex layouts, can take 15–30 minutes. The translated copy will appear in the same SharePoint library folder as the original file, with the target language name added to the filename. You can check translation status by looking at the document library's processing queue, accessible through Library settings → Document processing.
Do I need a separate Azure subscription for document processing, or can I use our existing one?
You can absolutely use your organization's existing Azure subscription, you don't need to create a new one. During the pay-as-you-go setup in the SharePoint admin center, you'll be prompted to select from subscriptions that your admin account has access to. The document processing charges will appear as a separate service meter in that subscription's billing. Many organizations simply create a dedicated resource group within their existing subscription (something like rg-m365-docprocessing) to keep document processing costs clearly separated from other Azure spend, which makes cost monitoring and budget alerts much easier to manage.