Blog Post

Microsoft SharePoint Blog
2 MIN READ

Processing status pane coming in July for SharePoint Autofill columns and document translation!

Karl_Harriau's avatar
Karl_Harriau
Icon for Microsoft rankMicrosoft
Jul 01, 2025

We're excited to announce the Processing status pane will be available for our global customers by the end of July at no charge.

The Processing status pane introduces a new visual way to track content AI model actions like Autofill columns and document translation, directly within your SharePoint document libraries. 

What's new?

The new Processing Status pane provides real-time insights into how Autofill columns and document translation are processing your documents including:

  • Tracking when a file is being processed 
  • Viewing processing status:  In Progress, Completed or Failed
  • Getting live status updates on the processing job
    • Access live status updates on your document translation job
    • Access live status updates on your autofill column

Note: The Processing status pane replaces our existing Status column which will now be hidden by default and deprecated in the future. 

Document translation Processing status paneAutofill columns Processing status paneEasily access the Processing Status pane for either Autofill columns or Document translation

Try it out today!

  1. Trigger Autofill columns or document translation on your documents
  2. Open the Processing status pane from the command bar, context menu or message bar
  3. Track model activity and review processing status in real time
  4. Filter by failed status or date range (up to 60 days of history) to quickly identify files that need attention
  5. Use error details to determine next steps

What's next?

We're also working on a Processing status pane for optical character recognition (OCR). 

Expanded file format support for document translation available now!

An additional 13 new file types for are now available for document translation. Those include mdown, mdtext, mdtxt, mdwn, mht, mhtml, mkd, mkdn, odt, rmd, tab, tsv, and most notably, XLIFF. 

With this release, you can now translate .xlf (XLIFF) files directly within SharePoint document libraries, unlocking new localization capabilities for eLearning platforms and software interfaces. XLIFF is a widely adopted industry standard used by content authors, learning teams, and localization vendors to export structured language assets from authoring tools. Now, with just a few clicks, your organization can localize training materials and user-facing content at scale, without relying on third-party workflows or manual format conversion.

Additional file type support is generally available as of 6/30/25. 

Reminder!

Through December 2025, if you have pay-as-you-go billing set up, your organization receives a limited amount of included capacity each month for selected services, letting you try SharePoint content processing services at no cost. This offering doesn't include capacity for Microsoft 365 Archive or Microsoft 365 Backup. For more information, check out the available SharePoint content processing features on MS Learn.

Let us know your thoughts.

Please feel free to add a question or comment or reach out to me via LinkedIn.

Updated Aug 18, 2025
Version 2.0

1 Comment

  • Hello Karl_Harriau​,

    Thanks for the write-up. The pane is a real improvement, but I am hitting a scale limit with it.

    In a production scenario I see roughly 10% of files fail autofill processing. When I re-run autofill manually on the same file, it succeeds every time, so the failure does not come from the document itself. Something fails on the service side and there is no retry.

    Two things make this hard to live with:

    1. No automatic retry. Every failed file has to be found and re-triggered by hand.

    2. The pane is scoped to a single library. My use case has more than 250 document libraries in the same site (permission segmentation), with hundreds of files uploaded every day. Nobody can realistically open 200 panes to look for failures.

    So two questions:

    - Is an automatic retry on failure planned for autofill columns?

    - Is there any cross-library or site-level view of processing failures, or a supported API / Power Automate action to re-trigger autofill on a file? Right now the only options I can find are undocumented REST calls (thank you @Leon amstrong), which I would rather not put into production.

    Any guidance would be very welcome.