|
| 1 | +--- |
| 2 | +title: Access provisioning by data owner to Azure Storage datasets |
| 3 | +description: Step-by-step guide showing how data owners can create access policies to datasets in Azure Storage |
| 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: 03/14/2022 |
| 10 | +ms.custom: |
| 11 | +--- |
| 12 | + |
| 13 | +# Access provisioning by data owner to Azure Storage datasets (preview) |
| 14 | + |
| 15 | +[!INCLUDE [feature-in-preview](includes/feature-in-preview.md)] |
| 16 | + |
| 17 | +This article describes how a data owner can use Azure Purview to enable access to datasets in Azure Storage. At this point, only the following data sources are supported: |
| 18 | +- Blob storage |
| 19 | +- Azure Data Lake Storage (ADLS) Gen2 |
| 20 | + |
| 21 | +## Prerequisites |
| 22 | +[!INCLUDE [Access policies generic pre-requisites](./includes/access-policies-prerequisites-generic.md)] |
| 23 | + |
| 24 | +[!INCLUDE [Azure Storage specific pre-requisites](./includes/access-policies-prerequisites-storage.md)] |
| 25 | + |
| 26 | +## Configuration |
| 27 | +[!INCLUDE [Access policies generic configuration](./includes/access-policies-configuration-generic.md)] |
| 28 | + |
| 29 | +### Register the data sources in Azure Purview for Data use governance |
| 30 | +Register and scan each Storage account with Azure Purview to later define access policies. You can follow these guides: |
| 31 | + |
| 32 | +- [Register and scan Azure Storage Blob - Azure Purview](register-scan-azure-blob-storage-source.md) |
| 33 | + |
| 34 | +- [Register and scan Azure Data Lake Storage (ADLS) Gen2 - Azure Purview](register-scan-adls-gen2.md) |
| 35 | + |
| 36 | +Follow this link to [Enable the data source for access policies](./how-to-enable-data-use-governance.md) in Azure Purview by setting the **Data use governance** toggle to **Enabled**, as shown in the picture. |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | +## Create and publish a data owner policy |
| 41 | +Execute the steps in the [data-owner policy authoring tutorial](how-to-data-owner-policy-authoring-generic.md) to create and publish a policy similar to the example shown in the image: a policy that provides group *Contoso Team* *read* access to Storage account *marketinglake1*: |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +>[!Important] |
| 47 | +> - Publish is a background operation. It can take up to **2 hours** for the changes to be reflected in Storage account(s). |
| 48 | +
|
| 49 | + |
| 50 | +## Additional information |
| 51 | +- Policy statements set below container level on a Storage account are supported. If no access has been provided at Storage account level or container level, then the App that requests the data must execute a direct access by providing a fully qualified name to the data object. If the App attempts to crawl down the hierarchy starting from the Storage account or Container, and there is no access at that level, the request will fail. The following documents show examples of how to do perform a direct access. See also blogs in the *Next steps* section of this tutorial. |
| 52 | + - [*abfs* for ADLS Gen2](../hdinsight/hdinsight-hadoop-use-data-lake-storage-gen2.md#access-files-from-the-cluster) |
| 53 | + - [*az storage blob download* for Blob Storage](../storage/blobs/storage-quickstart-blobs-cli.md#download-a-blob) |
| 54 | +- Creating a policy at Storage account level will enable the Subjects to access system containers e.g., *$logs*. If this is undesired, first scan the data source(s) and then create finer-grained policies for each (i.e., at container or sub-container level). |
| 55 | + |
| 56 | + |
| 57 | +### Limits |
| 58 | +- The limit for Azure Purview policies that can be enforced by Storage accounts is 100MB per subscription, which roughly equates to 5000 policies. |
| 59 | + |
| 60 | +### Known issues |
| 61 | + |
| 62 | +> [!Warning] |
| 63 | +> **Known issues** related to Policy creation |
| 64 | +> - Do not create policy statements based on Azure Purview resource sets. Even if displayed in Azure Purview policy authoring UI, they are not yet enforced. Learn more about [resource sets](concept-resource-sets.md). |
| 65 | +
|
| 66 | +### Policy action mapping |
| 67 | + |
| 68 | +This section contains a reference of how actions in Azure Purview data policies map to specific actions in Azure Storage. |
| 69 | + |
| 70 | +| **Azure Purview policy action** | **Data source specific actions** | |
| 71 | +|---------------------------|-----------------------------------------------------------------------------------------| |
| 72 | +||| |
| 73 | +| *Read* |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/read | |
| 74 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read | |
| 75 | +||| |
| 76 | +| *Modify* |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read | |
| 77 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/write | |
| 78 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/add/action | |
| 79 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/move/action | |
| 80 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete | |
| 81 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/read | |
| 82 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/write | |
| 83 | +| |<sub>Microsoft.Storage/storageAccounts/blobServices/containers/delete | |
| 84 | +||| |
| 85 | + |
| 86 | + |
| 87 | +## Next steps |
| 88 | +Check blog, demo and related tutorials: |
| 89 | + |
| 90 | +* [Demo of access policy for Azure Storage](/video/media/8ce7c554-0d48-430f-8f63-edf94946947c/purview-policy-storage-dataowner-scenario_mid.mp4) |
| 91 | +* [Concepts for Azure Purview data owner policies](./concept-data-owner-policies.md) |
| 92 | +* [Enable Azure Purview data owner policies on all data sources in a subscription or a resource group](./how-to-data-owner-policies-resource-group.md) |
| 93 | +* [Blog: 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) |
| 94 | +* [Blog: Accessing data when folder level permission is granted](https://techcommunity.microsoft.com/t5/azure-purview-blog/data-policy-features-accessing-data-when-folder-level-permission/ba-p/3109583) |
| 95 | +* [Blog: Accessing data when file level permission is granted](https://techcommunity.microsoft.com/t5/azure-purview-blog/data-policy-features-accessing-data-when-file-level-permission/ba-p/3102166) |
0 commit comments