Resultado da Busca
28 de jun. de 2022 · My Azure AD login is within a group, other members of the group can login to the database, but I get the error '<token-identified principal>'. (Microsoft SQL Server, Error: 18456), however If the user is added to the database, then I can login and it works.
26 de mai. de 2020 · Even though same name you need to make sure SQL User SID match the AAD Object ID or Application ID (In case of Service Principal or MSI). To fix it you will need to recreate user and grant required permissions
16 de mar. de 2022 · I receive the "Login failed for user '<token-identified principal>'" error in my Web App logs. If I set the Web App directly as the Azure Active Directory Admin, it can log in successfully. I have installed the MSI Validator through the .scm.
10 de set. de 2022 · Regarding your ask for Error: Login failed for user '<token-identified principal>', it means the user is invalid, usually related to a AAD user that does not have user created on SQL DB that you are trying to connect (User DB or Master DB) or that the user is not the AAD Server Admin.
30 de ago. de 2023 · 'login failed for user '<token-identified principal>' The authentication type is 'Azure Active Directory - Universal with MFA Support' (and the 'Account' for the user is found), the database to access has been specified, Encrypt is set to true and the Trust server certificate is set to true.
8 de jul. de 2020 · Try to connect again using the same steps provided on the blog that I mentioned. But now check the option AD Domain Name or Tenant ID and type your AAD domain name that you can require from your AAD administrator. Why?
29 de abr. de 2023 · I hope you are trying to connect to Azure SQL using Azure AAD Universal MFA using SSMS. Please check the configuration steps mentioned in this document. If you have already followed the steps and still facing the issue please let us know and here are the troubleshooting steps which you can refer to. Regards. Geetha
