Sensitivity labels - what do they look like
summary
Sensitivity labels act as metadata not automatic access control: they require Office 365 E5 to create and Power BI Pro/Premium PPU to apply, and service views show labels while enforcement is limited (exports to Excel can be blocked, Power BI desktop often does not prevent viewing). One label applies per artifact and reports inherit the most restrictive label when mashing sources, Azure SQL supports column-level classification (or MIP at DB level), Purview and Fabric scan and report uptake, and some tools (report builder, workbooks, B2B) have notable gaps.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 5:43Setup in M365 admin center
- 10:37Labels in Excel and Word
- 13:27Labels in Power BI Desktop
- 16:36Enable in Power BI service
- 20:10View labels in Power BI
- 22:58Labels in dataflows and dashboards
- 26:01Export to Excel and security
- 27:27Inheriting labels in reports
- 31:41Labels in Fabric and lakehouses
- 33:24Azure SQL protection options
- 36:57Scanning labels in Purview
- 40:11Gotchas and limitations
- 43:20Recap and Q&A session
related talks
54mData Governance using Azure Purview
22mManaging access to data sources in your data estate with Microsoft Purview
51mMaximize the business value of data with Microsoft Purview Data Governance
30mBeyond Labels: Evolving Data Classification
40mBuilding trust in your data. Why data governance is the key to success.
59mSecuring sensitive information with Glue Sensitive Data Detection
11mCreating Effective Labels
48mMicrosoft Purview Data Governance: Updates & Roadmap