Purview auto-labeling for legacy formats announced
- Maxime Hiez
- Purview
- 14 Nov, 2026
Introduction
SharePoint and OneDrive archives often hold old .doc, .xls and .ppt files that Microsoft Purview auto-labeling ignores today. Announcement MC1530948, published on October 29, 2026, extends service-side auto-labeling to these three formats. The feature is announced, not available : Public Preview is planned for early to mid-November 2026 and general availability for late November 2026. This article covers what changes and what admins need to prepare.
Check the article on auto-labeling and adaptive scopes HERE.
What changes for auto-labeling
Service-side auto-labeling evaluates and applies Sensitivity Labels to Word (.doc), Excel (.xls) and PowerPoint (.ppt) files in SharePoint and OneDrive, in both simulation and enforcement mode. So far, auto-labeling only supports .docx, .xlsx, .pptx and PDF files, and the Learn documentation has not yet been updated for the legacy formats.
On timing, roadmap item 574363 (Worldwide, In development status) points to preview and general availability in November 2026. For DoD, GCC and GCC High, item 578872 (In development status) plans general availability in December 2026.
What admins need to do
New auto-labeling policies cover the legacy formats automatically. Existing policies need action : a small edit (for example adding or removing a comment), a save, then a new run to trigger a fresh scan.
The announced approach comes down to a few steps :
- Review the labels and auto-labeling policies, including their SharePoint and OneDrive locations
- Identify the policies to extend
- Edit each policy slightly, save it, then run it again
- Run the updated policies in simulation mode first and check the results before enforcing
No dedicated toggle is reported : the policy itself is the lever.
Points to watch
The sources mention no change to the auto-labeling limits : 500 000 files per day at most for the tenant, 100 policies, 1 000 explicitly selected SharePoint sites and 20 000 000 matching files per simulation. The daily cap will now have to cover more files, which suggests more matches and longer runs (interpretation, not an announced fact).
The prerequisites stay those of the service : labels enabled for SharePoint and OneDrive, the Compliance Administrator or Compliance Data Administrator role, and a file open for editing cannot be labeled. Office apps do not natively label the 97-2003 format, and in the information protection client, saving a labeled file as 97-2003 removes the label. It is unknown whether this behavior applies to a label applied by the service.
Encryption of labeled files, licensing and whether preview requires enrollment are not documented. The only pointer is a general one : auto-labeling depends on licensing.
Conclusion
This change closes a known gap : entire archives escaped policies because they had stayed in .doc or .xls. Preview is announced for this month, so it is worth spotting the policies to rerun now. Once it reaches the tenant, simulation first, then enforcement, is the safest path. Until general availability is confirmed and encryption and licensing are documented, it is better not to promise anything to the business.
Sources
Microsoft 365 Roadmap - 574363
Microsoft 365 Roadmap - 578872
Microsoft Learn - Automatically apply a sensitivity label to Microsoft 365 data
Microsoft Learn - Resolve issues with auto-labeling policies in Microsoft Purview
Did you enjoy this post ? If you have any questions, comments or suggestions, please feel free to send me a message from the contact form.
Don’t forget to follow us and share this post.