Merge pull request #226893 from inward-eye/main

renamed from how-to to conceptual

Author: Court72

articles/purview/.openpublishing.redirection.purview.json

@@ -75,6 +75,11 @@
         "redirect_url": "/azure/purview/concept-policies-data-owner",
         "redirect_document_id": true
       },
+      {
+        "source_path_from_root": "/articles/purview/how-to-policies-purview-account-delete.md",
+        "redirect_url": "/azure/purview/concept-policies-purview-account-delete",
+        "redirect_document_id": true
+      },
       {
         "source_path_from_root": "/articles/purview/concept-account-upgrade.md",
         "redirect_url": "/azure/purview/catalog-permissions",

articles/purview/concept-policies-data-owner-action-update.md

@@ -0,0 +1,25 @@
+---
+title: Role definitions SQL Performance Monitor and SQL Security Auditor supported only from DevOps policies experience
+description: This guide discusses actions that have been retired from Data owner policies experience and are now supported only from the DevOps policies experience.
+author: inward-eye
+ms.author: vlrodrig
+ms.service: purview
+ms.subservice: purview-data-policies
+ms.topic: conceptual
+ms.date: 02/09/2023
+ms.custom:
+---
+# Role definitions SQL Performance Monitor and SQL Security Auditor supported only from DevOps policies experience
+
+This guide discusses actions that have been retired from Data owner policies experience and are now supported only from the DevOps policies experience.
+
+## Important considerations
+The following two actions that were previously available in the Microsoft Purview Data owner policies experience are now supported only from the Microsoft Purview DevOps policies, which is a more focused experience.
+- SQL Performance Monitor
+- SQL Security Auditor
+
+If you currently have Data owner policies with these actions we encourage you to give the DevOps policies experience a try. Creating new policies or editing existing policies that involve these two actions is now unsupported from the Data owner experience.
+
+## Next steps
+Check these concept guides
+* [DevOps policies](concept-policies-devops.md) 

articles/purview/how-to-policies-purview-account-delete.md renamed to articles/purview/concept-policies-purview-account-delete.md

@@ -6,18 +6,18 @@ ms.author: vlrodrig
 ms.service: purview
 ms.subservice: purview-data-policies
 ms.topic: conceptual
-ms.date: 11/16/2022
+ms.date: 02/09/2023
 ms.custom:
 ---
 # Impact of deleting Microsoft Purview account on access policies
 
 ## Important considerations 
-Deleting a Microsoft Purview account that has active (that is, published) policies will remove those policies. This means that the access to data sources or datasets that was previously provisioned via those policies will also be removed. This can lead to outages, that is, users or groups in your organization not able to access critical data. Review the decision to delete the Microsoft Purview account with the people in Policy Author role at root collection level before proceeding. To find out who holds that role in the Microsoft Purview account, review the section on managing role assignments in this [guide](./how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
+Deleting a Microsoft Purview account that has active (that is, published) policies removes those policies. Any access to a data source or a dataset that was previously provisioned from Microsoft Purview gets revoked. This can lead to outages, that is, users or groups in your organization not able to access critical data. Review the decision to delete the Microsoft Purview account with the people in Policy Author role at root collection level before proceeding. To find out who holds that role in the Microsoft Purview account, review the section on managing role assignments in this [guide](./how-to-create-and-manage-collections.md#add-roles-and-restrict-access-through-collections).
 
 Before deleting the Microsoft Purview account, it's advisable that you provision access to the users in your organization that need access to datasets using an alternate mechanism or a different Purview account. Then orderly delete or unpublish any active policies
-* [Deleting DevOps policies](how-to-policies-devops-authoring-generic.md#delete-a-devops-policy) - You'll need to delete DevOps policies for them to be unpublished.
+* [Deleting DevOps policies](how-to-policies-devops-authoring-generic.md#delete-a-devops-policy) - You need to delete DevOps policies for them to be unpublished.
 * [Unpublishing Data Owner policies](how-to-policies-data-owner-authoring-generic.md#unpublish-a-policy).
-* [Deleting Self-service access policies](how-to-delete-self-service-data-access-policy.md) - You'll need to delete Self-service access policies for them to be unpublished.
+* [Deleting Self-service access policies](how-to-delete-self-service-data-access-policy.md) - You need to delete Self-service access policies for them to be unpublished.
 
 ## Next steps
 Check these concept guides

articles/purview/toc.yml

@@ -134,6 +134,10 @@ items:
       href: concept-policies-devops.md
     - name: Self-service data access policy
       href: concept-self-service-data-access-policy.md
+    - name: Impact of deleting Microsoft Purview account on access policies
+      href: concept-policies-purview-account-delete.md
+    - name: Update on Data owner policies actions
+      href: concept-policies-data-owner-action-update.md
   - name: Data Estate Insights
     items:
     - name: Data Estate Insights
@@ -369,8 +373,6 @@ items:
     items:
     - name: Register data sources for "Data use management"
       href: how-to-enable-data-use-management.md
-    - name: Impact of deleting Microsoft Purview account on access policies
-      href: how-to-policies-purview-account-delete.md
     - name: DevOps policies
       items:
       - name: DevOps policies - Create, list, update and delete policies