Activity overview
Latest activity by leonorjon
Thanks for raising this question. I've seen similar behavior when moving from on-prem SQL Server to Azure SQL Database. Even when the schema is identical, differences in Microsoft Entra ID authentication, contained users, ownership chaining, and the EXECUTE AS context can affect how permissions are evaluated. It's also worth checking whether any dynamic SQL or views are involved, as those can bypass ownership chaining and require explicit permissions. For anyone comparing SQL Server and Azure environments, check here for more . Hopefully this helps others troubleshooting similar permission issues. / comments
Thanks for raising this question. I've seen similar behavior when moving from on-prem SQL Server to Azure SQL Database. Even when the schema is identical, differences in Microsoft Entra ID authenti...