Fabric workspace Connection Link (XMLA Endpoint) using Workspace ID instead of Name
Dear colleagues,
As you already know Fabric workspace XMLA Endpoint (aka Connection Link) follows the format
powerbi://api.powerbi.com/v1.0/myorg/<workspace name>
where Workspace name can have spaces and is case sensitive. Example:
powerbi://api.powerbi.com/v1.0/myorg/ SAMPLE workspace
Our org aims to implement XMLA usage without workspace names dependencies (you know to avoid issue when someone simply changes the name of the workspace).
For that reason it would be useful to be able to access to the Workspace XMLA Endpoint using the Workspace ID instead of its name. This will prevent name dependencies on workspace name that currently. This dependency does not exist when using other Fabric artifacts (data pipelines, deployment pipelines, ) so it would take sense to avoid also this name-dependency here using the internal Workspace ID
Thx
Recent ideas
Allow Excluding Specific Tables or Columns from Automatic Relationship Detection
Power BI automatically detects and creates relationships between tables when data is loaded. While this is useful, there are scenarios where certain tables or columns are intentionally designed to re...MohamedFowzan13 hours agoSuper UserNew5Views0likes0CommentsHave a DIRECT way to reach the *Transform Data Button* from any menu.
Hi. Currently (2026), in PowerBI you have to go click the HOME menu, than click the Transform Data button, each time you want to reach the Query editor menu. Please either create a dedicated button /...MOFabric4 hours agoRegular VisitorNew6Views0likes0CommentsShow clickable links to dependent objects, aka a usable lineage
I have say 12 reports connected to a semantic model which I have just changed so I need to check if anything has broken. This use to be easy, just click the semantic model to see dependents but this ...skiwii6 hours agoAdvocate INew6Views0likes0CommentsexecuteDaxQueries-like API call with effectiveUserName on SSO-enabled model with Service Principal
Please provide a way for a service principal to execute DAX - with an effective user name - against an SSO-enabled directlake semantic model and get per-user results that respect lakehouse OneLake Se...sean_cochran7 hours agoResolver INew4Views0likes0Comments