Sharing Your Data Safely: A Guide to Microsoft Purview Data Sharing

In today's data-driven world, the ability to share information securely and efficiently is paramount. Whether you're collaborating with internal teams or external partners, knowing how to share data effectively can unlock new insights and drive innovation. Microsoft Purview offers a robust solution for this, acting as a central hub for data governance and, importantly, data sharing.

It's worth noting upfront that the specific Microsoft Purview data sharing feature discussed here is currently in preview and is slated for retirement in September 2025, with support continuing until then. The recommendation is to explore external data sharing within Microsoft Fabric as the future path. However, understanding the current Purview method can still be beneficial for immediate needs or for those migrating.

So, how does this work? At its core, Microsoft Purview data sharing allows you to share data directly from Azure Data Lake Storage (ADLS Gen2) to ADLS Gen2, and from Blob Storage to Blob Storage. Think of it as creating a secure, controlled channel for your data.

Before you can start sharing, there are a few prerequisites to get in order. On the Microsoft Purview side, you'll need an active Purview account. Within that account, you'll need at least a 'Data Reader' role on a Purview collection to manage sharing through the governance portal. If you're planning to use the SDK, you won't need these specific Purview permissions.

Crucially, you'll need the recipient's Azure sign-in email address, or their application's object ID and tenant ID. Just an email alias won't cut it – it needs to be the primary Azure identifier.

From the Azure Storage account perspective, things get a bit more involved. Your Azure subscription needs to be registered for the 'AllowDataSharing' preview feature. If you haven't done this, or if you're looking for the newer approach, Microsoft Fabric's external data sharing is the way to go. Alternatively, you might need to contact support to get this feature enabled.

The source storage account itself must be created after you've completed the registration step. It can reside in a different Azure region than your Purview account, but it needs to adhere to the available configurations. To initiate the sharing, you'll need to have the 'Owner' or 'Storage Blob Data Owner' role on that source storage account. This ensures you have the necessary permissions to manage the data being shared.

If your storage account is in a different Azure subscription than your Purview account, there's an extra step: the Microsoft.Purview resource provider needs to be registered in the subscription where the storage account lives. This usually happens automatically when you add a resource if you have the right permissions (like Contributor or Owner) on that subscription. This registration is a one-time thing for that subscription when you first share or receive data.

Finally, for sharing via the Purview portal, your storage account needs to be registered within a Purview collection. This helps Purview understand and catalog your data sources. Instructions for registering your data sources can be found in the ADLS Gen2 or Blob Storage documentation. Again, this isn't a requirement if you're using the SDK.

Once all the prerequisites are met, creating a data share is straightforward. You have two main avenues: directly from the data resource itself or through the dedicated Data Sharing application within Purview.

Sharing Directly from a Data Resource

If you're using the Purview Data Catalog (either classic or the newer portal), you can search for or browse to the specific Azure Storage or ADLS Gen2 resource you want to share. Once you've located it, you'll see a 'Data Share' button. Clicking this and then selecting '+New share' will guide you through the rest of the process.

Sharing from the Data Sharing Application

In the newer Purview experience, you can navigate to the Data Catalog, then select 'Shares,' and from there, click '+New share.' If you're on the classic Purview experience, you'll go to the Data Map, select 'Shares' from the left-hand navigation, and then click '+New share.'

Regardless of the method you choose, the process involves defining who you're sharing with and what specific data they'll have access to. It's about making your data accessible while maintaining control and ensuring compliance.

Leave a Reply

Your email address will not be published. Required fields are marked *