Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hi,
I have a pro workspace with a dataset. My understanding was always that pro workspace datasets (semantic models ;D) could not be approached via API URL since for that you would at least need premium-per-user. I tested this behavior via SQL mgmt studio and Excel and indeed switching the workspace between PRO and PPU seems to either allow connections or not (though I did see some caching e.g. in Excel still could refresh the API connection to the dataset which had been downgraded from PPU to PRO).
But now I was meddling around with mixed models (Storage mode: mixed) and to my surprise you can just add DirectQuery connections that in fact underneath seems to use the API URL which is not available anymore because it's a PRO dataset now. This works when trying to visualize data based on it.
So my question: is this restriction then applied at Power BI service level? It gets an incoming query and detects if the source call comes from a Power BI environment: desktop, service, ... Or what do you think? 🙂
Thanks
This has always felt like an unnecessary arbitrary limitation. Not sure if caused by support volume or financial considerations. Good on you for finding cracks in that construct.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
78 | |
78 | |
59 | |
35 | |
33 |
User | Count |
---|---|
100 | |
62 | |
56 | |
47 | |
41 |