Skip to content

Commit e822862

Browse files
linda33wjlinda33wj
committed
Update supported capabilities
1 parent f427dd8 commit e822862

6 files changed

+78
-36
lines changed

‎articles/purview/available-metadata.md

Lines changed: 31 additions & 21 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-catalog
88
ms.topic: reference
9-
ms.date: 12/14/2022
9+
ms.date: 01/31/2023
1010
---
1111

1212
# Available metadata
@@ -20,54 +20,64 @@ This article has a list of the metadata that is available for a Power BI tenant
2020
| Classification | Manual | Microsoft Purview | All types | Yes | N/A |
2121
| Sensitivity Labels | Automatic | Microsoft Purview | All types | No | |
2222
| Glossary terms | Manual | Microsoft Purview | All types | Yes | N/A |
23-
| Collection | Automatic | Microsoft Purview | All types | | N/A |
23+
| Collection | Automatic | Microsoft Purview | All types | Yes | N/A |
2424
| Hierarchy | Automatic | Microsoft Purview | All types | No | N/A |
25-
| qualifiedName | Automatic | Microsoft Purview | All types | No | |
25+
| qualifiedName | Automatic | Microsoft Purview | All types | No | N/A |
2626
| Asset Description | Automatic/Manual* | Microsoft Purview | All types | Yes | N/A |
2727
| Contacts - Expert | Manual | Microsoft Purview | All types | Yes | N/A |
2828
| Contacts - Owner | Manual | Microsoft Purview | All types | Yes | N/A |
2929
| name | Automatic | Power BI | Power BI Dashboard | Yes | dashboard.DisplayName |
3030
| isReadOnly | Automatic | Power BI | Power BI Dashboard | No | dashboard.IsReadOnly |
31-
| EmbedUrl | Automatic | Power BI | Power BI Dashboard | No | dashboard.EmbedUrl |
31+
| embedUrl | Automatic | Power BI | Power BI Dashboard | No | dashboard.EmbedUrl |
3232
| tileNames | Automatic | Power BI | Power BI Dashboard | No | TileTitles |
33-
| Lineage | Automatic | Power BI | Power BI Dashboard | No | N/A |
3433
| users | Automatic | Power BI | Power BI Dashboard | No | dashboard.Users |
35-
| name | Automatic | Power BI | Power BI dataflow | Yes | dataflow.Name |
36-
| configured by | Automatic | Power BI | Power BI dataflow | No | dataflow.ConfiguredBy |
37-
| description | Automatic | Power BI | Power BI dataflow | Yes | dataflow.Description |
38-
| ModifiedBy | Automatic | Power BI | Power BI dataflow | No | dataflow.ModifiedBy |
39-
| ModifiedDateTime | Automatic | Power BI | Power BI dataflow | No | dataflow.ModifiedDateTime |
40-
| Endorsement | Automatic | Power BI | Power BI dataflow | No | dataflow.EndorsementDetails |
41-
| users | Automatic | Power BI | Power BI dataflow | No | dataflow.Users |
34+
| Lineage | Automatic | Power BI | Power BI Dashboard | No | N/A |
35+
| name | Automatic | Power BI | Power BI Dataflow | Yes | dataflow.Name |
36+
| description | Automatic | Power BI | Power BI Dataflow | Yes | dataflow.Description |
37+
| configuredBy | Automatic | Power BI | Power BI Dataflow | No | dataflow.ConfiguredBy |
38+
| modifiedBy | Automatic | Power BI | Power BI Dataflow | No | dataflow.ModifiedBy |
39+
| modifiedDateTime | Automatic | Power BI | Power BI Dataflow | No | dataflow.ModifiedDateTime |
40+
| Endorsement | Automatic | Power BI | Power BI Dataflow | No | dataflow.EndorsementDetails |
41+
| users | Automatic | Power BI | Power BI Dataflow | No | dataflow.Users |
42+
| Lineage | Automatic | Microsoft Purview | Power BI Dataflow | No | |
43+
| name | Automatic | Power BI | Power BI Datamart | Yes | datamart.Name |
44+
| description | Automatic | Power BI | Power BI Datamart | Yes | datamart.Description |
45+
| configuredBy | Automatic | Power BI | Power BI Datamart | No | datamart.ConfiguredBy |
46+
| modifiedBy | Automatic | Power BI | Power BI Datamart | No | datamart.ModifiedBy |
47+
| modifiedDateTime | Automatic | Power BI | Power BI Datamart | No | datamart.ModifiedDateTime |
48+
| Endorsement | Automatic | Power BI | Power BI Datamart | No | datamart.EndorsementDetails |
49+
| users | Automatic | Power BI | Power BI Datamart | No | datamart.Users |
50+
| Lineage | Automatic | Microsoft Purview | Power BI Datamart | No | |
4251
| name | Automatic | Power BI | Power BI Dataset | Yes | dataset.Name |
43-
| IsRefreshable | Automatic | Power BI | Power BI Dataset | No | dataset.IsRefreshable |
52+
| description | Automatic | Power BI | Power BI Dataset | Yes | dataset.Description |
53+
| isRefreshable | Automatic | Power BI | Power BI Dataset | No | dataset.IsRefreshable |
4454
| configuredBy | Automatic | Power BI | Power BI Dataset | No | dataset.ConfiguredBy |
4555
| contentProviderType | Automatic | Power BI | Power BI Dataset | No | dataset.ContentProviderType |
4656
| createdDate | Automatic | Power BI | Power BI Dataset | No | dataset.CreatedDateTime |
4757
| targetStorageMode | Automatic | Power BI | Power BI Dataset | No | dataset.TargetStorageMode |
48-
| Schema | Automatic/Manual | Power BI | Power BI Dataset | | |
49-
| Lineage | Automatic | Microsoft Purview | Power BI Dataset | No | |
50-
| description | Automatic | Power BI | Power BI Dataset | Yes | dataset.Description |
58+
| Schema | Automatic/Manual | Power BI | Power BI Dataset | | tables & columns |
5159
| Endorsement | Automatic | Power BI | Power BI Dataset | No | dataset.EndorsementDetails |
5260
| users | Automatic | Power BI | Power BI Dataset | No | dataset.Users |
61+
| Lineage | Automatic | Microsoft Purview | Power BI Dataset | No | |
5362
| name | Automatic | Power BI | Power BI Report | Yes | report.Name |
5463
| description | Automatic | Power BI | Power BI Report | Yes | report.Description |
5564
| createdDateTime | Automatic | Power BI | Power BI Report | No | report.CreatedDateTime |
56-
| WebUrl | Automatic | Power BI | Power BI Report | No | report.WebUrl |
57-
| EmbedUrl | Automatic | Power BI | Power BI Report | No | report.EmbedUrl |
58-
| PBIDatasetId | Automatic | Power BI | Power BI Report | No | report.DatasetId; |
65+
| webUrl | Automatic | Power BI | Power BI Report | No | report.WebUrl |
66+
| embedUrl | Automatic | Power BI | Power BI Report | No | report.EmbedUrl |
67+
| PBIDatasetId | Automatic | Power BI | Power BI Report | No | report.DatasetId |
5968
| modifiedBy | Automatic | Power BI | Power BI Report | No | report.ModifiedBy |
6069
| modifiedDateTime | Automatic | Power BI | Power BI Report | No | report.ModifiedDateTime |
6170
| reportType | Automatic | Power BI | Power BI Report | No | report.ReportType |
6271
| Endorsement | Automatic | Power BI | Power BI Report | No | report.EndorsementDetails |
72+
| users | Automatic | Power BI | Power BI Report | No | report.Users |
6373
| Lineage | Automatic | Microsoft Purview | Power BI Report | No | N/A |
64-
| users | Automatic | Power BI | Power BI Report | No | workspace.Users |
6574
| name | Automatic | Power BI | Power BI Workspace | Yes | workspace.Name |
66-
| Description | Automatic | Power BI | Power BI Workspace | Yes | workspace.Description |
75+
| description | Automatic | Power BI | Power BI Workspace | Yes | workspace.Description |
6776
| state | Automatic | Power BI | Power BI Workspace | No | workspace.State |
6877
| type | Automatic | Power BI | Power BI Workspace | No | ResourceType.Workspace |
6978
| IsReadOnly | Automatic | Power BI | Power BI Workspace | No | workspace.IsReadOnly |
7079
| IsOnDedicatedCapacity | Automatic | Power BI | Power BI Workspace | No | workspace.IsOnDedicatedCapacity |
80+
| users | Automatic | Power BI | Power BI Workspace | No | workspace.Users |
7181

