Azure Purview – Enhanced Power BI Integration

It seems like it’s Azure Purview week – another feature enhancement made it to my Purview account. The enhanced metadata scanning for Power BI tenants.

The Power BI integration in Azure Purview was there since the first public preview in December last year. But the assets discovered only got down to the Power BI dataset, report and dashboard level.

With the introduction of the enhanced metadata scanning API in Power BI, well.. more details about your Power BI tenant can be queried through the REST API (announcement blog post). That enhancement to the Power BI APIS now allow Azure Purview to get more granular information out of Power BI.

How do you get this more detailed information? Well – I created a short video for you to demo the new functionality and the steps that are required to get Azure Purview talk well to Power BI.

Azure Purview and Power BI Integration

Configuration Steps:

  • Azure Active Directory
    • Create a Security Group and add the Azure Purview Service Principal to that group
  • Power BI Admin portal
    • Allow the Purview service principal to access the Power BI API (you’ll use the created security group)
    • Enable – Allow service principals to use read-only Power BI admin APIs, and Enhance admin APIs responses with detailed metadata
Configuration settings in the Power BI Admin portal – allow the security group (for Azure Purview) to use the Power BI metadata APIs
  • Azure Purview
    • Configure a Power BI source
    • Configure a Scan
    • Browse your Power BI assets

What is included in the (enhanced) Power BI metadata?

What I found out so far – For Power BI datasets, there are more properties extracted now:

Dataset properties including the “hierarchy” -> in this screenshot the dataset is published into a shared capacity (Power BI PRO)

Power BI dataset properties in Azure Purview
Properties part 2

This is the really new part – Power BI dataset schema information.

Initially during my first tests, the schema part of the Purview asset did not populate. Together with the Purview team, we could solve this.

🎯If no Power BI schema information is extracted into Purview, make sure that the Power BI dataset is at least – one time refreshed in the service. I uploaded my demo dataset without a refresh in the service afterwards. The refresh (and a following Purview scan) solved the population of the asset section.

What is really new: Schema information

You can even drill down to a specific column / measure of the dataset

What is missing (in August 2021 and for Wolfi πŸ™‚ ?

Well, there is always something that is missing.. πŸ™‚ What I found as a start:

  • Data Lineage is still available on the data set / report / dashboard level -> detailed (column level) lineage would be really, really nice… (nicely looking into the direction of the Purview product team πŸ™‚
  • What would help, maybe, would be the DAX formula for a Measure. There is already a flag isMeasure set to true, but the DAX formula is not extracted

How do you like the enhanced Power BI & Azure Purview integration? What is missing for you? Is it working for yourself?

Happy data cataloging,

Wolfgang

About wolfgang

Data Platform enthusiast
This entry was posted in Azure, Azure Purview, PowerBI. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s