Skip to main content
Question

Sharepoint App Principal Missing

  • July 8, 2026
  • 7 replies
  • 104 views

KurtLO
Apprentice
Forum|alt.badge.img+4

Over the weekend, we started seeing errors in SharePoint online backups for all the tenants we backup with the error: “ Failed to validate any of the configured Azure Apps against the SharePoint Tenant Admin site. 1) Please verify the SharePoint Tenant Admin Url. 2) Please check the credentials and permissions for the configured apps. 3) Please ensure Custom App authentication is enabled on the SharePoint tenant.<br/>Source: xx, Process: SharePoint”

From logs on the Access Node:

CheckOffice365CredModern - Office365 app credentials incorrect : 
CheckOffice365CredModern - Error is: The remote server returned an error: (401) Unauthorized.

 

What we have done

  • Verified the Azure App secrets are not expired
  • Verified DisableCustomAppAuthentication on the tenant is set to false
  • Verified Azure app API permissions:
    • Microsoft Graph:  Application.ReadWrite.All, Application.ReadWrite.OwnedBy,  Directory.Read.All, Group.ReadWrite.All, Policy.Read.All, RoleManagement.ReadWrite.Directory, Sites.FullControl.All, Sites.Read.All, User.ReadWrite.All
    • SharePoint: Sites.FullControl.All, User.Read.All

I understand that Microsoft has deprecated ACS authorization and that new Graph APIs are required, but those permissions have all been granted per https://kb.commvault.com/article/?id=83163

I have also checked https://kb.commvault.com/article/?id=84896 and for versions 11.34 and earlier is states “With this value set to false you can now create App Registrations for SharePoint Online without the need of a certificate” (which we have set). Unfortunately, we aren’t able to upgrade to 11.36 due to other dependencies.

We have opened a ticket with support and they have told us this is due to the ACS deprecation. Why would this start occurring now, and not April 2nd?

7 replies

Paul G
Explorer
Forum|alt.badge.img+2
  • Explorer
  • July 10, 2026

Hi ​@KurtLO,

I had this issue as well for about 10 customers in our MSP platform (out of about 30). I don't know why this is becoming an issue at this moment but I was able to fix it. It seems that this was caused by azure apps not having certificates associated. By reapplying certificates, backup worked once more.

This was visible when verifying connection in the SharePoint connection settings in the SharePoint application configuration tab. We got a message that certificates were not available or incorrect. After that check was performed, the status of the azure apps changed to "invalid certificate”.

Using the option "Generate certificate” for each azure app, the certificates were rectified and backups started working once more. I did see that in some cases I had to perform this action twice or sometimes it took a long time before connection verification did work once more.

This did not happen for all customers. It could be that those azure apps were never created with certification authentication and Microsoft now enforces this but I am not sure if this has been an requirement sinds the beginning. For customers where we performed a manual certificate refresh, we did not see any previous certificates associated to the azure apps.

Manually creating and adding certificates: Create an Azure Certificate for SharePoint Online

I hope this helps.

Kind regards,

Paul G


KurtLO
Apprentice
Forum|alt.badge.img+4
  • Author
  • Apprentice
  • July 14, 2026

Thanks ​@Paul G. We upgraded to 11.36 yesterday and generated certs for all the Azure apps. They now show ‘Authorized’ after we verified connection, but only 3 out of the 9 Sharepoint Online clients started working after that.

 

For the ones failing, we are still seeing the same errors.


Paul G
Explorer
Forum|alt.badge.img+2
  • Explorer
  • July 14, 2026

Hi ​@KurtLO,

That is too bad but at least 1/3 of the issue has been resolved.

Are you sure the status is still authorized? I had the issue where I had to generate the certificate multiple times before it stuck. You also may need to remove the additional setting that allowed you to create the azure apps without certificate. That may cause interference.

To verify you can always test with manual certificate generation and applying those certificate files yourself.

Kind regards,

Paul G

 


KurtLO
Apprentice
Forum|alt.badge.img+4
  • Author
  • Apprentice
  • July 14, 2026

I believe I found the issue. Some of the Access Nodes for the Sharepoint Online clients were still not updated to 11.36, and on initial testing after update it resolves the issue.


  • Novice
  • July 16, 2026

Hello,
I have the same issue with a customer (beginning weekend of 5th July 2026, as with your issue).
We tried to Generate certificate as Paul mentions, but though I get the message, that certificate had been generated and uploaded, no certificates appear in Azure portal, nor does connection work between CommCell and Sharepoint Online.
I DO see the Authorization Status as “Authorized”, though.

Yesterday, I upgraded whole environment to latest and greatest 11.44.9, but still no success.
Any other ideas?

Thanks a lot,
Ollie


Paul G
Explorer
Forum|alt.badge.img+2
  • Explorer
  • July 16, 2026

Hi ​@Obelino,

Do you get an error message when verifying connection in the SharePoint application configuration tab? Once you have done so, you sometimes need to refresh the results in the azure app table so you can get the actual status per azure app.

It is more work but you can also generate the certificates manually and upload them to your azure apps and Commvault-side configuration. If this is just an certificate issue, this should resolve your issue as well. Be aware that you also need to enter your azure app secret when adding the certificate in Commvault so make sure you either look it op or generate a new secret.

Manually creating and adding certificates: Create an Azure Certificate for SharePoint Online

Kind regards,

Paul G


  • Novice
  • July 16, 2026

[...]

It is more work but you can also generate the certificates manually and upload them to your azure apps and Commvault-side configuration. If this is just an certificate issue, this should resolve your issue as well. Be aware that you also need to enter your azure app secret when adding the certificate in Commvault so make sure you either look it op or generate a new secret.

[...]

Hello Paul,
thanks for your fast reply. I think the issue was that the Azure App in Command Center was set to apllication secret (without certificate) and the option was greyed out.
I now tried the manual way you suggested, deleted the existing app and created new one with same tenantID, ApplicationID, secret, also uploaded .pfx certificate with matching password to Command Center and public .cer certificate to Azure Portal.

However, I still get “Failed to get access token, please check azure app details Certificate: Failed to get access token using certificate, please check certificate details” when verifying connection.

I am opening a support ticket with our distibutor now.

best regards,
Ollie