Skip to content

Commit 593e1bd

Browse files
authored
Merge pull request #173874 from linda33wj/master
Add Purview connection monitoring experience in ADF
2 parents 7d2d318 + 963b653 commit 593e1bd

File tree

2 files changed

+14
-3
lines changed

2 files changed

+14
-3
lines changed

articles/data-factory/connect-data-factory-to-azure-purview.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: linda33wj
66
ms.service: data-factory
77
ms.topic: conceptual
88
ms.custom: seo-lt-2019, references_regions
9-
ms.date: 09/15/2021
9+
ms.date: 09/27/2021
1010
---
1111

1212
# Connect Data Factory to Azure Purview (Preview)
@@ -75,9 +75,20 @@ Data factory's managed identity is used to authenticate lineage push operations
7575

7676
When connecting data factory to Purview on authoring UI, ADF tries to add such role assignment automatically. If you have Azure built-in **Owner** or **User Access Administrator** role on the Purview account, this operation is done successfully.
7777

78-
You may see below warning if you have the privilege to read Purview role assignment information and the needed role is not granted. To make sure the connection is properly set for the pipeline lineage push, go to your Purview account and check if **Purview Data Curator** role is granted to the data factory's managed identity. If not, manually add the role assignment.
78+
## Monitor Purview connection
7979

80-
:::image type="content" source="./media/data-factory-purview/register-purview-account-warning.png" alt-text="Screenshot for warning of registering a Purview account.":::
80+
Once you connect the data factory to a Purview account, you see the following page with details on the enabled integration capabilities.
81+
82+
:::image type="content" source="./media/data-factory-purview/monitor-purview-connection-status.png" alt-text="Screenshot for monitoring the integration status between Azure Data Factory and Purview.":::
83+
84+
For **Data Lineage - Pipeline**, you may see one of below status:
85+
86+
- **Connected**: The data factory is successfully connected to the Purview account. Note this indicates data factory is associated with a Purview account and has permission to push lineage to it. If your Purview account is protected by firewall, you also need to make sure the integration runtime used to execute the activities and conduct lineage push can reach the Purview account. Learn more from [Access a secured Azure Purview account from Azure Data Factory](how-to-access-secured-purview-account.md).
87+
- **Disconnected**: The data factory cannot push lineage to Purview because Purview Data Curator role is not granted to data factory's managed identity. To fix this issue, go to your Purview account to check the role assignments, and manually grant the role as needed. Learn more from [Set up authentication](#set-up-authentication) section.
88+
- **Unknown**: Data Factory cannot check the status. Possible reasons are:
89+
90+
- Cannot reach the Purview account from your current network because the account is protected by firewall. You can launch the ADF UI from a private network that has connectivity to your Purview account instead.
91+
- You don't have permission to check role assignments on the Purview account. You can contact the Purview account admin to check the role assignments for you. Learn about the needed Purview role from [Set up authentication](#set-up-authentication) section.
8192

8293
## Report lineage data to Azure Purview
8394

89.4 KB
Loading

0 commit comments

Comments
 (0)