You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/purview/register-scan-power-bi-tenant-cross-tenant.md
+17-4Lines changed: 17 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: csugunan
6
6
ms.service: purview
7
7
ms.subservice: purview-data-map
8
8
ms.topic: how-to
9
-
ms.date: 09/21/2022
9
+
ms.date: 09/22/2022
10
10
ms.custom: template-how-to, ignite-fall-2021
11
11
---
12
12
@@ -124,7 +124,7 @@ Use either of the following deployment checklists during the setup, or for troub
124
124
2.**Implicit grant and hybrid flows** > **ID tokens (used for implicit and hybrid flows)** is selected.
125
125
3.**Allow public client flows** is enabled.
126
126
127
-
1. If delegated authentication is used, in the Power BI Azure AD tenant validate the following Power BI admin user settings:
127
+
1. If delegated authentication is used, in the Power BI Azure AD tenant, validate the following Power BI admin user settings:
128
128
1. The user is assigned to the Power BI administrator role.
129
129
2. At least one [Power BI license](/power-bi/admin/service-admin-licensing-organization#subscription-license-types) is assigned to the user.
130
130
3. If the user is recently created, sign in with the user at least once, to make sure that the password is reset successfully, and the user can successfully initiate the session.
@@ -337,9 +337,20 @@ To create and run a new scan by using the self-hosted integration runtime, perfo
337
337
338
338
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault.png" alt-text="Screenshot of the instance of Azure Key Vault.":::
339
339
340
-
1. Enter a name for the secret. For **Value**, type the newly created password for the Azure AD user. Select **Create** to complete.
340
+
1. Enter a name for the secret. For **Value**, type the newly created secret for the App registration. Select **Create** to complete.
341
341
342
-
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault-secret.png" alt-text="Screenshot that shows how to generate a secret in Azure Key Vault.":::
342
+
343
+
2. Under **Certificates & secrets**, create a new secret and save it securely for next steps.
344
+
345
+
3. In Azure portal, navigate to your Azure key vault.
346
+
347
+
4. Select **Settings** > **Secrets** and select **+ Generate/Import**.
348
+
349
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault.png" alt-text="Screenshot how to navigate to Azure Key Vault.":::
350
+
351
+
5. Enter a name for the secret and for **Value**, type the newly created secret for the App registration. Select **Create** to complete.
352
+
353
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault-secret-spn.png" alt-text="Screenshot how to generate an Azure Key Vault secret for SPN.":::
343
354
344
355
1. If your key vault isn't connected to Microsoft Purview yet, you need to [create a new key vault connection](manage-credentials.md#create-azure-key-vaults-connections-in-your-microsoft-purview-account).
345
356
@@ -365,6 +376,8 @@ To create and run a new scan by using the self-hosted integration runtime, perfo
365
376
-**Tenant ID**: Your Power BI tenant ID
366
377
-**Client ID**: Use Service Principal Client ID (App ID) you created earlier
367
378
379
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-scan-spn-authentication.png" alt-text="Screenshot of the new credential menu, showing Power BI credential for SPN with all required values supplied.":::
380
+
368
381
1. Select **Test connection** before continuing to the next steps.
369
382
370
383
If the test fails, select **View Report** to see the detailed status and troubleshoot the problem:
Copy file name to clipboardExpand all lines: articles/purview/register-scan-power-bi-tenant.md
+35-18Lines changed: 35 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: csugunan
6
6
ms.service: purview
7
7
ms.subservice: purview-data-map
8
8
ms.topic: how-to
9
-
ms.date: 09/21/2022
9
+
ms.date: 09/22/2022
10
10
ms.custom: template-how-to, ignite-fall-2021
11
11
---
12
12
@@ -222,7 +222,7 @@ In Azure Active Directory Tenant, where Power BI tenant is located:
222
222
223
223
:::image type="content" source="./media/setup-power-bi-scan-PowerShell/add-group-member.png" alt-text="Screenshot of how to add the catalog's managed instance to group.":::
224
224
225
-
- If you are using **delegated authentication** or **service principal** as authentication method, add your **service princial** to this security group. Select **Members**, then select **+ Add members**.
225
+
- If you are using **delegated authentication** or **service principal** as authentication method, add your **service principal** to this security group. Select **Members**, then select **+ Add members**.
226
226
227
227
5. Search for your Microsoft Purview managed identity or service principal and select it.
228
228
@@ -305,7 +305,7 @@ For more information about Microsoft Purview network settings, see [Use private
305
305
306
306
To create and run a new scan, do the following:
307
307
308
-
1.Create an App Registration in your Azure Active Directory tenant. Provide a web URL in the **Redirect URI**. Take note of Client ID(App ID).
308
+
1.In the [Azure portal](https://portal.azure.com), select **Azure Active Directory** and create an App Registration in the tenant. Provide a web URL in the **Redirect URI**. Take note of Client ID(App ID).
309
309
310
310
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-create-service-principle.png" alt-text="Screenshot how to create a Service principle.":::
311
311
@@ -319,44 +319,60 @@ To create and run a new scan, do the following:
319
319
320
320
1. Under **Advanced settings**, enable **Allow Public client flows**.
321
321
322
-
2.In the Microsoft Purview Studio, navigate to the **Data map** in the left menu.
322
+
2.Under **Certificates & secrets**, create a new secret and save it securely for next steps.
323
323
324
-
1. Navigate to **Sources**.
324
+
3. In Azure portal, navigate to your Azure key vault.
325
325
326
-
1. Select the registered Power BI source.
326
+
4. Select **Settings** > **Secrets** and select **+ Generate/Import**.
327
327
328
-
1. Select **+ New scan**.
328
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault.png" alt-text="Screenshot how to navigate to Azure Key Vault.":::
329
329
330
-
1. Give your scan a name. Then select the option to include or exclude the personal workspaces.
330
+
5. Enter a name for the secret and for **Value**, type the newly created secret for the App registration. Select **Create** to complete.
331
+
332
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-key-vault-secret-spn.png" alt-text="Screenshot how to generate an Azure Key Vault secret for SPN.":::
333
+
334
+
6. If your key vault isn't connected to Microsoft Purview yet, you'll need to [create a new key vault connection](manage-credentials.md#create-azure-key-vaults-connections-in-your-microsoft-purview-account)
335
+
336
+
7. In the Microsoft Purview Studio, navigate to the **Data map** in the left menu.
337
+
338
+
8. Navigate to **Sources**.
339
+
340
+
9. Select the registered Power BI source.
341
+
342
+
10. Select **+ New scan**.
343
+
344
+
11. Give your scan a name. Then select the option to include or exclude the personal workspaces.
331
345
332
346
>[!Note]
333
347
> Switching the configuration of a scan to include or exclude a personal workspace will trigger a full scan of Power BI source.
334
348
335
-
1. Select your self-hosted integration runtime from the drop-down list.
349
+
12. Select your self-hosted integration runtime from the drop-down list.
336
350
337
351
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-scan-shir.png" alt-text="Image showing Power BI scan setup using SHIR for same tenant.":::
338
352
339
-
1. For the **Credential**, select **service principal** and select **+ New** to create a new credential.
353
+
13. For the **Credential**, select **service principal** and select **+ New** to create a new credential.
340
354
341
-
1. Create a new credential and provide required parameters:
355
+
14. Create a new credential and provide required parameters:
342
356
343
357
-**Name**: Provide a unique name for credential
344
358
-**Authentication method**: Service principal
345
359
-**Tenant ID**: Your Power BI tenant ID
346
360
-**Client ID**: Use Service Principal Client ID (App ID) you created earlier
347
-
348
-
1. Select **Test Connection** before continuing to next steps. If **Test Connection** failed, select **View Report** to see the detailed status and troubleshoot the problem
361
+
362
+
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-scan-spn-authentication.png" alt-text="Screenshot of the new credential menu, showing Power BI credential for SPN with all required values supplied.":::
363
+
364
+
15. Select **Test Connection** before continuing to next steps. If **Test Connection** failed, select **View Report** to see the detailed status and troubleshoot the problem
349
365
1. Access - Failed status means the user authentication failed. Scans using managed identity will always pass because no user authentication required.
350
366
2. Assets (+ lineage) - Failed status means the Microsoft Purview - Power BI authorization has failed. Make sure the Microsoft Purview managed identity is added to the security group associated in Power BI admin portal.
351
367
3. Detailed metadata (Enhanced) - Failed status means the Power BI admin portal is disabled for the following setting - **Enhance admin APIs responses with detailed metadata**
352
368
353
369
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-test-connection-status-report.png" alt-text="Screenshot of test connection status report page.":::
354
370
355
-
1. Set up a scan trigger. Your options are **Recurring**, and **Once**.
371
+
16. Set up a scan trigger. Your options are **Recurring**, and **Once**.
356
372
357
373
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/scan-trigger.png" alt-text="Screenshot of the Microsoft Purview scan scheduler.":::
358
374
359
-
1. On **Review new scan**, select **Save and run** to launch your scan.
375
+
17. On **Review new scan**, select **Save and run** to launch your scan.
360
376
361
377
### Create scan for same-tenant using self-hosted IR with delegated authentication
362
378
@@ -424,20 +440,21 @@ To create and run a new scan, do the following:
424
440
-**Client ID**: Use Service Principal Client ID (App ID) you created earlier
425
441
-**User name**: Provide the username of Power BI Administrator you created earlier
426
442
-**Password**: Select the appropriate Key vault connection and the **Secret name** where the Power BI account password was saved earlier.
443
+
427
444
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-scan-delegated-authentication.png" alt-text="Screenshot of the new credential menu, showing Power B I credential with all required values supplied.":::
428
445
429
-
1. Select **Test Connection** before continuing to next steps. If **Test Connection** failed, select **View Report** to see the detailed status and troubleshoot the problem
446
+
2. Select **Test Connection** before continuing to next steps. If **Test Connection** failed, select **View Report** to see the detailed status and troubleshoot the problem
430
447
1. Access - Failed status means the user authentication failed. Scans using managed identity will always pass because no user authentication required.
431
448
2. Assets (+ lineage) - Failed status means the Microsoft Purview - Power BI authorization has failed. Make sure the Microsoft Purview managed identity is added to the security group associated in Power BI admin portal.
432
449
3. Detailed metadata (Enhanced) - Failed status means the Power BI admin portal is disabled for the following setting - **Enhance admin APIs responses with detailed metadata**
433
450
434
451
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/power-bi-test-connection-status-report.png" alt-text="Screenshot of test connection status report page.":::
435
452
436
-
1. Set up a scan trigger. Your options are **Recurring**, and **Once**.
453
+
3. Set up a scan trigger. Your options are **Recurring**, and **Once**.
437
454
438
455
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/scan-trigger.png" alt-text="Screenshot of the Microsoft Purview scan scheduler.":::
439
456
440
-
1. On **Review new scan**, select **Save and run** to launch your scan.
457
+
4. On **Review new scan**, select **Save and run** to launch your scan.
441
458
442
459
:::image type="content" source="media/setup-power-bi-scan-catalog-portal/save-run-power-bi-scan.png" alt-text="Screenshot of Save and run Power BI source.":::
0 commit comments