+1This 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?
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:
Application.ReadWrite.OwnedBy has been added under Microsoft Graph Application permissions and admin consent has been granted. 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.
Hope this helps.
+1We 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?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.