Skip to main content
Solved

Exchange backup, Reports.Read.All

  • Nov 3, 2026 12:23 PM UTC
  • 1 reply
  • 12 views

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

Is the permission Reports.Read.All required for the Exchange Online backup?

Permission is not in this list:
ttps://documentation.commvault.com/11.44/software/application_permissions_for_azure_app_for_exchange_online.html 

Permission is listed here:
https://documentation.commvault.com/11.44/software/request_and_grant_permissions_to_azure_apis_for_azure_app_for_exchange_online.html

So should it be added or not? What happens if it is not added? What is it used for?

 

Best answer by Jon Vengust

Hi,

 

Thanks for having this raised. As the name of the permission implies, not having this permission configured will result in the inability to read service usage and reporting data via the Graph API.

 

There is most likely delineation here between backup and restore requirements, and tertiary functionality. The first document states that the listed permissions “are required for Exchange Online backup and restore operations”. Whereas the second document instructs, we have further capabilities that users may wish to take advantage of such as reporting.

 

With this in mind, I would highly recommend configuring this permission as stated for reporting features to be available through the API set.

View original

1 reply

Jon Vengust
Vaulter
Forum|alt.badge.img+12
  • Vaulter
  • Answer
  • Nov 4, 2026 7:41 AM UTC

Hi,

 

Thanks for having this raised. As the name of the permission implies, not having this permission configured will result in the inability to read service usage and reporting data via the Graph API.

 

There is most likely delineation here between backup and restore requirements, and tertiary functionality. The first document states that the listed permissions “are required for Exchange Online backup and restore operations”. Whereas the second document instructs, we have further capabilities that users may wish to take advantage of such as reporting.

 

With this in mind, I would highly recommend configuring this permission as stated for reporting features to be available through the API set.