Hi @Vivek Komarla Bhaskar
Thanks for the detailed explanation and for sharing your setup steps - that’s really helpful for understanding the issue.
You're correct in noting that group-based authentication with Azure Entra ID (formerly Azure AD) works smoothly with Azure SQL Database and SQL Server, but Azure Synapse Dedicated SQL Pools have some key limitations in this area.
- Azure Synapse Dedicated SQL Pools currently do not support group-based authentication directly in the same way Azure SQL Database does.
- While you can create logins and users from external providers, Dedicated SQL Pools require the login to be an individual Entra ID identity, not a group.
- This is why you're encountering errors like:
-
"Service Principal - login failed"
or -
"Login failed for user '<token-identified principal>'"
These typically appear when group-based access is attempted and the token identity doesn’t resolve as an individual user login within the pool.
-
Suggested Workarounds:
Use Individual Entra ID Users:
- Grant access to users individually (e.g.,
CREATE USER [******@domain.com] FROM EXTERNAL PROVIDER
). - This works reliably and is currently the supported pattern.
Automate Access Granting via Script:
- If managing many users, consider scripting the creation of users from a group list in Entra ID using PowerShell or CLI to keep it maintainable.
Log Feedback / Feature Request:
- Group-based authentication is a commonly requested feature for Synapse. You can upvote and track progress on Microsoft Feedback or escalate internally if needed.
If you're using SSMS or Synapse Studio, ensure you’re connecting using Azure Active Directory - Universal with MFA and not a service principal.
Also confirm that the user has been assigned the proper Synapse RBAC roles at the workspace level in addition to SQL roles.
Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer
and Yes
for was this answer helpful. And, if you have any further query do let us know.