Skip to main content
commvault.com commvault.com
Answer

Azure App identifier was not found in the directory

  • January 14, 2025
  • 2 replies
  • 553 views
Ken_H
Byte
Forum|alt.badge.img+15

My OneDrive backups have stopped working because the five App / Secret Key combinations I had set up expired. I created new App / Secret keys and deleted the old expired ones from in Azure. I then signed on to CommandCenter, navigated to Protect > Office 365 > OneDrive_V2 > Configuration, added the new App / secret key values and deleted the old. When I click “Verify connection”, I get:

The application wasn’t found in the directory/tenant. ErrorCode: AADSTS700016

Does anyone know where the problem is?

Best answer by Ken_H

I managed to get my OneDrive backups working yesterday but forgot to update this post. - my apologies for the delay.

The confusion is that there are several different Microsoft character strings that are involved and the naming is inconsistent between Microsoft and CommVault.

First, I needed to go into Microsoft Entra ID.  Two years ago this was named Azure Active Directory so right from the start there are struggles accessing the correct screens - thanks Microsoft. Once there, I generated new secret keys for the apps used by CommVault to do OneDrive backups.

Next, I connected to Command Center and navigated to Protect > Office 365 > OneDrive_V2 > Configuration (tab) > OneDrive Connection Settings (tile). After clicking Add Azure app, I selected Custom configuration and entered the Value from Azure into the Application ID field, and entered the Secret Key from Azure into the Application Secret field. This is the attempt that gave the ErrorCode: AADSTS700016 error. Further digging found the CvCloudBkup (not 100% certain on that name) log file contained the following.

Failed with exception [AADSTS700016: Application with identifier '<Azure GUID>' was not found in the directory '<Corporate Azure Account>'].

My second attempt was to return to add an Azure app but this time enter the Application (client) ID from Azure into the Application ID field and entered the Secret Key from Azure into the Application Secret field. This got rid of the ‘Application not found in directory’ message but still failed to connect to Azure to allow backups.

By this point I’m looking at trying every possible permutation and combination of values from Azure into CommVault to see if I can find one that works. Once again, I return to Command Center and try to add an Azure app but this time enter the Application (client) ID from Azure into the Application ID field and entered the Value from Azure into the Application Secret field. This final attempt was successful and my OneDrive backups are running once again.

Thank you ​@Ponte_Vedra for the reply. I don’t understand what your reply references and it doesn’t appear to be applicable to my problem but I appreciate the effort.

Ken

2 replies

P
Byte
Forum|alt.badge.img+5
  • Ponte_Vedra
  • Byte
  • January 15, 2025

I had this error last year and it was do to using a service account for credentials that in turn was using the PnP Management Shell application in Azure.

Microsoft removed the built-in multi-tenant PnP Management Shell Entra App on September 9, 2024. As a result, you now need to register your own app in Entra to use PnP PowerShell.

The error message you might see is: AADSTS700016: Application with identifier 'XXX' was not found in the directory.

Unfortunately, Microsoft hasn’t yet notified admins via MessageCenter, and this change impacts all code and existing scripts. To get back on track, register an app in Entra ID for PnP PowerShell.

I updated PnP PowerShell module to the latest and it then gave a much better description of the issue when trying to connect:

As of September 9th, 2024 the option to use the PnP Management Shell app registration for authentication is not available anymore. Refer to https://pnp.github.io/powershell/articles/registerapplication.html on how to register your own application.

So looks like we'll need to register our own Entra ID Application to use with PnP PowerShell instead.
And use something like this:

PowerShellCopy

Connect-PnPOnline -Url $AdminCenterURL -ClientId $ClientID -ClientSecret $ClientSecre
Ken_H
Byte
Forum|alt.badge.img+15
  • Ken_H
  • Author
  • Byte
  • Answer
  • January 15, 2025

I managed to get my OneDrive backups working yesterday but forgot to update this post. - my apologies for the delay.

The confusion is that there are several different Microsoft character strings that are involved and the naming is inconsistent between Microsoft and CommVault.

First, I needed to go into Microsoft Entra ID.  Two years ago this was named Azure Active Directory so right from the start there are struggles accessing the correct screens - thanks Microsoft. Once there, I generated new secret keys for the apps used by CommVault to do OneDrive backups.

Next, I connected to Command Center and navigated to Protect > Office 365 > OneDrive_V2 > Configuration (tab) > OneDrive Connection Settings (tile). After clicking Add Azure app, I selected Custom configuration and entered the Value from Azure into the Application ID field, and entered the Secret Key from Azure into the Application Secret field. This is the attempt that gave the ErrorCode: AADSTS700016 error. Further digging found the CvCloudBkup (not 100% certain on that name) log file contained the following.

Failed with exception [AADSTS700016: Application with identifier '<Azure GUID>' was not found in the directory '<Corporate Azure Account>'].

My second attempt was to return to add an Azure app but this time enter the Application (client) ID from Azure into the Application ID field and entered the Secret Key from Azure into the Application Secret field. This got rid of the ‘Application not found in directory’ message but still failed to connect to Azure to allow backups.

By this point I’m looking at trying every possible permutation and combination of values from Azure into CommVault to see if I can find one that works. Once again, I return to Command Center and try to add an Azure app but this time enter the Application (client) ID from Azure into the Application ID field and entered the Value from Azure into the Application Secret field. This final attempt was successful and my OneDrive backups are running once again.

Thank you ​@Ponte_Vedra for the reply. I don’t understand what your reply references and it doesn’t appear to be applicable to my problem but I appreciate the effort.

Ken

Terms & ConditionsCookie settingsAccessibility statement