Fix Microsoft 365 Document Processing Not Working
Why Microsoft 365 Document Processing Stops Working
I've seen this exact frustration play out dozens of times: you go to apply a document processing model to a SharePoint library, or you try to kick off an autofill column job, and nothing happens. Or worse , you get a vague permission error with no actionable message. Microsoft 365 document processing is genuinely powerful technology, but the setup path has enough moving parts that things break in ways you don't expect.
Here's the core reason this happens more than any other: document processing services are pay-as-you-go, and they require an active Azure subscription linked to your tenant. This isn't optional or automatic. Until that billing connection is established, every service , autofill columns, optical character recognition, document translation, eSignature, prebuilt models, structured and freeform models, unstructured models, the whole suite, sits completely dormant. No error message tells you this clearly. The admin center just shows features as unavailable or greyed out, and most IT admins waste hours looking in the wrong place.
The second major cause I see is the licensing transition. Microsoft ended the sale of per-user licenses for document processing services. If your organization was running on per-user licenses purchased before that cutoff, those licenses eventually expire, and when they do, everything stops without warning unless you've already switched to pay-as-you-go billing. A lot of teams are caught off guard by this because the licenses keep working right up until they don't.
Government Community Cloud (GCC) tenants have their own layer of complexity. Pay-as-you-go is not yet available for GCC environments, which means GCC admins are stuck on the per-user path until Microsoft rolls out that capability. If you're in a GCC tenant and you're seeing features that appear available in Microsoft's documentation but are missing from your admin center, this is almost certainly why.
There are also configuration errors at the SharePoint level, specifically around content types, library permissions, and Power Platform environment settings for structured or freeform models. And then there's the AI Builder credits situation: Microsoft announced the progressive end of AI Builder credits in October 2025, which affects any workflows that were consuming those credits instead of billing through the pay-as-you-go meters.
I know this is frustrating, especially when it blocks document automation work that your team is counting on. The good news is that every one of these problems has a clear fix once you know where to look. Browse all Microsoft fix guides →
The Quick Fix, Try This First
Before you dig into anything complicated, run through this check. It resolves the majority of Microsoft 365 document processing problems in under ten minutes.
Open the Microsoft 365 admin center at admin.microsoft.com. In the left navigation panel, go to Settings > Org settings, then click Services in the tab row. Scroll down until you see SharePoint in the list and click it. From there, navigate to the Microsoft 365 content center link, this is where document processing is managed at the tenant level.
Once you're in the content center, look for the Document processing section. You'll either see a prompt to set up pay-as-you-go billing, or you'll see service tiles. If you see the billing setup prompt, that's your answer, the Azure subscription link is missing, and that's what's killing every service for your users. Click Set up pay-as-you-go billing and follow the wizard. You'll need an active Azure subscription and Owner or Contributor rights on that subscription to complete the connection.
If billing is already set up and services still aren't responding, check your Azure subscription status at portal.azure.com. Go to Subscriptions and confirm the subscription linked to your tenant shows a status of Active. A disabled or over-quota subscription will silently break all document processing meters, Azure won't surface this error back through the SharePoint UI.
After confirming the subscription is active, go back to the content center and click any document processing service tile to verify it shows as enabled. For individual users seeing problems, have them sign out of all Microsoft 365 apps, clear the browser cache completely (not just cookies, full cache), and sign back in. Token refresh issues cause a surprising number of "it's broken" reports that disappear after a clean sign-in cycle.
Microsoft-SharePoint-Online that gets provisioned automatically. If your Azure subscription has policies that block automatic resource group creation (common in locked-down enterprise environments), the billing setup wizard will silently fail partway through. Check Azure Policy assignments on your subscription before running the setup wizard, it saves hours of re-running the same steps.
This is the foundational step. Microsoft 365 document processing runs on pay-as-you-go service meters in Azure. Without this connection, nothing else matters, no models run, no translations process, no OCR jobs fire.
Sign into the Microsoft 365 admin center (admin.microsoft.com) as a Global Administrator or SharePoint Administrator. Navigate to Setup > Use your apps, or alternatively go directly to Settings > Org settings > Services > SharePoint. Click the link to open the SharePoint admin center.
Inside the SharePoint admin center, click Content services in the left rail, then select Document processing. You'll land on the services overview page. Look for a banner or button labeled "Set up pay-as-you-go" or "Configure billing."
Click through the billing setup wizard. You'll be asked to:
- Select your Azure subscription from the dropdown (you must have Owner or Contributor role on this subscription)
- Choose or create a Resource group in that subscription
- Select your preferred Azure region
- Review the billing terms and confirm
After completing the wizard, wait 15–30 minutes for the service meters to activate. Refresh the Document processing page, all service tiles should now appear enabled rather than greyed out. If you see a service still showing as unavailable after 30 minutes, move on to Step 2.
# Verify the Azure resource registration via PowerShell (optional check)
Connect-AzAccount
Get-AzResourceProvider -ProviderNamespace "Microsoft.SharePoint" | Select-Object ProviderNamespace, RegistrationStateIf RegistrationState shows NotRegistered, run Register-AzResourceProvider -ProviderNamespace "Microsoft.SharePoint" and wait for it to complete.
Pay-as-you-go billing being active doesn't automatically turn on every service. Each document processing capability, autofill columns, document translation, eSignature, optical character recognition, content assembly, image tagging, taxonomy tagging, prebuilt models, structured and freeform models, unstructured models, must be individually enabled.
In the SharePoint admin center, go to Content services > Document processing. You'll see tiles for each service. Click on a tile to open its settings panel. For each service you want to activate, toggle the switch to On and click Save.
Some services have additional configuration steps beyond the toggle:
- Autofill columns: Requires specifying which SharePoint libraries are eligible. You can set this per-library or tenant-wide.
- eSignature: Requires accepting specific terms of service related to electronic signature legal compliance in your region.
- Document translation: No additional configuration beyond enabling, but verify your target languages are included in the supported list.
- Optical character recognition: Toggle-only activation, no further setup needed at the tenant level.
For prebuilt, structured/freeform, and unstructured models, enabling the service at the admin center level just unlocks the capability. Individual models are still created and applied at the content center or SharePoint library level by users with the appropriate site permissions.
After enabling each service, test it immediately with a single test document in a non-production library. Don't wait until you've enabled everything to test, isolating which service is misbehaving is much easier when you check them one at a time.
You should see processing jobs appear in the library's Automation menu once a service is correctly enabled and applied to that library.
Autofill columns is one of the highest-value features in Microsoft 365 document processing and also one of the most commonly misconfigured. It uses large language models to extract or generate content and write it directly into SharePoint metadata columns. When it stops working, the columns just stay blank, no error, no notification, just silence.
First, confirm the feature is enabled at both the tenant level (Step 2) and the specific library level. In your SharePoint document library, click the Automate button in the command bar. If you don't see Autofill columns as an option, the feature isn't enabled for this library specifically, even if it's on at the tenant level.
To enable it for the library: go to Library settings > Autofill columns. Click Set up and follow the configuration wizard. During setup, you'll map each autofill column to a source (either extracted from document content or generated by the LLM based on instructions you write). Common mistakes here:
- The column being mapped doesn't exist in the library's content type, create the column first, then configure autofill
- The LLM instruction is too vague, be specific: instead of "get the date," write "Extract the contract effective date in MM/DD/YYYY format from the first page"
- The document format isn't supported, PDFs and Word documents work well; image-only PDFs (scans without embedded text) require OCR to be enabled first
After reconfiguring, upload a fresh test document and check the column values after 2–5 minutes. Autofill jobs are asynchronous and don't run instantly. If columns still aren't populating after 10 minutes, check the Document processing activity log in the content center for error codes.
# Check autofill job status via SharePoint REST API
GET https://{tenant}.sharepoint.com/sites/{site}/_api/machinelearning/publications
Authorization: Bearer {token}
Accept: application/jsonIf you're getting errors when trying to apply a document processing model to a library, or models were applied but aren't processing new documents, there are three specific things to check.
Check 1: Content center access. Models are created and managed through the Microsoft 365 content center. The user creating or applying the model needs to be a Site member or higher on the content center site. Go to the content center site, click the gear icon, then Site permissions, and verify the user or group has appropriate access.
Check 2: Library content type association. For unstructured models in particular, the model works by classifying documents and applying a content type. That content type must exist in the site's content type hub and be published to the library you're targeting. Navigate to Library settings > Advanced settings and confirm Allow management of content types is set to Yes. Then under Content Types in library settings, confirm the model's associated content type appears in the list.
Check 3: Per-user license vs. pay-as-you-go conflict. If your tenant has a mix of users with active per-user licenses and users without them, model creation rights differ. Per-user license holders can create prebuilt, structured, and freeform models. Pay-as-you-go users can also create these models as long as pay-as-you-go billing is active. The error occurs when someone with an expired per-user license tries to create a model before the tenant has fully switched to pay-as-you-go billing, they fall into a licensing gap.
# Check current Syntex/document processing license assignments via PowerShell
Connect-MsolService
Get-MsolUser -All | Where-Object { $_.Licenses.AccountSkuId -like "*Syntex*" } | Select-Object UserPrincipalName, LicensesAfter confirming licensing is clean, re-apply the model to the library. Go to the content center, open your model, and click Add a library. Select the target site and library. You should see a confirmation message that the model was published to that library within a few seconds.
Document translation and eSignature both fail in unique ways that trip people up specifically because their error messages point in the wrong direction.
Document Translation not creating translated copies: The most common cause is that the source document library doesn't have versioning enabled. Document translation creates a copy of the document in the same library (or a specified destination library) with the translated content. If the library's file storage quota is near its limit, the translation job will fail silently. Check the library's storage: go to Library settings > Storage metrics. Also verify that the language pair you're requesting is actually supported, go to the Document translation service tile in the admin center and review the supported languages list.
For documents larger than 40 MB or with more than 200 pages, translation jobs take significantly longer and may time out in some browser sessions. These jobs run in the background even after your session closes, check the job status by going to Automate > Document translation history in the library view.
eSignature requests not sending or recipients not receiving: First check that eSignature is enabled and that the user sending the request has a Microsoft 365 license (any license, eSignature access is organization-wide as long as pay-as-you-go is set up). The document being sent for signature must be stored in a SharePoint document library, eSignature doesn't work with files stored in OneDrive personal folders or local file shares.
If recipients report not receiving the signature request email, check your organization's external sharing settings in the SharePoint admin center. eSignature requests to external recipients require external sharing to be enabled at the tenant level. Go to SharePoint admin center > Policies > Sharing and ensure the setting is not locked to Only people in your organization.
# Verify SharePoint external sharing level via PowerShell
Connect-SPOService -Url https://{tenant}-admin.sharepoint.com
Get-SPOTenant | Select-Object SharingCapabilityIf SharingCapability returns Disabled, update it to at least ExternalUserSharingOnly for eSignature to reach external recipients.
Advanced Troubleshooting for Microsoft 365 Document Processing
When the standard fixes don't resolve the problem, you're usually dealing with something at the enterprise configuration level, tenant policies, Power Platform environment settings, or subtle Azure subscription issues that need deeper investigation.
Event Viewer and ULS Logs: Microsoft 365 document processing jobs log detailed telemetry to the SharePoint Unified Logging Service. If you have access to a SharePoint Server hybrid environment or need to pull server-side logs, use the SharePoint admin center's Health monitoring section under Reports > Usage. For tenant admins, the most useful audit trail is in the Microsoft Purview compliance portal under Audit > Search, filter by activity type SyntexModelApplied or DocumentProcessingJobCompleted to see exactly when models fired and whether they errored.
Power Platform Environment Issues for Structured and Freeform Models: Structured and freeform document processing models that run in a custom Power Platform environment (rather than the default environment) require that environment to be specifically configured for document processing. This is documented by Microsoft as a separate setup step that many admins miss entirely. If your models work in the default Power Platform environment but fail in a custom one, go to the Power Platform admin center at admin.powerplatform.microsoft.com. Select your custom environment, click Settings, then navigate to Product > Features and verify that AI Builder is toggled on for that environment.
AI Builder Credits End-of-Life Impact: Microsoft announced the progressive end of AI Builder credits in October 2025. Any document processing workflows that were consuming AI Builder credits, rather than billing through pay-as-you-go Azure meters, will eventually stop working as those credits are depleted and no longer replenished. If you're in an organization that heavily used AI Builder credits for document processing automation, audit your Power Automate flows and Power Apps that call AI Builder actions. Each of those flows will need to be evaluated: some will naturally migrate to the pay-as-you-go meter billing, while others may need explicit reconfiguration.
Tenant-Level Feature Flags via PowerShell: Some document processing capabilities are controlled by tenant-level SharePoint feature flags that aren't exposed in the admin center UI. If a service is enabled in the admin center but still not appearing for users, run this check:
# Check SharePoint tenant-level document processing feature flags
Connect-SPOService -Url https://{tenant}-admin.sharepoint.com
Get-SPOTenant | Select-Object EnableAIPrefixSensitivityLabel, IsFluidEnabled, EnableAutoNewsDigestFor content type publishing issues blocking model deployment, check that the content type hub is properly configured:
# Verify content type hub URL
Get-SPOTenant | Select-Object ContentTypeSyncSiteTemplatesList, ContentCenterMigrationStateIf ContentCenterMigrationState shows anything other than Completed, the content center setup wasn't fully provisioned and models can't be published to libraries until that migration finishes. Contact Microsoft Support to manually trigger the content center provisioning job.
Prevention & Best Practices for Document Processing in Microsoft 365
Most of the Microsoft 365 document processing problems I see on enterprise tenants are completely avoidable with a few upfront configuration habits. The technology is solid, it's the setup and maintenance hygiene that causes the headaches.
Plan your Azure subscription strategy before you need it. The single biggest source of document processing outages is Azure subscription disruption, a subscription gets disabled due to spending limits, a credit card expires, or a subscription gets moved to a different billing account. Because the Microsoft 365 document processing meters bill through Azure, any interruption to the subscription instantly breaks all services for the entire tenant. Set up Azure cost alerts and billing health notifications in Azure Cost Management so you're notified well before any subscription issue becomes a service outage.
Proactively migrate off per-user licenses. Per-user licenses for document processing services are no longer sold by Microsoft. Existing licenses can still be assigned to new users while they remain active, but once they expire, the switch to pay-as-you-go is not optional. Don't wait for expiration day, set up pay-as-you-go billing now, validate that every service your organization uses works correctly under the pay-as-you-go model, then let the per-user licenses wind down naturally. Running both in parallel during the transition gives you a safety net.
Test models in a staging library before production deployment. Document processing models, especially prebuilt models for invoices, contracts, and receipts, and custom trained unstructured models, should always be validated against a representative sample of 20–30 real documents before being applied to production libraries. Model accuracy against your specific document variations may differ significantly from the benchmark accuracy numbers in Microsoft's documentation. Build a dedicated test library in a non-production site for this purpose.
Document your pay-as-you-go configuration. Record the Azure subscription ID, resource group name, and region used for your document processing billing setup. This information is critical during incident response, if billing breaks at 11 PM on a Friday, whoever is on call needs to find that information in seconds, not spend 30 minutes hunting through the Azure portal.
- Set Azure spending alerts at 80% and 100% of your monthly document processing budget, billing interruptions kill all services instantly
- Create a dedicated SharePoint content center site for model management, separate from production team sites, to keep model governance clean
- Enable document library versioning everywhere you deploy document processing models, several services write metadata back to documents and versioning gives you a recovery path
- Review and update your Power Automate flows that call AI Builder actions before the AI Builder credits sunset impacts them, migrate to pay-as-you-go meter billing proactively
Frequently Asked Questions
Why are all my document processing features greyed out in the SharePoint admin center?
This almost always means pay-as-you-go billing hasn't been set up yet, or the Azure subscription it was connected to has been disabled. Go to SharePoint admin center > Content services > Document processing and look for the billing setup prompt. You need to be a Global Administrator or SharePoint Administrator with Owner or Contributor rights on an active Azure subscription to complete the setup. Once billing is connected and active, the service tiles should become clickable within 15–30 minutes.
Can individual users access document processing services or does an admin have to enable it for them?
Under the pay-as-you-go model, any user in your Microsoft 365 tenant can use document processing services, as long as they have any valid Microsoft 365 license and the tenant-level services are enabled by an admin. There's no per-user license required for access. The admin enables the services at the tenant level, sets up billing, and from that point on, usage is available organization-wide with costs billed to the Azure subscription based on actual consumption.
My organization is on GCC (Government Community Cloud), why can't I see the pay-as-you-go setup option?
Pay-as-you-go billing for document processing services is not yet available for Government Community Cloud tenants. This is a documented limitation. GCC organizations can continue using per-user licenses for document processing while Microsoft works on bringing pay-as-you-go capability to the GCC environment. Keep an eye on the Microsoft 365 roadmap and the Microsoft Tech Community blog for GCC availability announcements. In the meantime, make sure your per-user licenses are renewed and assigned appropriately.
I set up pay-as-you-go billing but I'm not seeing any charges in Azure, is the billing actually working?
It's possible, Azure billing for document processing meters can take up to 24–48 hours to appear in Azure Cost Management after your first usage events. If you've used services and still see zero charges after 48 hours, first check that you're looking at the correct Azure subscription (the one you selected during billing setup). Then go to Azure Cost Management > Cost analysis and filter by the Microsoft.SharePoint resource provider. If nothing appears, verify that the resource group Microsoft-SharePoint-Online exists in your subscription, if it doesn't, the billing link wasn't fully established.
What happened to Microsoft Syntex? Is that the same as document processing?
Yes, same product, new name. Microsoft rebranded Syntex as "document processing for Microsoft 365" as part of a broader naming consolidation. All features and functionality remain identical. The pay-as-you-go services that were previously branded as Microsoft Syntex pay-as-you-go are now simply referred to as document processing services. If you have existing documentation, training materials, or admin scripts that reference "Syntex," they still apply, the underlying APIs and admin center paths haven't changed, just the marketing name.
My autofill columns were working and then stopped, what changed?
The most common reason autofill columns stop working after previously functioning correctly is a disruption to the Azure subscription billing connection. Check the subscription status in Azure portal first. The second most common cause is a change to the library's content type structure, if a column that autofill was mapped to gets deleted or renamed, the autofill configuration breaks silently without alerting you. Go to Library settings > Autofill columns and review each column mapping. Finally, if your organization had AI Builder credits configured as part of the autofill pipeline, those credits are being progressively ended and the pipeline may need to be updated to use pay-as-you-go billing meters instead.