Fix Microsoft 365 Document Processing Not Working

This is the foundational step. Every Microsoft 365 document processing service, autofill columns, document translation, eSignature, optical character recognition, content assembly, image tagging, taxonomy tagging, and all the model types, bills through Azure. If there's no active Azure subscription linked to your tenant, none of these services will work, period.

To set up pay-as-you-go billing for document processing:

1. Sign into the Microsoft 365 admin center (admin.microsoft.com) as a Global Administrator.
2. Go to Setup in the left menu.
3. Search for "Document processing" in the search bar at the top of the Setup page.
4. Click Set up pay-as-you-go billing.
5. On the billing setup screen, you'll be asked to select an Azure subscription, a Resource Group, and a Region. You need Owner or Contributor access on the Azure subscription to proceed.
6. Select your subscription, choose or create a resource group, select the region closest to your SharePoint tenant geography, and click Save.

If the Azure subscription dropdown appears blank, it means your Microsoft 365 admin account doesn't have the right permissions on any Azure subscriptions. You'll need to work with your Azure billing administrator to grant you at least Contributor access on an active subscription before retrying.

Once saved, wait five to ten minutes and then revisit the SharePoint admin center. The document processing services should now show as available. If you still see them as unavailable after fifteen minutes, sign out of both admin.microsoft.com and portal.azure.com, clear your browser cache, and sign back in to force a permissions token refresh.

What you should see when this works: the document processing section in the Microsoft 365 admin center changes from a "Set up" prompt to a status page showing your linked Azure subscription name and the list of available services.

Even with pay-as-you-go billing active, individual users still need a base Microsoft 365 license to access document processing features. The pay-as-you-go model gives any licensed user in the tenant access, but "any user" in Microsoft's documentation means any user who already has a Microsoft 365 license assigned, not an unlicensed user.

This catches IT admins off guard fairly often. You set up billing correctly, everything looks good in the admin center, but one specific user or team keeps reporting that features aren't available to them. Nine times out of ten, that user was added to the tenant but never got a Microsoft 365 license assigned, or their license was removed during an offboarding process and then they were re-onboarded without a new license assignment.

To check and fix this:

1. In the Microsoft 365 admin center, go to Users > Active users.
2. Find the affected user and click their name.
3. On their profile page, click the Licenses and apps tab.
4. Confirm they have a Microsoft 365 license (Business Basic, Business Standard, Business Premium, E3, E5, or equivalent) checked and assigned.
5. If not, check the appropriate license and click Save changes.

If your organization is still running on active per-user licenses (from before Microsoft stopped selling them), those users can still be assigned to new people, existing licenses just can't be renewed once they expire. Check this under Billing > Your products in the admin center. You'll see the per-user document processing license listed there if you have one, along with its expiration date.

After assigning or verifying a license, wait about five minutes for the change to propagate. Have the user sign out of all Microsoft 365 sessions and sign back in. If they're using SharePoint in a browser, a full browser cache clear (Ctrl+Shift+Delete) often helps the new permissions surface correctly.

Pay-as-you-go billing being active doesn't automatically turn on every service. Some document processing services need to be explicitly enabled in the SharePoint admin center before they're available in document libraries. This is a step that's easy to skip, and Microsoft's onboarding wizard doesn't always make it obvious.

Here's how to enable the specific services you need:

