Skip to content

Commit 0f9e562

Browse files
Merge pull request #225878 from linda33wj/purview
Update supported capabilities
2 parents 87f87df + 8636dcd commit 0f9e562

File tree

1 file changed

+13
-2
lines changed

1 file changed

+13
-2
lines changed

articles/purview/register-scan-power-bi-tenant-cross-tenant.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: jingwang
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: how-to
9-
ms.date: 10/24/2022
9+
ms.date: 01/31/2023
1010
ms.custom: template-how-to, ignite-fall-2021
1111
---
1212

@@ -20,7 +20,18 @@ This article outlines how to register a Power BI tenant in a cross-tenant scenar
2020
|---|---|---|---|---|---|---|---|
2121
| [Yes](#deployment-checklist)| [Yes](#deployment-checklist)| Yes | No | No | No| [Yes](how-to-lineage-powerbi.md)| No|
2222

23-
For a list of metadata available for Power BI, see our [available metadata documentation](available-metadata.md).
23+
When scanning Power BI source, Microsoft Purview supports:
24+
25+
- Extracting technical metadata including:
26+
27+
- Workspaces
28+
- Dashboards
29+
- Reports
30+
- Datasets including the tables and columns
31+
- Dataflows
32+
- Datamarts
33+
34+
- Fetching static lineage on assets relationships among above Power BI artifacts as well as external data source assets. Learn more from [Power BI lineage](how-to-lineage-powerbi.md).
2435

2536
### Supported scenarios for Power BI scans
2637

0 commit comments

Comments
 (0)