The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
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.