1. Go to the SharePoint admin center at your-tenant-admin.sharepoint.com.
2. In the left nav, click Settings.
3. Scroll down to find Document processing (previously labeled Syntex in older tenants, if you don't see it, try searching for "autofill" or "content AI" in the settings search bar).
4. You'll see a list of available services. Each one has its own toggle:
   • Autofill columns, uses LLMs to extract or generate metadata from document content
   • Document translation, creates translated copies in SharePoint libraries
   • eSignature, sends electronic signing requests while keeping documents in Microsoft 365
   • Optical character recognition, extracts text from images and scanned documents
   • Image tagging, applies AI tags to images in document libraries
   • Taxonomy tagging, applies term sets from the SharePoint term store automatically
5. Enable each service your organization needs by toggling it on.

For model-based services, prebuilt document processing, structured and freeform models, and unstructured document processing models, enabling the service here doesn't automatically apply a model to any library. You'll still need to go into each SharePoint library, click Automate > Apply a document processing model, and configure which model runs on that library's content.

What success looks like: after enabling a service, navigate to a SharePoint document library, click the Automate button in the top toolbar, and you should see the relevant options appear. If "Apply a document processing model" or "Autofill a column" options are still missing after enabling the service and waiting five minutes, proceed to Step 4.

This step is specifically for users who have models set up, prebuilt, structured, freeform, or unstructured, but the models have stopped running, aren't processing new files, or are throwing errors when documents are uploaded.

The most common cause here is a disconnect between the model and the library that happens after a service interruption, a tenant migration, or an expiring per-user license. The model itself is intact and hasn't been deleted, but its association with the library needs to be re-established.

Here's how to reapply a model:

1. Navigate to the SharePoint document library that should be processing documents.
2. Click Automate in the command bar, then select Apply a document processing model.
3. In the panel that opens, you'll see any models currently applied to this library. If the list is empty when you expected to see a model, you need to navigate to the content center where the model was created.
4. To find your content center: go to the SharePoint start page, look for a site named something like "[Your Org] Content Center", this is the site Microsoft created when document processing was first enabled.
5. From within the content center, go to Models in the left nav, find the model you want, click on it, then click Apply model and select the target library.

For unstructured document processing models specifically, which classify documents that vary in composition and extract information from them, you may need to retrain the model if it was created under a per-user license and the license has since expired. Microsoft's documentation confirms that existing per-user license holders can still create and run prebuilt, structured, and freeform models, but model behavior may degrade as the transition to pay-as-you-go completes.

# To check which libraries a model is applied to via SharePoint PnP PowerShell:
Connect-PnPOnline -Url "https://yourtenant.sharepoint.com/sites/ContentCenter" -Interactive
Get-PnPSyntexModel | Select-Object Title, ApplicationCount

When it's working: upload a test document to the library. Within a few minutes (processing is near-real-time for most services), the document's metadata columns should populate with extracted values.

If you're seeing errors related to "AI Builder credits" or your document processing workflows inside Power Automate suddenly stopped functioning, this step is for you. Microsoft announced in October 2025 that AI Builder credits are being progressively retired. This directly affects organizations that built document processing pipelines using Power Platform flows that consumed AI Builder credits behind the scenes.

The fix is to transition those workflows from AI Builder credit consumption to the pay-as-you-go meter system. Here's how:

1. In the Power Platform admin center (admin.powerplatform.microsoft.com), go to Billing > Licenses and check your current AI Builder credits balance. A zero or near-zero balance with no renewal path is a signal to migrate immediately.
2. Back in the Microsoft 365 admin center, confirm your pay-as-you-go billing for document processing is linked to an active Azure subscription (Step 1 of this guide).
3. For any Power Automate flows that were using the AI Builder document processing action, review whether those actions can be replaced with direct SharePoint document processing service calls. In many cases, a flow that was using "Process and save information from documents" via AI Builder can be simplified by letting the SharePoint library's applied model do the extraction automatically, removing Power Automate from the processing chain entirely.
4. If you need to keep a Power Automate integration, check Microsoft's updated connector documentation for the new pay-as-you-go meter-based actions. These bill against your Azure subscription rather than consuming AI Builder credits.
5. For custom Power Platform environments running structured or freeform models, Microsoft's documentation specifically calls out that you need to set up a custom Power Platform environment separately. This is done from the SharePoint admin center under Settings > Document processing > Power Platform environment.

When this is resolved correctly, your Power Automate flow run history should show successful document processing actions again, and your Azure subscription in the Azure portal will start showing usage under the Microsoft 365 document processing service meter, confirming billing is flowing through the correct channel.