Forum Discussion

alfBI's avatar
alfBI
Icon for Responsive Resident rankResponsive Resident
1 year ago
Solved

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...
workspaces
  • nilendraFabric's avatar
    nilendraFabric
    1 year ago

    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.

     

burakkaragoz's avatar
burakkaragoz
Icon for Super User rankSuper User
1 year ago

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.