An Azure relational database service.
Login Issues with SQL Authentication After Enabling Entra ID Authentication
Previously, SQL Server was authenticated using SQL authentication, and I enabled Microsoft Entra ID authentication to allow direct connections to the database via SSMS. I implemented Entra ID authentication without removing the existing SQL authentication user accounts. However, after enabling Entra ID authentication, some login issues occurred with the existing SQL authentication users.
Are there any known issues or reports related to this, or is it possible that enabling Entra ID authentication could affect existing SQL authentication users?
I executed the following queries:
- In the master database and each respective database: CREATE USER [****@def.com] FROM EXTERNAL PROVIDER;**
- In other databases (but not in the master database): EXEC sp_addrolemember N'db_datawriter', N'******@def.com'; EXEC sp_addrolemember N'db_datareader', N'******@def.com';
Azure SQL Database
SQL Server | Other
Additional SQL Server features and topics not covered by specific categories