Find your PII reports and make your data safer
summary
Three methods to locate PII are described with concrete tradeoffs: Premium scan that adds 30% extra compute to every refresh and misses some fields; database-level classification via Synapse/Azure SQL that auto-mombs models to sensitivity labels; and a Gateway/cloud-connector pattern that maps connection IDs to enforce service-account access. Practical steps include using Microsoft Purview, DLP and Microsoft Defender, auditing re-share and downloads, and watch for scale issues (examples: 10,000 reports, 6,000 sources).
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:00Locate PII in Power BI
- 9:33Track PII with Gateway connectors
- 15:54Information protection and DLP
- 23:05Sensitivity labels in Power BI and Fabric
- 27:42Parent labels and security risks
- 30:29PII scanning and labeling policies
- 34:10Microsoft Defender for data protection
- 41:17Block external users and personal workspaces
- 43:48Monitor reshare access and usage
- 49:12Audit settings and Q&A
related talks
28mHow Privacy Engineers Deliver ROI
01h 59mDeep Dive Workshop – Data Security and Data Protection
01h 59mDeep Dive Workshop – Data Security and Data Protection
24mStop Making Your Data Team the 'Data Police'
54mData Governance using Azure Purview
29mOperationalizing Data In Support Of Privacy Regulations
51mMaximize the business value of data with Microsoft Purview Data Governance
22mEnhancing Privacy through an Interactive On-demand Incremental Information