Skip to content

Commit 51fa8ae

Browse files
authored
Merge pull request #187566 from whhender/update-data-policy-generic
Update data policy generic
2 parents aeda2e7 + fd694b2 commit 51fa8ae

7 files changed

+196
-62
lines changed

articles/purview/how-to-data-owner-policy-authoring-generic.md

Lines changed: 61 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -6,39 +6,56 @@ ms.author: vlrodrig
66
ms.service: purview
77
ms.subservice: purview-data-policies
88
ms.topic: how-to
9-
ms.date: 2/22/2022
10-
ms.custom:
9+
ms.date: 2/24/2022
1110
---
1211

13-
# Authoring and publishing data owner access policies (preview)
14-
This tutorial describes how a data owner can create, update and publish access policies in Azure Purview.
12+
# Authoring and publishing data owner access policies (Preview)
13+
14+
[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
15+
16+
Access policies allow data owners to manage access to datasets from Azure Purview. Data owners can monitor and manage data use from within the Azure Purview Studio, without directly modifying the resource where the data is housed.
17+
18+
This tutorial describes how a data owner can create, update, and publish access policies in Azure Purview.
1519

1620
## Prerequisites
17-
The following actions are needed before authoring access policies in Azure Purview:
18-
1. Configure permissions in the data source and in Azure Purview
19-
1. Register the data source in Azure Purview for Data Use Governance
2021

21-
These tutorials list the pre-requisites of supported data sources
22-
- [Azure Storage](./tutorial-data-owner-policies-storage.md#configuration)
23-
- [Resource Groups and Subscriptions](./tutorial-data-owner-policies-resource-group.md#configuration)
22+
### Required permissions
23+
24+
>[!IMPORTANT]
25+
> - Currently, policy operations are only supported at **root collection level** and not child collection level.
26+
27+
- User needs Azure Purview *Data source administrator* role at the root collection level to:
28+
- Register a data source, resource group or subscription for *Data use governance*.
29+
- Publish a policy.
30+
- User needs Azure Purview *Policy authors* role at root collection level to create or edit policies.
31+
32+
For more information, see the guide on [managing Azure Purview role assignments](catalog-permissions.md#assign-permissions-to-your-users).
33+
34+
### Source configuration
35+
36+
To apply these policies to data sources in your environment, you'll need to configure your sources.
37+
38+
1. Your source needs to already be registered to Azure Purview. To register a resource, follow the **Prerequisites** and **Register** sections of the [source pages](azure-purview-connector-overview.md) for your resources.
39+
1. [Enable data use governance on your resource](how-to-enable-data-use-governance.md#enable-data-use-governance).
40+
1. Follow any policy-specific prerequisites for your source. Check the [Azure Purview supported data sources table](azure-purview-connector-overview.md#azure-purview-data-sources) and select the link in the **Access Policy** column for sources where access policies are available. Follow any steps listed in the Access policy or Prerequisites sections.
2441

2542
## Create a new policy
2643

2744
This section describes the steps to create a new policy in Azure Purview.
2845

29-
1. Sign in to Azure Purview Studio.
46+
1. Sign in to the [Azure Purview Studio](https://web.purview.azure.com/resource/).
3047

3148
1. Navigate to the **Data policy** feature using the left side panel. Then select **Data policies**.
3249

3350
1. Select the **New Policy** button in the policy page.
3451

35-
![Image shows how a data owner can access the Policy functionality in Azure Purview when it wants to create policies.](./media/access-policies-common/policy-onboard-guide-1.png)
52+
:::image type="content" source="./media/access-policies-common/policy-onboard-guide-1.png" alt-text="Data owner can access the Policy functionality in Azure Purview when it wants to create policies.":::
3653

3754
1. The new policy page will appear. Enter the policy **Name** and **Description**.
3855

3956
1. To add policy statements to the new policy, select the **New policy statement** button. This will bring up the policy statement builder.
4057

41-
![Image shows how a data owner can create a new policy statement.](./media/access-policies-common/create-new-policy.png)
58+
:::image type="content" source="./media/access-policies-common/create-new-policy.png" alt-text="Data owner can create a new policy statement.":::
4259

4360
1. Select the **Effect** button and choose *Allow* from the drop-down list.
4461

@@ -50,63 +67,64 @@ This section describes the steps to create a new policy in Azure Purview.
5067
- To create a broad policy statement that covers an entire data source, resource group, or subscription that was previously registered, use the **Data sources** box and select its **Type**.
5168
- To create a fine-grained policy, use the **Assets** box instead. Enter the **Data Source Type** and the **Name** of a previously registered and scanned data source. See example in the image.
5269

53-
![Image shows how a data owner can select a Data Resource when editing a policy statement.](./media/access-policies-common/select-data-source-type.png)
70+
:::image type="content" source="./media/access-policies-common/select-data-source-type.png" alt-text="Data owner can select a Data Resource when editing a policy statement.":::
5471

55-
1. Select the **Continue** button and transverse the hierarchy to select and underlying data-object (e.g. folder, file, etc). Select **Recursive** to apply the policy from that point in the hierarchy down to any child data-objects. Then select the **Add** button. This will take you back to the policy editor.
72+
1. Select the **Continue** button and transverse the hierarchy to select and underlying data-object (for example: folder, file, etc.). Select **Recursive** to apply the policy from that point in the hierarchy down to any child data-objects. Then select the **Add** button. This will take you back to the policy editor.
5673

57-
![Image shows how a data owner can select the asset when creating or editing a policy statement.](./media/access-policies-common/select-asset.png)
74+
:::image type="content" source="./media/access-policies-common/select-asset.png" alt-text="Data owner can select the asset when creating or editing a policy statement.":::
5875

5976
1. Select the **Subjects** button and enter the subject identity as a principal, group, or MSI. Then select the **OK** button. This will take you back to the policy editor
6077

61-
![Image shows how a data owner can select the subject when creating or editing a policy statement.](./media/access-policies-common/select-subject.png)
78+
:::image type="content" source="./media/access-policies-common/select-subject.png" alt-text="Data owner can select the subject when creating or editing a policy statement.":::
6279

6380
1. Repeat the steps #5 to #11 to enter any more policy statements.
6481

65-
1. Select the **Save** button to save the policy
82+
1. Select the **Save** button to save the policy.
6683

67-
## Update or delete a policy
84+
Now that you have created your policy, you will need to publish it for it to become active.
6885

69-
Steps to create a new policy in Azure Purview are as follows.
86+
## Publish a policy
7087

71-
1. Sign in to Azure Purview Studio.
88+
A newly created policy is in the **draft** state. The process of publishing associates the new policy with one or more data sources under governance. This is called "binding" a policy to a data source.
7289

73-
1. Navigate to the **Data policy** feature using the left side panel. Then select **Data policies**.
90+
The steps to publish a policy are as follows:
7491

75-
![Image shows how a data owner can access the Policy functionality in Azure Purview when it wants to update a policy.](./media/access-policies-common/policy-onboard-guide-2.png)
92+
1. Sign in to the [Azure Purview Studio](https://web.purview.azure.com/resource/).
7693

77-
1. The Policy portal will present the list of existing policies in Azure Purview. Select the policy that needs to be updated.
94+
1. Navigate to the **Data policy** feature using the left side panel. Then select **Data policies**.
7895

79-
1. The policy details page will appear, including Edit and Delete options. Select the **Edit** button, which brings up the policy statement builder. Now, any parts of the statements in this policy can be updated. To delete the policy, use the **Delete** button.
96+
:::image type="content" source="./media/access-policies-common/policy-onboard-guide-2.png" alt-text="Data owner can access the Policy functionality in Azure Purview when it wants to update a policy by selecting 'Data policies'.":::
8097

81-
![Image shows how a data owner can edit or delete a policy statement.](./media/access-policies-common/edit-policy.png)
98+
1. The Policy portal will present the list of existing policies in Azure Purview. Locate the policy that needs to be published. Select the **Publish** button on the right top corner of the page.
8299

83-
## Publish the policy
100+
:::image type="content" source="./media/access-policies-common/publish-policy.png" alt-text="Data owner can publish a policy.":::
84101

85-
A newly created policy is in the draft state. The process of publishing associates the new policy with one or more data sources under governance. This is called "binding" a policy to a data source.
102+
1. A list of data sources is displayed. You can enter a name to filter the list. Then, select each data source where this policy is to be published and then select the **Publish** button.
86103

87-
The steps to publish a policy are as follows
104+
:::image type="content" source="./media/access-policies-common/select-data-sources-publish-policy.png" alt-text="Data owner can select the data source where the policy will be published.":::
88105

89-
1. Sign in to Azure Purview Studio.
106+
>[!Note]
107+
> After making changes to a policy, there is no need to publish it again for it to take effect if the data source(s) continues to be the same.
90108
91-
1. Navigate to the **Data policy** feature using the left side panel. Then select **Data policies**.
109+
## Update or delete a policy
92110

93-
![Image shows how a data owner can access the Policy functionality in Azure Purview when it wants to publish a policy.](./media/access-policies-common/policy-onboard-guide-2.png)
111+
Steps to update or delete a policy in Azure Purview are as follows.
94112

95-
1. The Policy portal will present the list of existing policies in Azure Purview. Locate the policy that needs to be published. Select the **Publish** button on the right top corner of the page.
113+
1. Sign in to the [Azure Purview Studio](https://web.purview.azure.com/resource/).
96114

97-
![Image shows how a data owner can publish a policy.](./media/access-policies-common/publish-policy.png)
115+
1. Navigate to the **Data policy** feature using the left side panel. Then select **Data policies**.
98116

99-
1. A list of data sources is displayed. You can enter a name to filter the list. Then, select each data source where this policy is to be published and then select the **Publish** button.
117+
:::image type="content" source="./media/access-policies-common/policy-onboard-guide-2.png" alt-text="Data owner can access the Policy functionality in Azure Purview when it wants to update a policy.":::
100118

101-
![Image shows how a data owner can select the data source where the policy will be published.](./media/access-policies-common/select-data-sources-publish-policy.png)
119+
1. The Policy portal will present the list of existing policies in Azure Purview. Select the policy that needs to be updated.
102120

103-
>[!Note]
104-
> - After making changes to a policy, there is no need to publish it again for it to take effect if the data source(s) continues to be the same.
121+
1. The policy details page will appear, including Edit and Delete options. Select the **Edit** button, which brings up the policy statement builder. Now, any parts of the statements in this policy can be updated. To delete the policy, use the **Delete** button.
122+
123+
:::image type="content" source="./media/access-policies-common/edit-policy.png" alt-text="Data owner can edit or delete a policy statement.":::
105124

106125
## Next steps
107-
Check blog, demo and related tutorials
108126

109-
* [What's New in Azure Purview at Microsoft Ignite 2021](https://techcommunity.microsoft.com/t5/azure-purview/what-s-new-in-azure-purview-at-microsoft-ignite-2021/ba-p/2915954)
110-
* [Demo of data owner access policies for Azure Storage](https://www.youtube.com/watch?v=CFE8ltT19Ss)
111-
* [Enable Azure Purview data owner policies on all data sources in a subscription or a resource group](./tutorial-data-owner-policies-resource-group.md)
112-
* [Enable Azure Purview data owner policies on an Azure Storage account](./tutorial-data-owner-policies-storage.md)
127+
For specific guides on creating policies, you can follow these tutorials:
128+
129+
- [Enable Azure Purview data owner policies on all data sources in a subscription or a resource group](./tutorial-data-owner-policies-resource-group.md)
130+
- [Enable Azure Purview data owner policies on an Azure Storage account](./tutorial-data-owner-policies-storage.md)
Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
---
2+
title: Enabling data use governance on your Azure Purview sources
3+
description: Step-by-step guide on how to enable data use access for your registered sources.
4+
author: inward-eye
5+
ms.author: vlrodrig
6+
ms.service: purview
7+
ms.subservice: purview-data-policies
8+
ms.topic: how-to
9+
ms.date: 2/24/2022
10+
ms.custom:
11+
---
12+
13+
# Enable data use governance on your Azure Purview sources
14+
15+
[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)]
16+
17+
Data use governance is a feature within your registered Azure Purview resources that lets Azure Purview administrators manage data use from within Azure Purview.
18+
19+
## Prerequisites
20+
21+
To register a data source, resource group, or subscription in Azure Purview with the *Data use Governance* option set, a user needs to have **either one of the following** IAM role combinations on that resource:
22+
23+
- IAM *Owner*
24+
- Both IAM *Contributor* + IAM *User Access Administrator*
25+
26+
Follow this [guide to configure Azure RBAC role permissions](../role-based-access-control/check-access.md).
27+
28+
29+
## Enable data use governance
30+
31+
To enable data use governance for a resource, the resource will first need to be registered in Azure Purview.
32+
To register a resource, follow the **Prerequisites** and **Register** sections of the [source pages](azure-purview-connector-overview.md) for your resources.
33+
34+
Once you have your resource registered, follow the rest of the steps to enable an individual resource for data use governance.
35+
36+
1. Go to the [Azure Purview Studio](https://web.purview.azure.com/resource/).
37+
38+
1. Select the **Data map** tab in the left menu.
39+
40+
1. Select the **Sources** tab in the left menu.
41+
42+
1. Select the source you want to enable data use governance for.
43+
44+
1. At the top of the source page, select **Edit source**.
45+
46+
1. Enable the data source for data use governance in Azure Purview by setting the **Data use governance** toggle to **Enabled**, as shown in the image below.
47+
48+
:::image type="content" source="./media/tutorial-data-owner-policies-storage/register-data-source-for-policy-storage.png" alt-text="Set Data use governance toggle to **Enabled** at the bottom of the menu.":::
49+
50+
> [!WARNING]
51+
> **Known issues** related to source registration:
52+
>
53+
> - Moving data sources to a different resource group or subscription is not yet supported. If want to do that, de-register the data source in Azure Purview before moving it and then register it again after that happens.
54+
> - Once a subscription gets disabled for *Data use governance* any underlying assets that are enabled for *Data use governance* will be disabled, which is the right behavior. However, policy statements based on those assets will still be allowed after that.
55+
56+
57+
## Disable data use governance
58+
59+
>[!Note]
60+
>If your resource is currently a part of any active access policy, you will not be able to disable data use governance. First [remove the resource from the policy](how-to-data-owner-policy-authoring-generic.md#update-or-delete-a-policy), then disable data use governance.
61+
62+
To disable data use governance for a source, resource group, or subscription, a user needs to either be a data source **Owner** or an Azure Purview **Data source admin**. Once you have those permissions follow these steps:
63+
64+
1. Go to the [Azure Purview Studio](https://web.purview.azure.com/resource/).
65+
66+
1. Select the **Data map** tab in the left menu.
67+
68+
1. Select the **Sources** tab in the left menu.
69+
70+
1. Select the source you want to disable data use governance for.
71+
72+
1. At the top of the source page, select **Edit source**.
73+
74+
1. Set the **Data use governance** toggle to **Disabled**.
75+
76+
>[!NOTE]
77+
> Disabling **Data use governance** for a subscription source will disable it also for all assets registered in that subscription.
78+
79+
## Data use governance best practices
80+
81+
- We highly encourage registering data sources for *Data use governance* and managing all associated access policies in a single Azure Purview account.
82+
- Should you have multiple Azure Purview accounts, be aware that **all** data sources belonging to a subscription must be registered for *Data use governance* in a single Azure Purview account. That Azure Purview account can be in any subscription in the tenant. The *Data use governance* toggle will become greyed out when there are invalid configurations. Some examples of valid and invalid configurations follow in the diagram below:
83+
- **Case 1** shows a valid configuration where a Storage account is registered in an Azure Purview account in the same subscription.
84+
- **Case 2** shows a valid configuration where a Storage account is registered in an Azure Purview account in a different subscription.
85+
- **Case 3** shows an invalid configuration arising because Storage accounts S3SA1 and S3SA2 both belong to Subscription 3, but are registered to different Azure Purview accounts. In that case, the *Data use governance* toggle will only work in the Azure Purview account that wins and registers a data source in that subscription first. The toggle will then be greyed out for the other data source.
86+
87+
:::image type="content" source="./media/access-policies-common/valid-and-invalid-configurations.png" alt-text="Diagram shows valid and invalid configurations when using multiple Azure Purview accounts to manage policies.":::
88+
89+
## Next steps
90+
91+
- [Create data owner policies for your resources](how-to-data-owner-policy-authoring-generic.md)
92+
- [Enable Azure Purview data owner policies on all data sources in a subscription or a resource group](./tutorial-data-owner-policies-resource-group.md)
93+
- [Enable Azure Purview data owner policies on an Azure Storage account](./tutorial-data-owner-policies-storage.md)
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
author: whhender
3+
ms.author: whhender
4+
ms.service: purview
5+
ms.topic: include
6+
ms.date: 02/04/2022
7+
---
8+
9+
1. Go to the subscription or the resource group in the Azure portal.
10+
1. Select **Access Control (IAM)** from the left menu.
11+
1. Select **+Add**.
12+
1. In the **Select input** box, select the **Reader** role and enter your Azure Purview account name (which represents its MSI file name).
13+
1. Select **Save** to finish the role assignment. This will allow Azure Purview to list resources under a subscription or resource group.

0 commit comments

Comments
 (0)