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/includes/access-policies-configuration-azure-sql-db.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ ms.author: vlrodrig
4
4
ms.service: purview
5
5
ms.subservice: purview-data-policies
6
6
ms.topic: include
7
-
ms.date: 03/17/2022
7
+
ms.date: 03/24/2022
8
8
---
9
9
10
10
Return to the Azure portal for Azure SQL Database to verify it is now governed by Microsoft Purview
@@ -20,3 +20,6 @@ Return to the Azure portal for Azure SQL Database to verify it is now governed b
20
20

21
21
22
22
1. Confirm that the Microsoft Purview Governance Status shows `Governed`. Note that **it may take a few minutes** after you enable *Data use management* in Microsoft Purview for the correct status to be reflected.
23
+
24
+
>[!NOTE]
25
+
> If you disable Data use management for this Azure SQL Database data source, it might take up to 24 hours for the Microsoft Purview Governance Status to be updated automatically to `Not Governed`. This can be accelerated by selecting **Check for Microsoft Purview Governance**. Before you enable *Data use management* for the data source in another Microsoft Purview account, ensure that the Purview Governance Status shows as `Not Governed`. Then repeat the steps above with the new Microsoft Purview account.
0 commit comments