Classifications, Sensitivity and Technical Metadata

Learn how scanning, classifications and source metadata contribute to the technical governance context visible in Microsoft Purview.

Scanning does more than create an inventory of asset names. Depending on the source and connector capabilities, Microsoft Purview can ingest schema information, classifications, labels or other source metadata that helps explain how an asset should be governed.

Classifications

Classifications can identify patterns such as personal or sensitive information where the connector and scan configuration support classification.

Sensitivity metadata

Sensitivity-label behaviour varies by source. Data Custodians should understand what the connector can ingest or apply rather than assuming every platform behaves in the same way.

Source metadata

Some connectors also ingest platform-native properties or tags. This technical context can then support Data Stewards, Data Product Owners and consumers in Unified Catalog.

The Data Custodian’s responsibility is to make sure the technical metadata pipeline is working and to understand the capability differences between source types.

Learning with Data SkyLab Studio

Follow practical Microsoft Purview and Data Governance learning from Data SkyLab Studio on YouTube.