Perform on my Microsoft Fabric tenant a “fine” Licensing (Power BI : PRO/PPU) tracking

It’s no longer a mystery now, you all know Power BI PRO and PPU licenses will see their prices increasing next year

Wouldn’t it be time to do a bit of cleaning up after 5 years of distributing these 2 types of licenses ?

Obviously , YES ne need to

Everything will start with the collection of activities in power BI

Depending on whether you are on Microsoft Fabric architecture or on Bigquery or one Snowflake here is more or less the process to ingest and offer SQL gold historical data

MS Fabric
Bigquery or Snowflake

Basically we perform the API results ingestion in a Data Warehouse or in a Lakehouse

https://learn.microsoft.com/en-us/rest/api/power-bi/admin/get-activity-events

Ingest day by day, ideally to rely on 3 months of history

ETC. ETC. Store data on your SQL domain data product

Et voila ? no , go head with 3 mandatory lists ingestion on your SQL domain data product


First one : Ask your Entra ID colleagues to regularly provide you with the list of Power BI user licenses (focused PRO and PPU types)

Don’t forget the allocation date to benefit from enough perspective for usage statistics

ETC. ETC. Store data on your SQL domain data product

Second one , the most important and “diplomatic” concerns the type (qualification) of operations in activity events

Are we in the presence of a PRO and/or PPU (PRO overloaded) type operation ?

Kindly ask Microsoft for this list

ETC . ETC. Store data on your SQL domain data product

Super Early Bird
Third step consists on get your Workspaces metadata information with Power BI Admin Scanner API (run on a python script) or on a pyspark notebook (semantic-links-labs library)

ETC. ETC. Store data on your SQL domain data product

Normally , on a SQL data point of view normally , now everything is OK

Jump to a Power BI semantic model to create 5 KPI by user (upn)

KPI DAX measures used to qualify PRO users

Count1 = count events(activity rows) when the Workspace is stored on a F (>= 64) capacity and operations flag = “PRO”

Count2 = count events(activity rows) when the Workspace is not stored on a F (>= 64) capacity and type is not personal WS <=== 💡🚀 Urgent : Propose to migrate the WS to a F (>= 64) capacity

Count3 = count events(activity rows) when the PRO qualified operations are not linked a WS (like on premise gateway management)

Business rules :

ETC. ETC.

KPI DAX measures used to qualify PPU users

Count4 = count events(activity rows) when the Workspace is not stored on a F (>= 64) capacity and type is not personal WS and the operation need a PPU license

<=== 💡🚀Urgent : Propose to migrate the WS to a F(>=64) “pay as you go” capacity – on/off capacity during the day

Count5 = count events(activity rows) when the PPU qualified operations are not linked a WS (like ?)

Business rules :

ETC. ETC.

Create now a report live connected to the PBI semantic model (belongs a domain data product)

About the Author

👉 Christophe Hervouet
 

Ingénieur Analytique / Lead tech / Expert ==> Microsoft BI ( Fabric et Power BI) && Data Analyste GCP Bigquery et DBT cloud && Conseiller DATA (organisations , gouvernances , architectures)

Reference:

Hervouet, C (2025). Perform on my Microsoft Fabric tenant a “fine” Licensing (Power BI : PRO/PPU) tracking. Available at: Perform on my Microsoft Fabric tenant a “fine” Licensing (Power BI : PRO/PPU) tracking | LinkedIn [Accessed: 11th March 2025].

Share this on...

Rate this Post:

Share:

Tags: