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!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
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.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
| User | Count |
|---|---|
| 57 | |
| 43 | |
| 41 | |
| 22 | |
| 17 |
| User | Count |
|---|---|
| 183 | |
| 114 | |
| 93 | |
| 62 | |
| 45 |