An Azure relational database service.
Hello **Xhevahir Mehalla
**It looks like you’re running into two common issues when using MFA against an Azure SQL Database:
- Your client tool (SSMS) doesn’t fully support the “Azure AD – Universal with MFA” flow
- The Azure AD principal (user or group) hasn’t actually been provisioned in the database
Kindly please try to verify the below,
- Upgrade your client to a recent SSMS
- Install SSMS 22 (or at least SSMS 18.6+). Older SSMS versions use the “classic” auth dialog and won’t complete the Entra MFA flow correctly.
- SSMS 22 installs side-by-side, so you won’t lose your existing setup.
- Configure Azure AD admin on your SQL server
- In the Azure Portal, go to your SQL server resource → Active Directory admin → set yourself (or an Entra group) as the AD admin.
- This step ensures that MFA-based logins are allowed at the server level.
- Connect with the correct auth method
- In SSMS’s Connect dialog, set Authentication = “Azure Active Directory – Universal with MFA” (sometimes labeled “Microsoft Entra MFA”).
- Complete the browser-based MFA prompt; once it says “Authentication complete,” SSMS should finish connecting.
- Create your Entra users/groups in the database
- Connect as your AD admin, then run for each security group:
CREATE USER [******@contoso.com] FROM EXTERNAL PROVIDER; - Assign roles, for example:
ALTER ROLE db_datareader ADD MEMBER [******@contoso.com];
- Connect as your AD admin, then run for each security group:
- Verify and retry
- After that, try connecting as a member of that group. You should no longer see the 18456 error.
https://learn.microsoft.com/en-us/azure/azure-sql/database/active-directory-interactive-connect-azure-sql-db?view=azuresql
https://learn.microsoft.com/en-us/azure/azure-sql/database/authentication-aad-overview?view=azuresql
If this doesn't help, please share your more insights for further investigation.