Hello Community,

Has anyone come up with this error above?  The Cloud Services Team have provided me the following

Application (Client) ID

Secret Passphrase:

Directory (Tenant) ID

but can’t see where this goes in and if there is additional permissions needed on any accounts.

Setting Up an Application and Tenant for Azure Resource Manager (commvault.com)  Any help on this would be greatly appreciated.

thanks

TonyQ

Hi @TonyQ , I see you have a case for this with support now (I searched for the error and your case was the first hit ).

Looks like your support engineer found the log issue:

vsdiscovery.log

1520  30e4  10/13 20:00:16 4495491 Failed to get authorization token from Azure Active Directory MSI. Please ensure Azure MSI is enabled for all proxies
1520  30e4  10/13 20:00:16 4495491 Failed to connect to Azure. Please check Azure credentials

Have you checked these and confirmed this back to the case owner?

Hi Mike

I got it resolved in the end.  This was the update i gave the engineer was this:

“

Even though the logs said the following:

“1520  30e4  10/13 20:00:16 4495491 Connection failed - Response status code does not indicate success: 400 (Bad Request). 
1520  30e4  10/13 20:00:16 4495491 Failed to get authorization token from Azure Active Directory MSI. Please ensure Azure MSI is enabled for all proxies
1520  30e4  10/13 20:00:16 4495491 Failed to connect to Azure. Please check Azure credentials
1520  30e4  10/13 20:00:16 4495491 VSDisc::PrepareVMInfo() - Error Connecting - Failed to connect to subscription o2f84e126-7701-482c-9592-ddee6cc4439c\] with Azure Managed Identity enabled access node eaz-comma-lv1].  zFailed to get access token. Connection failed]

We don’t use Azure Managed identities.  It turned out quite simple in the end. The Application Subscription id Secret had expired.  Once this was renewed we got a successful backup and have since.