Skip to content

Commit 90393ba

Browse files
BCS2022BCS2022
authored
Merge pull request #204645 from whhender/pbi-metadata-page
Power BI metadata reference page
2 parents f19f273 + e79e44e commit 90393ba

File tree

4 files changed

+88
-8
lines changed

4 files changed

+88
-8
lines changed

‎articles/purview/available-metadata.md

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
---
2+
title: Available metadata for Power BI in the Microsoft Purview governance portal
3+
description: This reference article provides a list of metadata that is available for a Power BI tenant in the Microsoft Purview governance portal.
4+
author: chanuengg
5+
ms.author: csugunan
6+
ms.service: purview
7+
ms.subservice: purview-data-catalog
8+
ms.topic: reference
9+
ms.date: 08/02/2022
10+
---
11+
12+
# Available metadata
13+
14+
This article has a list of the metadata that is available for a Power BI tenant in the Microsoft Purview governance portal.
15+
16+
## Power BI
17+
18+
| Metadata | Population method | Source of truth | Asset type | Editable | Upstream metadata |
19+
|-----------------------|-------------------|-------------------|--------------------|----------|---------------------------------|
20+
| Classification | Manual | Microsoft Purview | All types | Yes | N/A |
21+
| Sensitivity Labels | Automatic | Microsoft Purview | All types | No | |
22+
| Glossary terms | Manual | Microsoft Purview | All types | Yes | N/A |
23+
| Collection | Automatic | Microsoft Purview | All types | | N/A |
24+
| Hierarchy | Automatic | Microsoft Purview | All types | No | N/A |
25+
| qualifiedName | Automatic | Microsoft Purview | All types | No | |
26+
| Asset Description | Automatic/Manual* | Microsoft Purview | All types | Yes | N/A |
27+
| Contacts - Expert | Manual | Microsoft Purview | All types | Yes | N/A |
28+
| Contacts - Owner | Manual | Microsoft Purview | All types | Yes | N/A |
29+
| name | Automatic | Power BI | Power BI Dashboard | Yes | dashboard.DisplayName |
30+
| isReadOnly | Automatic | Power BI | Power BI Dashboard | No | dashboard.IsReadOnly |
31+
| EmbedUrl | Automatic | Power BI | Power BI Dashboard | No | dashboard.EmbedUrl |
32+
| tileNames | Automatic | Power BI | Power BI Dashboard | No | TileTitles |
33+
| Lineage | Automatic | Power BI | Power BI Dashboard | No | N/A |
34+
| name | Automatic | Power BI | Power BI dataflow | Yes | dataflow.Name |
35+
| configured by | Automatic | Power BI | Power BI dataflow | No | dataflow.ConfiguredBy |
36+
| description | Automatic | Power BI | Power BI dataflow | Yes | dataflow.Description |
37+
| ModelUrl | Automatic | Power BI | Power BI dataflow | No | dataflow.ModelUrl |
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+
| name | Automatic | Power BI | Power BI Dataset | Yes | dataset.Name |
42+
| IsRefreshable | Automatic | Power BI | Power BI Dataset | No | dataset.IsRefreshable |
43+
| configuredBy | Automatic | Power BI | Power BI Dataset | No | dataset.ConfiguredBy |
44+
| contentProviderType | Automatic | Power BI | Power BI Dataset | No | dataset.ContentProviderType |
45+
| createdDate | Automatic | Power BI | Power BI Dataset | No | dataset.CreatedDateTime |
46+
| targetStorageMode | Automatic | Power BI | Power BI Dataset | No | dataset.TargetStorageMode |
47+
| Schema | Automatic/Manual | Power BI | Power BI Dataset | | |
48+
| Lineage | Automatic | Microsoft Purview | Power BI Dataset | No | |
49+
| description | Automatic | Power BI | Power BI Dataset | Yes | dataset.Description |
50+
| Endorsement | Automatic | Power BI | Power BI Dataset | No | dataset.EndorsementDetails |
51+
| name | Automatic | Power BI | Power BI Report | Yes | report.Name |
52+
| description | Automatic | Power BI | Power BI Report | Yes | report.Description |
53+
| createdDateTime | Automatic | Power BI | Power BI Report | No | report.CreatedDateTime |
54+
| WebUrl | Automatic | Power BI | Power BI Report | No | report.WebUrl |
55+
| EmbedUrl | Automatic | Power BI | Power BI Report | No | report.EmbedUrl |
56+
| PBIDatasetId | Automatic | Power BI | Power BI Report | No | report.DatasetId; |
57+
| modifiedBy | Automatic | Power BI | Power BI Report | No | report.ModifiedBy |
58+
| modifiedDateTime | Automatic | Power BI | Power BI Report | No | report.ModifiedDateTime |
59+
| reportType | Automatic | Power BI | Power BI Report | No | report.ReportType |
60+
| Endorsement | Automatic | Power BI | Power BI Report | No | report.EndorsementDetails |
61+
| Lineage | Automatic | Microsoft Purview | Power BI Report | No | N/A |
62+
| name | Automatic | Power BI | Power BI Workspace | Yes | workspace.Name |
63+
| Description | Automatic | Power BI | Power BI Workspace | Yes | workspace.Description |
64+
| state | Automatic | Power BI | Power BI Workspace | No | workspace.State |
65+
| type | Automatic | Power BI | Power BI Workspace | No | ResourceType.Workspace |
66+
| IsReadOnly | Automatic | Power BI | Power BI Workspace | No | workspace.IsReadOnly |
67+
| IsOnDedicatedCapacity | Automatic | Power BI | Power BI Workspace | No | workspace.IsOnDedicatedCapacity |
68+
69+
70+
## Next steps
71+
72+
- [Register and scan a Power BI tenant](register-scan-power-bi-tenant.md)
73+
- [Register and scan Power BI across tenants](register-scan-power-bi-tenant-cross-tenant.md)
74+
- [Register and scan Power BI troubleshooting](register-scan-power-bi-tenant-troubleshoot.md)

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

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ 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).
24+
2325
### Supported scenarios for Power BI scans
2426

