Skip to content

Commit 86236d2

Browse files
authored
Merge pull request #96906 from prashantatrimicrosoft/patch-3
update quickstart-connect-azure-purview.md
2 parents 81f68fb + f6401eb commit 86236d2

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/synapse-analytics/catalog-and-governance/quickstart-connect-azure-purview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,10 @@ For **Data Lineage - Synapse Pipeline**, you may see one of below status:
8282
- Cannot reach the Microsoft Purview account from your current network because the account is protected by firewall. You can launch the Synapse Studio from a private network that has connectivity to your Microsoft Purview account instead.
8383
- You don't have permission to check role assignments on the Microsoft Purview account. You can contact the Microsoft Purview account admin to check the role assignments for you. Learn about the needed Microsoft Purview role from [Set up authentication](#set-up-authentication) section.
8484

85+
>[!Note]
86+
>
87+
> Disconnected status doesn't impact you to use catalog search feature within Azure Synapse; it continues to work if the data readers role is granted at the Microsoft purview collection level.
88+
8589
## Report lineage to Microsoft Purview
8690

8791
Once you connect the Synapse workspace to a Microsoft Purview account, when you execute pipelines, Synapse reports lineage information to the Microsoft Purview account. For detailed supported capabilities and an end to end walkthrough, see [Metadata and lineage from Azure Synapse Analytics](../../purview/how-to-lineage-azure-synapse-analytics.md).

0 commit comments

Comments
 (0)