Current User is me in master, but dbo everywhere else

Question

Current User is me in master, but dbo everywhere else

Jim Graff 40

When I connect and run SELECT CURRENT_USER inthe master database, it yields '******@mycompany.com'. When I switch to another database, SELECT CURRENT_USER yields 'dbo'. What do I need to do to be the 'right' user in the other databases. Some things that may be important.

I am using the Microsoft Entra MFA authentication method
I am an admin on our virtual server
I have created a user for myself in the 'other' database

Saraswathi Devadula 9,370 Reputation points Microsoft External Staff Moderator

2025-07-28T03:02:13.2866667+00:00
Hello Jim Graff

In addition to Erland's post, please review the below information in Creating a login in Azure SQL allows users to authenticate and access databases. Below are the steps to create a SQL login using SQL Authentication.

Create SQL Login on master database (connect with admin account to master database):

CREATE LOGIN <login name> WITH PASSWORD = '<strong_password>';

Create SQL user on the master database, this is necessary for login attempt to the <default> database, as with Azure SQL you cannot set the DEFAULT_DATABASE property of the login so it always will be [master] database.):

CREATE USER <username> FROM LOGIN MaryLogin;

Create SQL User on the user database (connect with admin account to user database):

CREATE USER <username> FROM LOGIN MaryLogin;

Reference document: https://techcommunity.microsoft.com/blog/azuredbsupport/create-sql-login-and-sql-user-on-your-azure-sql-db/368813

Please do let us know if you have any further concerns. I am happy to address you.
Jim Graff 40 Reputation points

2025-07-28T13:14:00.2333333+00:00

Thanks for this. I had already created a login (in master only) and a user in both master and the database in question.

Accepted answer

0 additional answers

Your answer

Saraswathi Devadula 9,370 Reputation points Microsoft External Staff Moderator

2025-07-28T03:02:13.2866667+00:00

Hello Jim Graff

In addition to Erland's post, please review the below information in Creating a login in Azure SQL allows users to authenticate and access databases. Below are the steps to create a SQL login using SQL Authentication.

Create SQL Login on master database (connect with admin account to master database):

CREATE LOGIN <login name> WITH PASSWORD = '<strong_password>';

Create SQL user on the master database, this is necessary for login attempt to the <default> database, as with Azure SQL you cannot set the DEFAULT_DATABASE property of the login so it always will be [master] database.):

CREATE USER <username> FROM LOGIN MaryLogin;

Create SQL User on the user database (connect with admin account to user database):

CREATE USER <username> FROM LOGIN MaryLogin;

Reference document: https://techcommunity.microsoft.com/blog/azuredbsupport/create-sql-login-and-sql-user-on-your-azure-sql-db/368813

Please do let us know if you have any further concerns. I am happy to address you.
Jim Graff 40 Reputation points

2025-07-28T13:14:00.2333333+00:00

Thanks for this. I had already created a login (in master only) and a user in both master and the database in question.

Answer 1

Erland Sommarskog 123.5K MVP Volunteer Moderator

Because you are admin, you map to dbo in all databases. It is as simple as that.

Jim Graff 40 Reputation points

2025-07-28T13:17:42.46+00:00

That is unfortunate. If I create routines that but the Current_User in a column (like [Updated By]) I wouldn't want the ID to show 'dbo' after I run the routine. I think ultimately I will need to take myself out of the server admin group. Will test later
Erland Sommarskog 123.5K Reputation points MVP Volunteer Moderator

2025-07-28T13:32:56.8933333+00:00

Try using SYSTEM_USER instead. This gives you the login on server level. Also in Azure SQL Database.
Jim Graff 40 Reputation points

2025-07-28T13:39:48.5966667+00:00

Thanks

Share via

Current User is me in master, but dbo everywhere else

0 additional answers

Your answer