2527
|**Scenario** |**Microsoft Purview public access** |**Power BI public access** | **Runtime option** | **Authentication option** | **Deployment checklist** |
@@ -62,7 +64,7 @@ Use either of the following deployment checklists during the setup, or for troub
6264

6365
1. Check your instance of Azure Key Vault to make sure:
6466
1. There are no typos in the password.
65-
2. Microsoft Purview managed identity has get and list access to secrets.
67+
2. Microsoft Purview managed identity has **get** and **list** access to secrets.
6668

6769
1. Review your credential to validate that the:
6870
1. Client ID matches the _Application (Client) ID_ of the app registration.
@@ -101,7 +103,7 @@ Use either of the following deployment checklists during the setup, or for troub
101103

102104
1. Check your instance of Azure Key Vault to make sure:
103105
1. There are no typos in the password.
104-
2. Microsoft Purview managed identity has get and list access to secrets.
106+
2. Microsoft Purview managed identity has **get** and **list** access to secrets.
105107

106108
1. Review your credential to validate that the:
107109
1. Client ID matches the _Application (Client) ID_ of the app registration.
@@ -204,7 +206,7 @@ To create and run a new scan by using the Azure runtime, perform the following s
204206
1. Give your scan a name. Then select the option to include or exclude the personal workspaces.
205207

206208
> [!Note]
207-
> If you switch the configuration of a scan to include or exclude a personal workspace, you trigger a full scan of the PowerBI source.
209+
> If you switch the configuration of a scan to include or exclude a personal workspace, you trigger a full scan of the Power BI source.
208210
209211
1. Select **Azure AutoResolveIntegrationRuntime** from the dropdown list.
210212

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

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,8 @@ 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+
For a list of metadata available for Power BI, see our [available metadata documentation](available-metadata.md).
24+
2325
### Supported scenarios for Power BI scans
2426

2527
|**Scenarios** |**Microsoft Purview public access allowed/denied** |**Power BI public access allowed /denied** | **Runtime option** | **Authentication option** | **Deployment checklist** |
@@ -61,7 +63,7 @@ Use any of the following deployment checklists during the setup or for troublesh
6163

6264
1. Make sure Power BI and Microsoft Purview accounts are in the same tenant.
6365
1. Make sure Power BI tenant ID is entered correctly during the registration.
64-
1. Make sure your [PowerBI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
66+
1. Make sure your [Power BI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
6567
1. From Azure portal, validate if Microsoft Purview account Network is set to public access.
6668
1. From Power BI tenant Admin Portal, make sure Power BI tenant is configured to allow public network.
6769
1. In Azure Active Directory tenant, create a security group.
@@ -73,7 +75,7 @@ Use any of the following deployment checklists during the setup or for troublesh
7375

7476
1. Make sure Power BI and Microsoft Purview accounts are in the same tenant.
7577
1. Make sure Power BI tenant ID is entered correctly during the registration.
76-
1. Make sure your [PowerBI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
78+
1. Make sure your [Power BI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
7779
1. From Azure portal, validate if Microsoft Purview account Network is set to public access.
7880
1. From Power BI tenant Admin Portal, make sure Power BI tenant is configured to allow public network.
7981
1. Check your Azure Key Vault to make sure:
@@ -105,7 +107,7 @@ Use any of the following deployment checklists during the setup or for troublesh
105107

106108
1. Make sure Power BI and Microsoft Purview accounts are in the same tenant.
107109
1. Make sure Power BI tenant ID is entered correctly during the registration.
108-
1. Make sure your [PowerBI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
110+
1. Make sure your [Power BI Metadata model is up to date by enabling metadata scanning.](/power-bi/admin/service-admin-metadata-scanning-setup#enable-tenant-settings-for-metadata-scanning)
109111
1. Check your Azure Key Vault to make sure:
110112
1. There are no typos in the password.
111113
2. Microsoft Purview Managed Identity has get/list access to secrets.
@@ -242,7 +244,7 @@ To create and run a new scan, do the following:
242244
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-scan-setup.png" alt-text="Image showing Power BI scan setup.":::
243245

244246
> [!Note]
245-
> Switching the configuration of a scan to include or exclude a personal workspace will trigger a full scan of PowerBI source.
247+
> Switching the configuration of a scan to include or exclude a personal workspace will trigger a full scan of Power BI source.
246248
247249
3. Select **Test Connection** before continuing to next steps. If **Test Connection** failed, select **View Report** to see the detailed status and troubleshoot the problem.
248250
1. Access - Failed status means the user authentication failed. Scans using managed identity will always pass because no user authentication required.
@@ -310,7 +312,7 @@ To create and run a new scan, do the following:
310312
1. Give your scan a name. Then select the option to include or exclude the personal workspaces.
311313

312314
>[!Note]
313-
> Switching the configuration of a scan to include or exclude a personal workspace will trigger a full scan of PowerBI source.
315+
> Switching the configuration of a scan to include or exclude a personal workspace will trigger a full scan of Power BI source.
314316
315317
1. Select your self-hosted integration runtime from the drop-down list.
316318

‎articles/purview/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -383,6 +383,8 @@ items:
383383
items:
384384
- name: Product glossary reference
385385
href: reference-azure-purview-glossary.md
386+
- name: Available source metadata
387+
href: available-metadata.md
386388
- name: Supported browsers
387389
href: supported-browsers.md
388390
- name: Supported classifications

0 commit comments

Comments
 (0)