Fabric workspace Connection Link (XMLA Endpoint) using Workspace ID instead of Name

[alfBI]

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.
Is that possible or should I propose an idea to MS?

Thanks

Alfons

[nilendraFabric · Accepted solution]

Hi @alfBI 

You cannot use the workspace ID in place of the workspace name in Fabric/Power BI XMLA Endpoint URLs. Connections must use the workspace name, which is case-sensitive

you should submit this as a feature request to Microsoft. This is not currently possible, and your scenario is a valid use case for such an enhancement.

[v-veshwara-msft]

Hi @alfBI ,

Thanks for raising this in Fabric Community Forum.

The XMLA endpoint for a workspace requires the workspace name in the connection URL and does not support using the workspace ID. The workspace name is case-sensitive and must match exactly, including spaces.

Semantic model connectivity and management with the XMLA endpoint in Power BI - Power BI | Microsoft...

There are no recent updates that change this behavior.

Thanks for submitting the idea to the Fabric Ideas portal. Encouraging others to vote will help bring visibility to this request.

Hope it gets more votes so that Microsoft will consider implementing this in future.

Hope this helps. Please reach out for further assistance.

Best Regards,
Vinay

[burakkaragoz]

Hi @alfBI ,

This is a super relevant topic for anyone managing Fabric workspaces, especially if you've ever struggled with workspace names that have spaces or special characters in XMLA endpoint URLs. Using the workspace ID instead of the name would make things so much smoother, especially for automation and scripting. Workspace names can be changed or get messy, but IDs are always unique and consistent.

At the moment, using the workspace ID directly in the XMLA endpoint URL isn't supported, but it really feels like a feature that should be standard. If this would make your life easier, definitely share your feedback and upvote this idea. The more real-world examples and requests Microsoft sees, the higher the chance they'll consider it for future updates.

If anyone here has found creative workarounds or knows a hidden trick, please share with the group. Would also love to hear if there are any updates from the product team.

Let's keep the discussion going. Having the option to use Workspace IDs in endpoint URLs would be a big improvement for managing Fabric workspaces, especially at scale.

[alfBI · Accepted solution]

Hi,

Idea has been added here

Fabric workspace Connection Link (XMLA Endpoint) u... - Microsoft Fabric Community

If someone thinks this might be useful please vote it!

Thx

[nilendraFabric · Accepted solution]

Hi @alfBI 

You cannot use the workspace ID in place of the workspace name in Fabric/Power BI XMLA Endpoint URLs. Connections must use the workspace name, which is case-sensitive

you should submit this as a feature request to Microsoft. This is not currently possible, and your scenario is a valid use case for such an enhancement.