is the name of the managed identity in Azure AD. If you want, you can add the identity to an Azure AD group, then grant SQL Database access to the Azure AD group instead of the identity.ДЇor example, the following commands add the managed identity from the previous step to a new group called myAzureSQLDBAccessGroup: The application could fail while connecting to Azure SQL using MSI with the error message: The roles should be configured as per your application's use case. Navigate to the Access Control IAM) > Add Role assignment and choose the necessary storage related permission. Choose the Service Principal (name of the App Service).Navigate to the Access Policies Blade of KeyVault from the Azure Portal.KeyVaultДЇrom the below error message, we see that the App Service doesnвЂ™t have necessary permissions to access the KeyVault. Run the command 'msi-validator test-connection -r -e ' and check if data is returned from the resource or inspect the error message. Do you still face the issue if Managed Identity is disabled and enabled again ?.If Yes, is the device to which the traffic is force tunneled, blocking any Azure Active Directory Dependency ?

Does the App Service have regional VNet Integration / is the App in ASE?ДЄre there any User Defined Routes on the subnet to which the App Service is integrated ?.Otherwise, it indicates that MSI service has issues reaching out to Azure Active Directory to fetch a token. Run the command 'msi-validator get-token -r ' and check if a token is being returned. The Environmental Variables MSI_ENDPOINT and MSI_SECRET would have been set automatically.

Navigate to Kudu Console ( > Environment Section and search for MSI (Ctrl + F)

msi-validator.exe test-connection -r sql -e 'Data Source=. Initial Catalog= 'ДЇrom the Identity Blade of the App Service, ensure that Managed Identity is turned on.

msi-validator.exe test-connection -r storage -e.

msi-validator test-connection -r 'keyvault' -e '.

Valid Arguments for resource = keyvault, storage, sql

Rgh keyvault validator