@emma_s We are using a serverless cluster, but when my colleagues talk with copilot agent the cluster doesn't turn on / or simply answer if we already have the cluster on. 
We also had already provide permissions to the users to use the Warehouse, but it continues not working. 

Here’s the behaviour I’m observing:

• What Works:
• The user who created the agents, configured both connections (using oAuth and service principal), and published the agent (in Teams/M365) can interact with the agents without any issues.
• Other users tested genie inside the workspace and they have accees and can use it properly
• What’s Failing:
• Users who receive the shared agent are not able to interact with it.
• We have also tested by sharing the connectivity through the Power Apps connection but this didn’t work as well
• Workaround
• As part of the investigation, we asked one of the affected users to create the connection directly in Copilot Studio using their own identity. In this scenario, the user was able to interact with Genie successfully during the test. However, we don’t want to have to request every user to create manual connections to the workspace and cluster, and also this would require every user to have edit capabilities on coPilot

In summary:

The issue is with the shared agent using an existing connection—meaning the identity is not flowing through when the agent is shared, even though it works for the creator and for users who create their own connection.

Even when sharing the agent for development purposes, the users still cannot interact using the existing connectivity configuration.

Do you have more suggestions?