7282

7383
## Next steps

‎articles/purview/how-to-lineage-powerbi.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,15 +29,14 @@ This article elaborates on the data lineage aspects of Power BI source in Micros
2929

3030
## Power BI artifacts in Microsoft Purview
3131

32-
Once the [scan of your Power BI](../purview/register-scan-power-bi-tenant.md) is complete, following Power BI artifacts will be inventoried in Microsoft Purview
32+
Once the [scan of your Power BI](../purview/register-scan-power-bi-tenant.md) is complete, following Power BI artifacts will be inventoried in Microsoft Purview:
3333

34-
* Capacity
3534
* Workspaces
36-
* Dataflow
37-
* Dataset
38-
* Report
39-
* Dashboard
40-
* Datamart
35+
* Dashboards
36+
* Reports
37+
* Datasets
38+
* Dataflows
39+
* Datamarts
4140

4241
The workspace artifacts will show lineage of Dataflow -> Dataset -> Report -> Dashboard.
4342

‎articles/purview/register-scan-adls-gen2.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,20 @@ This article outlines the process to register and govern an Azure Data Lake Stor
1616

1717
|**Metadata Extraction**| **Full Scan** |**Incremental Scan**|**Scoped Scan**|**Classification**|**Access Policy**|**Lineage**|**Data Sharing**|
1818
|---|---|---|---|---|---|---|---|
19-
| [Yes](#register) | [Yes](#scan)|[Yes](#scan) | [Yes](#scan)|[Yes](#scan)| [Yes (preview)](#access-policy) | Limited** |[Yes](#data-sharing)|
19+
| [Yes](#register) | [Yes](#scan)|[Yes](#scan) | [Yes](#scan)|[Yes](#scan)| [Yes (preview)](#access-policy) | Limited* |[Yes](#data-sharing)|
2020

21+
\* *Lineage is supported if dataset is used as a source/sink in [Data Factory](how-to-link-azure-data-factory.md) or [Synapse pipeline](how-to-lineage-azure-synapse-analytics.md).*
2122

22-
\** Lineage is supported if dataset is used as a source/sink in [Data Factory Copy activity](how-to-link-azure-data-factory.md)
23+
When scanning Azure Data Lake Storage Gen2 source, Microsoft Purview supports extracting technical metadata including:
24+
25+
- Storage account
26+
- Data Lake Storage Gen2 Service
27+
- File system (container)
28+
- Folders
29+
- Files
30+
- Resource sets
31+
32+
When setting up scan, you can choose to scan the entire ADLS Gen2 or selective folders. Learn about the supported file format [here](microsoft-purview-connector-overview.md#file-types-supported-for-scanning).
2333

2434
## Prerequisites
2535

‎articles/purview/register-scan-azure-data-explorer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ This article outlines how to register Azure Data Explorer, and how to authentica
1919

2020
|**Metadata Extraction**| **Full Scan** |**Incremental Scan**|**Scoped Scan**|**Classification**|**Access Policy**|**Lineage**|**Data Sharing**|
2121
|---|---|---|---|---|---|---|---|
22-
| [Yes](#register) | [Yes](#scan) | [Yes](#scan) | [Yes](#scan)| [Yes](#scan)| No | Limited** | No |
22+
| [Yes](#register) | [Yes](#scan) | [Yes](#scan) | [Yes](#scan)| [Yes](#scan)| No | Limited* | No |
2323

24-
\** Lineage is supported if dataset is used as a source/sink in [Data Factory Copy activity](how-to-link-azure-data-factory.md)
24+
\* *Lineage is supported if dataset is used as a sink in [Data Factory](how-to-link-azure-data-factory.md) or [Synapse pipeline](how-to-lineage-azure-synapse-analytics.md).*
2525

2626
## Prerequisites
2727

‎articles/purview/register-scan-azure-synapse-analytics.md

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

@@ -21,9 +21,19 @@ This article outlines how to register dedicated SQL pools (formerly SQL DW), and
2121

2222
|**Metadata Extraction**| **Full Scan** |**Incremental Scan**|**Scoped Scan**|**Classification**|**Access Policy**|**Lineage**|**Data Sharing**|
2323
|---|---|---|---|---|---|---|---|
24-
| [Yes](#register) | [Yes](#scan)| [Yes](#scan)| [Yes](#scan)| [Yes](#scan)| No | Limited** | No |
24+
| [Yes](#register) | [Yes](#scan)| [Yes](#scan)| [Yes](#scan)| [Yes](#scan)| No | Limited* | No |
2525

26-
\** Lineage is supported if dataset is used as a source/sink in [Data Factory Copy activity](how-to-link-azure-data-factory.md)
26+
\* *Lineage is supported if dataset is used as a source/sink in [Data Factory](how-to-link-azure-data-factory.md) or [Synapse pipeline](how-to-lineage-azure-synapse-analytics.md).*
27+
28+
When scanning dedicated SQL pool (formerly SQL DW) source, Microsoft Purview supports extracting technical metadata including:
29+
30+
- Server
31+
- Dedicated SQL pools
32+
- Schemas
33+
- Tables including columns
34+
- Views including columns
35+
36+
When setting up the scan, you can further scope it after providing the dedicated SQL pool name by selecting tables and views as needed.
2737

2838
### Known limitations
2939

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

Lines changed: 14 additions & 1 deletion
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: 11/03/2022
9+
ms.date: 01/31/2023
1010
ms.custom: template-how-to, ignite-fall-2021
1111
---
1212

@@ -20,6 +20,19 @@ This article outlines how to register a Power BI tenant in a **same-tenant scena
2020
|---|---|---|---|---|---|---|---|
2121
| [Yes](#deployment-checklist)| [Yes](#deployment-checklist)| Yes | No | No | No| [Yes](how-to-lineage-powerbi.md)| No |
2222

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).
35+
2336
For a list of metadata available for Power BI, see our [available metadata documentation](available-metadata.md).
2437

2538
### Supported scenarios for Power BI scans

0 commit comments

Comments
 (0)