Forum Discussion
Clarification on Access Control for SQL Endpoints in Fabric Workspaces
Hi AndyDDC,
Thank you for your detailed explanation and walkthrough! Your solution was actually my first approach since it really makes sense that users can be added to the SQL Endpoint without being part of the workspace permissions.
However, I ran into the following issue when attempting to connect to the SQL Endpoint using SQL Server Management Studio (SSMS):
Error message:
After investigating further, I found that the only way to resolve this issue was to add the user to the workspace. To double-check, I reviewed the documentation, YouTube videos, and discussions, and these sources confirmed that adding the user to the workspace is required.
My question to you is: Have you verified that it actually works for you in practice to add users to the SQL Endpoint without including them in the workspace? Or did you, like me, make the assumption that it should work based on the design?
Thanks again for sharing your solution! It would be very interesting to hear if you've successfully managed to get this working without workspace permissions.
Can you point me towards documentation/videos that state that users need to be added to Workspaces? I have confirmed that adding users to a workspace is not required, I have tested this myself with both SSMS and browsing the OneLake catalog.
What version of SSMS are you using?
- SwedishJAS1 year agoRegular VisitorA big thank you to both of you—I’ll give it another shot next time. This time, I worked around the issue by creating a dedicated workspace for a SQL endpoint. I’m glad that a dedicated Fabric capacity is no longer required. 🙂
I trust your explanations, and that does seem like the most reasonable scenario. I couldn’t find the description I initially interpreted as confirming the worse situation—it might have been incorrect or outdated.
Thanks again for your quick and detailed responses!
/Jens