Forum Discussion

Zicozen's avatar
Zicozen
New Member
7 months ago
Solved

Connection Access

I have created a blank new Workspace and I have created a feature branch in Azure DevOps. I now want to integrate my newly created Workspace with the feature branch. However I am getting the following error for a particular pipeline called Child - Ingest Data...

Cluster URI https://wabi-north-europe-i-primary-redirect.analysis.windows.net/

Request ID 15a006b0-38e8-481f-a190-6bb13c088c85

Workload Error Code RequestValidationFailed

Workload Error Message User does not have access to the connection used in the Pipeline. Please verify the user's permissions.

Time Wed Jan 07 2026 09:37:04 GMT+0000 (Greenwich Mean Time)


The Child - Ingest Data pipeline 

 

In another Workspace where this pipeline has been deployed, when I open up the pipeline, I see the following warning message...

You cannot access one or more connections used in this pipeline. You can either ask the pipeline owner to grant permissions to all connections used in the pipeline or choose other connections that you can access. 


I am struggling to understand the security model in Fabric related to connections and how it works and how I can resolve this moving forward with best practice recommendations

Thanks in advance

  • Hi there, this is extremely common in workspaces where the items and associated connections were first created with a service principal and then the branching off was done manually.

     

    First you can check to see if somebody has permissions to access the connection in "Manage connections and Gateways" and then see if they can assign you permissins.

     

    Ongoing, if the way to create the items is automated ensure the process also adds additional permissions to the connections. If done manually, ensure whoever adds them goes to "Manage connections and Gateways" and adds the relevant permissions.

    I hope this helps resolve your issues long-term.

7 Replies

  • Hi Zicozen

     

    You can use the Fabric REST API endpoints to check the connections an item is associated with followed by who's the owner of the connection. 

     

    GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}/connections

     

    GET https://api.fabric.microsoft.com/v1/connections/{connectionId}/roleAssignments
     
    You could then reach out to the owner and ask to grant you the required permissions. 
     
    Hope this helps - please leave a Kudos or accept as a Solution! 
     
  • Hi there, this is extremely common in workspaces where the items and associated connections were first created with a service principal and then the branching off was done manually.

     

    First you can check to see if somebody has permissions to access the connection in "Manage connections and Gateways" and then see if they can assign you permissins.

     

    Ongoing, if the way to create the items is automated ensure the process also adds additional permissions to the connections. If done manually, ensure whoever adds them goes to "Manage connections and Gateways" and adds the relevant permissions.

    I hope this helps resolve your issues long-term.

    • Zicozen's avatar
      Zicozen
      New Member

      Thanks for your response...it is much appreciated!

      The issue was that one of the developers created a few connections and did not share the connections with the security group for the development team. It meant that he was the only one able to sync his feature branch with his workspace and everyone else was getting the error I posted.

      Now I can sync my feature with my workspace successfully

      Thanks once again!

  • Hi Zicozen

     

    There are gateway or cloud connections in use that you don't have permissions on. 

    If they are cloud connections, ask the original author of the pipeline to share them with you. If they are gateway connections, you can ask the gateway admin to share them. 

     

     

  • Hi Zicozen 

    May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.


    Thank you