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
This article discusses concepts related to managing access to data sources in your data estate from within the Microsoft Purview governance portal. In particular, it focuses on DevOps policies.
# Provision access to system metadata in Arc-enabled SQL Server
15
13
16
14
[DevOps policies](concept-policies-devops.md) are a type of Microsoft Purview access policies. They allow you to manage access to system metadata on data sources that have been registered for *Data use management* in Microsoft Purview. These policies are configured directly in the Microsoft Purview governance portal, and after being saved they get automatically published and then get enforced by the data source.
# Create, list, update and delete Microsoft Purview DevOps policies
15
13
16
14
[DevOps policies](concept-policies-devops.md) are a type of Microsoft Purview access policies. They allow you to manage access to system metadata on data sources that have been registered for *Data use management* in Microsoft Purview. These policies are configured directly in the Microsoft Purview governance portal, and after being saved they get automatically published and then get enforced by the data source.
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).
| Azure |[Multiple sources](register-scan-azure-multiple-sources.md)|[Yes](register-scan-azure-multiple-sources.md#register)|[Yes](register-scan-azure-multiple-sources.md#scan)| No |[Yes (Preview)](register-scan-azure-multiple-sources.md#access-policy)| No |
| Azure |[Multiple sources](register-scan-azure-multiple-sources.md)|[Yes](register-scan-azure-multiple-sources.md#register)|[Yes](register-scan-azure-multiple-sources.md#scan)| No |[Yes](register-scan-azure-multiple-sources.md#access-policy)| No |
||[Azure Data Explorer](register-scan-azure-data-explorer.md)|[Yes](register-scan-azure-data-explorer.md#register)|[Yes](register-scan-azure-data-explorer.md#scan)| No*| No | No|
27
27
||[Azure Data Factory](how-to-link-azure-data-factory.md)|[Yes](how-to-link-azure-data-factory.md)| No |[Yes](how-to-link-azure-data-factory.md)| No | No|
28
28
||[Azure Data Lake Storage Gen1](register-scan-adls-gen1.md)|[Yes](register-scan-adls-gen1.md#register)|[Yes](register-scan-adls-gen1.md#scan)| Limited*| No | No|
29
-
||[Azure Data Lake Storage Gen2](register-scan-adls-gen2.md)|[Yes](register-scan-adls-gen2.md#register)|[Yes](register-scan-adls-gen2.md#scan)| Limited*|[Yes (Preview)](register-scan-adls-gen2.md#access-policy)|[Yes](register-scan-adls-gen2.md#data-sharing)|
29
+
||[Azure Data Lake Storage Gen2](register-scan-adls-gen2.md)|[Yes](register-scan-adls-gen2.md#register)|[Yes](register-scan-adls-gen2.md#scan)| Limited*|[Yes](register-scan-adls-gen2.md#access-policy) (Preview) |[Yes](register-scan-adls-gen2.md#data-sharing)|
30
30
||[Azure Data Share](how-to-link-azure-data-share.md)|[Yes](how-to-link-azure-data-share.md)| No |[Yes](how-to-link-azure-data-share.md)| No | No|
31
31
||[Azure Database for MySQL](register-scan-azure-mysql-database.md)|[Yes](register-scan-azure-mysql-database.md#register)|[Yes](register-scan-azure-mysql-database.md#scan)| No*| No | No |
32
32
||[Azure Database for PostgreSQL](register-scan-azure-postgresql.md)|[Yes](register-scan-azure-postgresql.md#register)|[Yes](register-scan-azure-postgresql.md#scan)| No*| No | No |
33
33
||[Azure Dedicated SQL pool (formerly SQL DW)](register-scan-azure-synapse-analytics.md)|[Yes](register-scan-azure-synapse-analytics.md#register)|[Yes](register-scan-azure-synapse-analytics.md#scan)| No*| No | No |
34
34
||[Azure Files](register-scan-azure-files-storage-source.md)|[Yes](register-scan-azure-files-storage-source.md#register)|[Yes](register-scan-azure-files-storage-source.md#scan)| Limited*| No | No |
35
-
||[Azure SQL Database](register-scan-azure-sql-database.md)|[Yes](register-scan-azure-sql-database.md#register)|[Yes](register-scan-azure-sql-database.md#scan)|[Yes (Preview)](register-scan-azure-sql-database.md#lineagepreview)|[Yes (Preview)](register-scan-azure-sql-database.md#access-policy)| No |
35
+
||[Azure SQL Database](register-scan-azure-sql-database.md)|[Yes](register-scan-azure-sql-database.md#register)|[Yes](register-scan-azure-sql-database.md#scan)|[Yes (Preview)](register-scan-azure-sql-database.md#lineagepreview)|[Yes](register-scan-azure-sql-database.md#access-policy) (Preview) | No |
36
36
||[Azure SQL Managed Instance](register-scan-azure-sql-managed-instance.md)|[Yes](register-scan-azure-sql-managed-instance.md#scan)|[Yes](register-scan-azure-sql-managed-instance.md#scan)| No*| No | No |
37
37
||[Azure Synapse Analytics (Workspace)](register-scan-synapse-workspace.md)|[Yes](register-scan-synapse-workspace.md#register)|[Yes](register-scan-synapse-workspace.md#scan)|[Yes - Synapse pipelines](how-to-lineage-azure-synapse-analytics.md)| No| No |
38
38
|Database|[Amazon RDS](register-scan-amazon-rds.md)|[Yes](register-scan-amazon-rds.md#register-an-amazon-rds-data-source)|[Yes](register-scan-amazon-rds.md#scan-an-amazon-rds-database)| No | No | No |
Copy file name to clipboardExpand all lines: articles/purview/overview.md
+4-4Lines changed: 4 additions & 4 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: whhender
6
6
ms.service: purview
7
7
ms.custom: event-tier1-build-2022
8
8
ms.topic: overview
9
-
ms.date: 11/10/2022
9
+
ms.date: 11/16/2022
10
10
---
11
11
12
12
# What's available in the Microsoft Purview governance portal?
@@ -65,9 +65,9 @@ Microsoft Purview Data Policy is a set of central, cloud-based experiences that
65
65
- At-scale access provisioning
66
66
67
67
For more information, see our introductory guides:
68
-
*[Data owner access policies](concept-policies-data-owner.md)(preview): Provision fine-grained to broad access to users and groups via intuitive authoring experience.
69
-
*[Self-service access policies](concept-self-service-data-access-policy.md)(preview): Self-Service: Workflow approval and automatic provisioning of access requests initiated by business analysts that discover data assets in Microsoft Purview’s catalog.
70
-
*[DevOps policies](concept-policies-devops.md)(preview): Provision access to system metadata for IT operations and other DevOps personnel, supporting typical functions like SQL Performance Monitor and SQL Security Auditor.
68
+
*[Data owner access policies](concept-policies-data-owner.md)(preview): Provision fine-grained to broad access to users and groups via intuitive authoring experience.
69
+
*[Self-service access policies](concept-self-service-data-access-policy.md)(preview): Self-Service: Workflow approval and automatic provisioning of access requests initiated by business analysts that discover data assets in Microsoft Purview’s catalog.
70
+
*[DevOps policies](concept-policies-devops.md): Provision access to system metadata for IT operations and other DevOps personnel, supporting typical functions like SQL Performance Monitor and SQL Security Auditor.
71
71
72
72
## Traditional challenges that Microsoft Purview seeks to address
0 commit comments