Big news for anyone running Microsoft Purview Information Protection 👇
𝐒𝐡𝐚𝐫𝐞𝐏𝐨𝐢𝐧𝐭 𝐥𝐢𝐛𝐫𝐚𝐫𝐢𝐞𝐬 𝐜𝐚𝐧 𝐧𝐨𝐰 𝐚𝐮𝐭𝐨-𝐥𝐚𝐛𝐞𝐥 𝐞𝐱𝐢𝐬𝐭𝐢𝐧𝐠 𝐟𝐢𝐥𝐞𝐬 𝐚𝐭 𝐫𝐞𝐬𝐭 𝐭𝐨 𝐦𝐚𝐭𝐜𝐡 𝐭𝐡𝐞 𝐝𝐞𝐟𝐚𝐮𝐥𝐭 𝐬𝐞𝐧𝐬𝐢𝐭𝐢𝐯𝐢𝐭𝐲 𝐥𝐚𝐛𝐞𝐥.
Default labels only applied to new files in the older experience. Your options for existing content at rest:
• Manual labeling (doesn’t scale)
• SIT-based auto-labeling (only works if content matches patterns)
• On-demand classification (costly, complex)
• Leave it unprotected
𝑻𝒉𝒆 𝒏𝒆𝒘 𝒆𝒙𝒑𝒆𝒓𝒊𝒆𝒏𝒄𝒆
- Set a default label on a library → Purview applies it to everything already in there:
- Close labeling gaps on migrated content at rest
- Protect legacy files that don’t match SIT patterns
- Simpler compliance model – label by location, not by content analysis
- Reduce manual governance overhead
- Finally address the “what about our existing data?” audit question
For NHS Digital and other highly regulated environments, this changes how we approach SharePoint governance. We can finally have consistent protection across both new and existing data.
One step closer to true secure-by-default for everything, not just new content.
Roadmap ID: 559105