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/how-to-policies-devops-authoring-generic.md
+4-3Lines changed: 4 additions & 3 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: vlrodrig
6
6
ms.service: purview
7
7
ms.subservice: purview-data-policies
8
8
ms.topic: how-to
9
-
ms.date: 03/10/2023
9
+
ms.date: 03/12/2023
10
10
ms.custom:
11
11
---
12
12
# Create, list, update and delete Microsoft Purview DevOps policies
@@ -80,7 +80,7 @@ To delete a DevOps policy, ensure first that you have the Microsoft Purview Poli
80
80

81
81
82
82
## Test the DevOps policy
83
-
After creating the policy, any of the Azure AD users in the Subject should now be able to connect to the data sources in the scope of the policy. To test, use SSMS or any SQL client and try to query some DMVs/DMFs. We list here some examples. For more, you can consult the [Microsoft Purview DevOps policies concept guide](/azure/purview/concept-policies-devops.md#mapping-of-popular-dmvsdmfs)
83
+
After creating the policy, any of the Azure AD users in the Subject should now be able to connect to the data sources in the scope of the policy. To test, use SSMS or any SQL client and try to query some DMVs/DMFs. We list here some examples. For more, you can consult the [Microsoft Purview DevOps policies concept guide](./concept-policies-devops.md#mapping-of-popular-dmvsdmfs)
84
84
85
85
### Testing SQL Performance Monitor access
86
86
If you provided the Subject(s) of the policy SQL Performance Monitor role, you can issue the following commands
@@ -143,4 +143,5 @@ Check the blogs, videos and related documents
0 commit comments