In our on-premise database, we create database users mapped to a login, and then assign the user to specific roles within the database. Access to the database is strictly governed by which stored procedures each role has EXECUTE permissions on. The user has no other rights other than by stored procedure grants (e.g. they cannot run arbitrary select statements in SSMS).
I notice that SQL Server (on-premise) provides a default user assignment to the server's "public" role. When assigning user access to a SQL Azure server however, I do not see the "public" role. However, I must select a role in order to create the user:
Can anyone please advise what I should do here to honour our existing approach, or whether the on-premise approach is even still possible?
I cannot find any documentation to describe what privileges are granted from the roles listed.