Principal could not be resolved. . ms/sqlaadsetup)' Feb 15, 2022 · CREATE USER [name of account] FROM EXTERNAL PROVIDER Returns this Principal 'name of account' could not be resolved. $mdInfo += "The following scoped assignments reference application or service principal objects that could not be resolved:`n`n" $mdInfo += "| Principal | Type | Scope Target Kind | DirectoryScopeId |`n" Feb 18, 2022 · Hi All, I have an Azure Logic App with a system managed identity enabled that requires access to 2 Azure SQL databases. Error message: 'Server identity is not configured. I was able to grant the Apr 20, 2023 · Principal ‘xyz’ could not be found or this principal type is not supported. This can be checked from Azure portal -> Azure SQL server or Managed instance -> Azure Active Directory Admin (as below): May 7, 2020 · Msg 33159, Level 16, State 1, Server <SERVER_NAME>, Line 1 Principal '<PRINCIPAL_NAME>' could not be created. This can be checked from Azure portal -> Azure SQL server or Managed instance -> Azure Active Directory Admin (as below): Oct 8, 2017 · Perhaps one of the most useful features at your disposal when working with Azure SQL Databases is the ability to integrate your Azure Active Directory (Azure AD) login accounts, a la Windows Authentication for on-premise SQL Server. Error message: ‘%ls’” in Microsoft SQL Server, the reason why it appears and the solution to fix it. Quick notes before we start, please make sure you have an AAD admin set to your Azure SQL. Read on for several reasons why things might be going wrong.