Differencies between Synapse Administrator and Synapse SQL Administator roles to access a serverless SQL pool

Question

Hi,

in the same tenant/subscription I can use two Synapse Analytics workspaces, asaws1 and asaws2. For both workspaces my Microsoft Entra user (with MFA) is a Synapse Administrator.

Using Synapse Studio or SSMS, I can access to the asaws1 serverless SQL pool successfully, but I cannot access to the asaws2 serverless SQL pool. If I add my user to the Synapse SQL Administrator role for asaws2 workspace I can access to the related serverless SQL pool without any problems.

The asaws1 workspace is more recent than the asaws2 one. Are there recent changes about the Synapse Administrator and Synapse SQL Administrator roles?

Is the Synapse SQL Administrator role a complementary role than the Synapse Administrator role?

I know that the Synapse Administrator role includes all Synapse SQL Administrator permissions and according to this article How to set up access control for your Azure Synapse workspace
Now, any suggests to me in order to solve a such issue, please? Thanks

Answer 1

Sometimes, role assignments and the associated permissions might not propagate immediately across all resources in the Azure environment. This could lead to temporary access issues. However, this should resolve itself over time or after a manual refresh.

There may be specific configurations or security settings in the older asaws2 workspace that prevent the Synapse Administrator role from inheriting the necessary SQL permissions. These could include custom RBAC configurations, security policies, or inherited permissions from other Azure resources that override default settings.

If you're still facing issues, use Azure Monitor or the logs feature to track any access errors or permission denials when you try to connect to the asaws2 serverless SQL pool. This can give you more specific information about what's blocking access.

If the issue persists and everything seems to be configured correctly, it might be worth reaching out to Microsoft Support to report the problem. They can check for any backend issues or provide more detailed diagnostics.