Skip to content

Commit 622e114

Browse files
authored
in progress
1 parent 538c3ca commit 622e114

File tree

1 file changed

+106
-0
lines changed

1 file changed

+106
-0
lines changed

Workloads-Specific/Purview/BestPractices.md

Lines changed: 106 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,114 @@ Last updated: 2025-05-03
1313
<details>
1414
<summary><b>List of References</b> (Click to expand)</summary>
1515

16+
- [Use Microsoft Purview to govern Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/governance/microsoft-purview-fabric)
17+
- [Governance overview and guidance](https://learn.microsoft.com/en-us/fabric/governance/governance-compliance-overview)
18+
- [Metadata scanning overview](https://learn.microsoft.com/en-us/fabric/governance/metadata-scanning-overview)
19+
20+
</details>
21+
22+
<details>
23+
<summary><b>Table of Content</b> (Click to expand)</summary>
24+
25+
- [Unified Data Catalog](#unified-data-catalog)
26+
- [Sensitivity Labeling](#sensitivity-labeling)
27+
- [Data Loss Prevention DLP](#data-loss-prevention-dlp)
28+
- [End-to-End Lineage](#end-to-end-lineage)
29+
- [Role-Based Governance](#role-based-governance)
30+
- [Trust & Endorsement](#trust--endorsement)
31+
- [Monitoring & Auditing](#monitoring--auditing)
32+
1633
</details>
1734

35+
## Unified Data Catalog
36+
37+
> Use the Microsoft Purview Unified Catalog to automatically register and view metadata for Fabric items. This helps users discover datasets, semantic models, and reports with full lineage and context. Ensure metadata scanning is enabled across all Fabric workspaces.
38+
39+
> [!IMPORTANT]
40+
> - **Admins** can configure scanning policies and permissions in the **Microsoft Purview governance portal**. <br/>
41+
> - Ensure that **Fabric is registered as a data source** in Purview. <br/>
42+
> - Use **role-based access control (RBAC)** to manage who can view or edit catalog metadata.
43+
44+
### 1. **Access the Purview Hub in Fabric**
45+
46+
- Go to the [Microsoft Fabric portal](https://app.fabric.microsoft.com/)
47+
- Click on ⚙️, select **“Purview hub”**.
48+
- This is your central place for managing governance, metadata, and data protection across Fabric.
49+
50+
<img width="550" alt="image" src="https://github.com/user-attachments/assets/9f22b062-051f-41b3-b480-4c109d332a57" />
51+
52+
https://github.com/user-attachments/assets/cf5f5a25-29bd-4b78-9d3c-c926026e13be
53+
54+
### 2. **Enable Metadata Scanning**
55+
56+
> Ensure that **metadata scanning is enabled** for all relevant Fabric workspaces.
57+
58+
1. **Configure tenant settings**:
59+
- In the [Fabric admin portal](https://app.fabric.microsoft.com/), go to **Tenant Settings**.
60+
61+
<img width="550" alt="image" src="https://github.com/user-attachments/assets/39bcb3a0-a794-4fd4-9bbb-6062b067bca2" />
62+
63+
- Enable detailed metadata scanning, and allow service principal access:
64+
65+
https://github.com/user-attachments/assets/276cf0bd-e388-4b59-89b3-5a07de214ae8
66+
67+
2.. **Run a scan**:
68+
- Use the **Purview portal** or **scanner APIs** to initiate a scan.
69+
- You can perform full, incremental, or scoped scans depending on your governance needs.
70+
71+
- This allows Purview to automatically discover and register items like:
72+
- Lakehouses
73+
- Dataflows
74+
- Semantic models
75+
- Reports
76+
- Scanning can be configured at the **workspace level** or **tenant level** by an admin.
77+
- **Where to monitor**: Once scanning is active, go to the **Purview hub in Fabric** to view registered items, lineage graphs, and metadata properties.
78+
79+
80+
### 3. **View and Explore the Unified Catalog**
81+
- Once scanning is active, go to the **“Data Catalog”** section within the Purview hub.
82+
- Here, you can:
83+
- Search for datasets, models, and reports.
84+
- View **metadata** such as schema, owner, last modified date.
85+
- See **data lineage**—how data flows from source to report.
86+
- Filter by sensitivity labels, endorsements, or domains.
87+
88+
### 4. **Use Lineage for Impact Analysis**
89+
- Click on any item to view its **lineage graph**.
90+
- This shows upstream and downstream dependencies (e.g., a semantic model feeding into multiple reports).
91+
- Use this to assess the impact of changes or troubleshoot data issues.
92+
93+
### 5. **Promote Discoverability**
94+
- Add **descriptions, tags, and endorsements** to important items.
95+
- This helps other users find and trust the right data assets.
96+
- Encourage data producers to maintain metadata hygiene.
97+
98+
## Sensitivity Labeling
99+
100+
> Apply sensitivity labels to all Fabric items (e.g., Lakehouses, semantic models, reports) using `Microsoft Purview Information Protection`. Labels persist across exports and help enforce data protection policies. Regularly audit label usage and ensure labels align with your data classification framework.
101+
102+
## Data Loss Prevention (DLP)
103+
104+
> Implement DLP policies for Power BI semantic models to prevent accidental data leaks. Define rules that restrict sharing or exporting sensitive data. Monitor DLP alerts and refine policies based on usage patterns.
105+
106+
## End-to-End Lineage
107+
108+
> Enable data lineage tracking to visualize how data flows from sources (e.g., OneLake, SQL, Cosmos DB) through transformations to reports. Use this to assess impact before making changes and to support compliance audits.
109+
110+
## Role-Based Governance
111+
112+
> Use tenant, domain, and workspace-level settings to delegate governance responsibilities. Platform admins should define global policies, while domain and workspace admins manage local configurations. This supports scalability and autonomy.
113+
114+
## Trust & Endorsement
115+
116+
> Encourage data producers to endorse trusted datasets and models. Use tags and descriptions to improve discoverability and promote reuse. This builds a culture of data trust and reduces duplication.
117+
118+
## Monitoring & Auditing
119+
120+
> Use the Purview hub in Fabric to monitor sensitivity labels, DLP activity, and data access. Regularly review audit logs to detect anomalies and ensure compliance with internal and external regulations.
121+
122+
123+
18124
<div align="center">
19125
<h3 style="color: #4CAF50;">Total Visitors</h3>
20126
<img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>

0 commit comments

Comments
 (0)