Comments
Sort by recent activity
Yes, SQL Server permissions can behave differently compared to Azure SQL Database, even when the schema looks the same. The main differences usually come from authentication models, ownership chaining, and security boundaries. In on-prem SQL Server, ownership chaining often allows stored procedures to access underlying tables without explicitly granting permissions, as long as they share the same owner like dbo . In Azure SQL Database, this behavior can be more restrictive, especially with contained users and Entra ID authentication. Another key point is that Azure SQL is designed with stricter isolation. Server-level roles are limited, and many permissions must be handled at the database level. Because of this, you may need to explicitly grant SELECT or EXECUTE permissions, even if things worked fine on SQL Server. To fix the issue, you can:
Grant explicit permissions on required tables
Use EXECUTE AS OWNER in stored procedures
Verify schema ownership and user mappings
These small differences often cause confusion, but testing with explicit permissions usually helps identify the exact problem quickly. For reference on mobile apps and tools, I came across Traffic Rider which is useful if you are exploring Android-based applications alongside your workflow. / comments
Yes, SQL Server permissions can behave differently compared to Azure SQL Database, even when the schema looks the same. The main differences usually come from authentication models, ownership chain...