Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Apologies in advance as I am sure this question has probably been asked and answered, but I am having trouble finding examples that match my use case.
My org uses a SaaS project management service which does not have very robust reporting capabilities, but it offers a data warehouse solution that allows us to export all of the data so we can report on it using an 3rd party BI tool.
The SaaS service provides us with a daily dump of data that we want to bring into Azure where we can report on it. We would have 3 people building reports and another 3 people that need to have access to run the reports.
From what I have read, I believe the 3 people building reports would need pro licenses, as would the 3 people running reports. So that's 6 pro licenses. On top of that, I assume I need some sort of Azure SQL DB / storage to hold the data itself, and potentially some sort of consumption / capacity licensing for the actual reporting service?
Solved! Go to Solution.
In a perfect world, you could connect directly to the SaaS project management tool instead of exporting and loading but let's assume that's out of the question. It doesn't really affect the licensing situation anyway.
There are two ways that licensing works. Either everyone has a license (including builders and users) or else you buy a premium capacity license. The latter usually doesn't make sense for just a few people (though Premium Per User might).
So you're looking at 6 licenses. The Power BI Service is included with this, so you don't have extra consumption / capacity licensing beyond whatever you'd be paying for Azure SQL DB.
In a perfect world, you could connect directly to the SaaS project management tool instead of exporting and loading but let's assume that's out of the question. It doesn't really affect the licensing situation anyway.
There are two ways that licensing works. Either everyone has a license (including builders and users) or else you buy a premium capacity license. The latter usually doesn't make sense for just a few people (though Premium Per User might).
So you're looking at 6 licenses. The Power BI Service is included with this, so you don't have extra consumption / capacity licensing beyond whatever you'd be paying for Azure SQL DB.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.