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/concept-self-service-data-access-policy.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: blessonj
6
6
ms.service: purview
7
7
ms.subservice: purview-data-policies
8
8
ms.topic: conceptual
9
-
ms.date: 03/10/2022
9
+
ms.date: 11/11/2022
10
10
---
11
11
12
12
# Microsoft Purview Self-service data discovery and access (Preview)
@@ -42,11 +42,11 @@ Microsoft Purview allows organizations to catalog metadata about all registered
42
42
43
43
With self-service data access workflow, data consumers can not only find data assets but also request access to the data assets. When the data consumer requests access to a data asset, the associated self-service data access workflow is triggered.
44
44
45
-
A default self-service data access workflow template is provided with every Microsoft Purview account. The default template can be amended to add more approvers and/or set the approver's email address. For more details refer [Create and enable self-service data access workflow](./how-to-workflow-self-service-data-access-hybrid.md).
45
+
A default self-service data access workflow template is provided with every Microsoft Purview account. The default template can be amended to add more approvers and/or set the approver's email address. For more details, refer [Create and enable self-service data access workflow](./how-to-workflow-self-service-data-access-hybrid.md).
46
46
47
-
Whenever a data consumer requests access to a dataset, the notification is sent to the workflow approver(s). The approver(s) can view the request and approve it either from Microsoft Purview portal or from within the email notification. When the request is approved, a policy is auto-generated and applied against the respective data source. Self-service data access policy gets auto-generated only if the data source is registered for **Data Use Management**. The pre-requisites mentioned within the [Data Use Management](./how-to-enable-data-use-management.md#prerequisites) have to be satisfied.
47
+
Whenever a data consumer requests access to a dataset, the notification is sent to the workflow approver(s). The approver(s) can view the request and approve it either from Microsoft Purview governance portal or from within the email notification. When the request is approved, a policy is auto-generated and applied against the respective data source. Self-service data access policy gets auto-generated only if the data source is registered for **Data Use Management**. The pre-requisites mentioned within the [Data Use Management](./how-to-enable-data-use-management.md#prerequisites) have to be satisfied.
48
48
49
-
Data consumer can access the requested dataset using tools such as PowerBI or Azure Synapse Analytics workspace.
49
+
Data consumer can access the requested dataset using tools such as Power BI or Azure Synapse Analytics workspace.
50
50
51
51
>[!NOTE]
52
52
> Users will not be able to browse to the asset using the Azure Portal or Storage explorer if the only permission granted is read/modify access at the file or folder level of the storage account.
[Self-service policies](concept-self-service-data-access-policy.md) allow you to manage access from Microsoft Purview to data sources that have been registered for **Data Use Management**.
17
17
18
-
This how-to guide describes how self-service policies get created in Microsoft Purview to enable access to Azure SQL DB. The following actions are currently enabled: *Read Tables*, and *Read Views*.
18
+
This how-to guide describes how self-service policies get created in Microsoft Purview to enable access to Azure SQL Database. The following actions are currently enabled: *Read Tables*, and *Read Views*.
19
19
20
20
> [!CAUTION]
21
-
> *Ownership chaining* must exist for *select* to work on Azure SQL DB*views*.
21
+
> *Ownership chaining* must exist for *select* to work on Azure SQL Database*views*.
Copy file name to clipboardExpand all lines: articles/purview/overview.md
+3-3Lines changed: 3 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: 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/11/2022
10
10
---
11
11
12
12
# What's available in the Microsoft Purview governance portal?
@@ -61,7 +61,7 @@ Microsoft Purview Data Policy is a set of central, cloud-based experiences that
61
61
- Manage access to data sources from a single-pane of glass, cloud-based experience
62
62
- Introduces a new data-plane permission model that is external to data sources
63
63
- Seamless integration with Microsoft Purview Data Map and Catalog helps search for data assets and grant access only to what is required via fine-grained policies
64
-
- Based on role definitions that are simple and abstracted (e.g. Read, Modify)
64
+
- Based on role definitions that are simple and abstracted (for example: Read, Modify)
65
65
- At-scale access provisioning
66
66
67
67
For more information, see our introductory guides:
@@ -112,7 +112,7 @@ Discovering and understanding data sources and their use is the primary purpose
112
112
113
113
At the same time, users can contribute to the catalog by tagging, documenting, and annotating data sources that have already been registered. They can also register new data sources, which are then discovered, understood, and consumed by the community of catalog users.
114
114
115
-
Lastly, Microsoft Purview Data Policy app leverages the metadata in the Data Map, providing a superior solution to keep your data secure.
115
+
Lastly, Microsoft Purview Data Policy app applies the metadata in the Data Map, providing a superior solution to keep your data secure.
116
116
* Structure and simplify the process of granting/revoking access.
117
117
* Reduce the effort of access provisioning.
118
118
* Access decision in Microsoft data systems has negligible latency penalty.
0 commit comments