Skip to main content
Question

MS365 Application.ReadWrite.OwnedBy

  • Oct 27, 2026 7:37 AM UTC
  • 5 replies
  • 47 views

Unique display name
Apprentice
Forum|alt.badge.img+1

This feature, apps can rotate their own secrets by adding Application.ReadWrite.OwnedBy and give service principal owner permissions - is there any way to verify this is working?

It doesn’t seem to be a part of the “verify connection” feature in the job configuration.

btw, are they still called azure apps, or entra apps now? or something else?

 

https://documentation.commvault.com/11.46/software/request_and_grant_permissions_for_azure_apis_for_onedrive_for_business.html

5 replies

Unique display name
Apprentice
Forum|alt.badge.img+1

11.44.25 btw


Unique display name
Apprentice
Forum|alt.badge.img+1

❓
(11.44.29 now btw)


Forum|alt.badge.img
  • Vaulter
  • Nov 11, 2026 1:07 PM UTC

Hi,

Application.ReadWrite.OwnedBy is used for automatic secret key rotation. The Commvault documentation also notes that you may need to configure the application as an owner of itself when using this functionality. 

I wouldn't rely on Verify connection alone to validate the automatic secret rotation configuration. I would also verify in Microsoft Entra ID that:

  1. Application.ReadWrite.OwnedBy has been added under Microsoft Graph Application permissions and admin consent has been granted. 
  2. The application/service principal ownership is configured as required. Microsoft Learn confirms that this permission allows an application to manage applications that it owns. 
  3. Ultimately, successful automatic credential rotation would provide the end-to-end validation that the configuration is working as expected.

Regarding the terminology, Microsoft Entra ID is the current name replacing Azure AD. 

Commvault is updating terminology in its documentation, but you may see both "Azure AD" and "Entra ID" referenced interchangeably for some time. The technical configuration steps and concepts remain the same regardless of the naming.


https://documentation.commvault.com/11.46/software/request_and_grant_permissions_for_azure_apis_for_onedrive_for_business.html

Hope this helps.


Unique display name
Apprentice
Forum|alt.badge.img+1

We manage our customers’ Commvault, not their Azure/Entra environments, so we do not have access to see anything on that end.

So there is no way from the Commvault interface to test or make sure the Application.ReadWrite.OwnedBy is set properly, and that it is actually rotating secrets. Is that what you are saying?


Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 2:09 PM UTC

Hi,

Yes, with one clarification.

Commvault documents Application.ReadWrite.OwnedBy as required for automatic key rotation and notes that the application may need to be configured as an owner of itself. 

The 11.44 Verify Connection functionality checks Azure application permissions/status, but I could not find documentation confirming that it specifically tests Application.ReadWrite.OwnedBy, validates the ownership relationship, or performs an actual secret rotation.

Because of that, I would not consider a successful Verify Connection alone as proof that automatic secret rotation is working.

Since you don't have access to the customer's Entra environment, their Entra administrator would need to confirm the permission, consent and ownership configuration. From the Commvault side, a successful automatic rotation followed by continued Microsoft 365 authentication/protection would provide practical end-to-end confirmation.

I also couldn't find a documented 11.44.x option to trigger secret rotation on demand. If anyone is aware of a specific Commvault diagnostic/log or workflow that can validate the rotation without waiting for the scheduled rotation, that would be useful to confirm.

Regards,
Karthick