Share Azure Storage data in-place with Microsoft Purview Data Sharing (preview)
Important
This feature is currently being retired, with support provided until September 2025 to allow for migration to Microsoft Fabric external data sharing.
Microsoft Purview Data Sharing supports in-place data sharing from Azure Data Lake Storage (ADLS Gen2) to ADLS Gen2, and Blob storage account to Blob storage account. This article explains how to share data using Microsoft Purview.
Prerequisites to share data
Microsoft Purview prerequisites
- A Microsoft Purview account.
- A minimum of Data Reader role is needed on a Microsoft Purview collection to use data sharing in the governance portal. Refer to Microsoft Purview permissions to learn more about the Microsoft Purview collection and roles.
- To use the SDK, no Microsoft Purview permissions are needed.
- Your data recipient's Azure sign-in email address, or the object ID and tenant ID of the recipient application, that you'll use to send the invitation to receive a share. The recipient's email alias won't work.
Azure Storage account prerequisites
Your Azure subscription must be registered for the AllowDataSharing preview feature. (If you haven't already registered this preview feature, consider using Microsoft Fabric external data sharing instead, since Microsoft Purview Data Sharing will be retired in September 2025.) Or, contact support.
A source storage account created after the registration step is completed. Source storage account can be in a different Azure region from your Microsoft Purview account, but needs to follow the available configurations.
You need the Owner or Storage Blob Data Owner role on the source storage account to be able to share data. You can find more details on the ADLS Gen2 or Blob storage data source page.
If the source storage account is in a different Azure subscription than the one for Microsoft Purview account, the Microsoft. Purview resource provider needs to be registered in the Azure subscription where the Storage account is located. It's automatically registered at the time of share provider adding an asset if the user has permission to do the
/register/action
operation and therefore, Contributor or Owner roles to the subscription where the Storage account is located. This registration is only needed the first time when sharing or receiving data into a storage account in the Azure subscription.A storage account needs to be registered in the collection to create a share using the Microsoft Purview compliance portal experience. For instructions to register, see the ADLS Gen2 or Blob storage data source pages. This step isn't required to use the SDK.
Create a share
There are two ways you can create a data share:
Create share from asset
You can create a share by starting from Data Catalog
Within the classic Microsoft Purview governance portal or the new Microsoft Purview portal, find the Azure Storage or Azure Data Lake Storage (ADLS) Gen 2 data asset you would like to share data from using either the data catalog search or browse.
Once you have found your data asset, select the Data Share button.
Select +New Share.
Follow the rest of the steps to create your data share.
Create share from application
If you're using the new Microsoft Purview experience You can create a share by starting from the Data Catalog.
Open the Microsoft Purview portal. Navigate to the Data Catalog application. Then select Shares. Select +New Share.
If you're using the classic Microsoft Purview experience You can create a share by starting from the Data Map.
Open the Microsoft Purview governance portal. Select the Data Map icon from the left navigation. Then select Shares. Select +New Share.
From either location, select the Storage account type and the Storage account you want to share data from. Then select Continue.
Follow the rest of the steps to create your data share.
Create share
Specify a name and a description of share contents (optional). Then select Continue.
Search for and add all the assets you'd like to share out at the container, folder, and file level, and then select Continue.
Important
Only containers, files, and folders that belong to the current Blob or ADLSGen2 Storage account can be added to the share.
You can edit the display names the shared data will have, if you like. Then select Continue.
Select Add Recipient and select User or App.
To share data to a user, select User, then enter the Azure sign-in email address of who you want to share data with. By default, the option to enter email address of user is shown.
To to share data with a service principal, select App. Enter the object ID and tenant ID of the recipient you want to share data with.
Select Create and Share. Optionally, you can specify an Expiration date for when to terminate the share. You can share the same data with multiple recipients by selecting Add Recipient multiple times.
You've now created your share. The recipients of your share will receive an invitation and they can view the share invitation in their Microsoft Purview account.
When a share is created, a new asset of type sent share is ingested into the Microsoft Purview catalog, in the same collection as the storage account from which you created the share. You can search for it like any other asset in the data catalog.
You can also track lineage for data shared using Microsoft Purview. See, Microsoft Purview Data Sharing lineage to learn more about share assets and data sharing lineage.
Note
Shares created using the SDK without registering the storage account with Microsoft Purview will not be ingested into the catalog. User can register their storage account if desired. If a storage account is un-registered or re-registered to a different collection, share assets of that storage account continue to be in the initial collection.
Update a sent share
Once a share is created, you can update description, assets, and recipients.
Note
If you only have the Reader role on the source storage account, you will be able to view list of sent shares and received shares but not edit. You can find more details on the ADLS Gen2 or Blob storage data source page.
You can find your sent shares one of two ways:
Access the blob storage or ADLS Gen2 asset where the data was shared from in the data catalog. Open it, then select Data Share. There you're able to see all the shares for that asset. Select a share, and then select the Edit option.
For shares that you sent, in the classic Microsoft Purview governance portal you can find them in the Shares menu in the Microsoft Purview Data Map. In the new Microsoft Purview portal you can find them in the Data Catalog application in the Shares menu. There you're able to see all the shares you have sent. Select a share, and then select the Edit option.
From any of these places you can:
Edit details
On the Details tab of the edit share page, you can update the share name and description. Save any changes by selecting Save.
Edit assets
On the Asset tab of the edit share page you can see all the shared files and folders.
You can remove any containers, files, or folders from the share by selecting the delete button in the asset's row however you can't remove all the assets of a sent share.
You can add new assets by selecting the Edit button and then searching for and selecting any other containers, files, and folders in the asset that you would like to add.
Once you've selected your assets, select Add, and you'll see your new asset in the Asset tab.
Save all your changes by selecting the Save button.
Edit recipients
On the Recipients tab of the edit share page you can see all the users and groups that are receiving your shares, their status, and the expiration date for their share.
Here are what each of the recipient statuses mean:
Status | Meaning |
---|---|
Attached | The share has been accepted and the recipient has access to the shared data. |
Detached | The recipient hasn't accepted the invitation or is no longer active. They aren't receiving the share. |
You can remove or delete recipients by either selecting the delete button on the recipient's row, or selecting multiple recipients and then selecting the Delete recipients button at the top of the page.
You can add recipients by selecting the Add recipients button.
Select Add Recipient again and select User or App.
To share data to a user, select User, then enter the Azure sign-in email address of who you want to share data with. By default, the option to enter email address of user is shown.
To to share data with a service principal, select App. Enter the object ID and tenant ID of the recipient you want to share data with.
Optionally, you can specify an Expiration date for when to terminate the share. You can share the same data with multiple recipients by clicking on Add Recipient multiple times.
When you're finished, select the Add recipients confirmation button at the bottom of the page.
Save all your changes by selecting the Save button.
Delete share
To delete your share, on any tab in the edit share page, select the Delete share button.
Confirm that you would like to delete in the pop-up window and the share will be removed.
Troubleshoot
Here are some common issues for sharing data and how to troubleshoot.
Can't create Microsoft Purview account
If you're getting an error related to quota when creating a Microsoft Purview account, it means your organization has exceeded Microsoft Purview service limit. If you require an increase in limit, contact support.
Can't find my Storage account asset in the Catalog
There are a couple possible reasons:
- The data source isn't registered in Microsoft Purview. Refer to the registration steps for Blob Storage and ADLSGen2 respectively. Performing a scan isn't necessary.
- Data source is registered to a Microsoft Purview collection that you don't have a minimum of Data Reader permission to. Refer to Microsoft Purview catalog permissions and reach out to your collection admin for access.
Can't create shares or edit shares
- You don't have permission to the data store where you want to share data from. Check the prerequisites for required data store permissions.
Can't view list of shares in the storage account asset
- You don't have enough permissions the data store that you want to see shares of. You need a minimum of Reader role on the source storage account to see a read-only view of sent shares and received shares. You can find more details on the ADLS Gen2 or Blob storage data source page.
- Review storage account prerequisites and make sure your storage account region, performance, and redundancy options are all supported.