Overview
This Knowledge Base article addresses issues related to Microsoft Teams backups that fail with "Permission Denied" and an error code 404. The error typically occurs when the backup job is unable to read files or fetch metadata via the Microsoft Graph API. The error message indicates that the requested API path is not supported, which is symptomatic of a permissions issue.
Error Description
Backup time: Apr 27 2026 03:48, Reason: Unable to read file. Permission Denied Response Code: 404 Text:{"error":{"code":"NotFound","message":"Requested API is not supported. Please check the path.","innerError":{"date":"2026-04-27T03:48:21","request-id":"e8e3e8fd-3c29-464e-81a1-7e66ac996c10","client-request-id":"c6a440b8-fb66-4dc7-8165-5701c8dd1bf6"}}}Cause
The error arises when the Microsoft Graph API fails with a 404 response ("Requested API is not supported") combined with a "Permission Denied" message while attempting to access or read files within Teams.
Reason
This typically occurs due to missing or insufficient Microsoft Graph API permissions assigned to the configured Microsoft 365 admin account or the backup application. In Microsoft Graph, lacking the required scopes for a specific Teams endpoint can result in the API rejecting the path as "not supported" (404) rather than throwing a standard access denied (403) error. Note that some backups might intermittently succeed after retries, but recurring failures indicate a persistent permission gap.
Reference Article
For additional information, refer to the Druva Help Article on Microsoft 365 Permissions for Druva App.
Resolution Steps
Audit Application Permissions: Check the Microsoft 365 app configuration in your tenant. Verify that all required Microsoft Graph API permissions related to Microsoft Teams (such as reading files and channels) are properly assigned and consented to.
Reconfigure App with Global Admin: If Teams-related Microsoft Graph API permissions are missing, reconfigure the Microsoft 365 app integration. Ensure you perform this action using a Global Admin account so the correct permissions and admin consent can be successfully applied to the tenant.
Monitor Backup Jobs: If you have noticed that some backups succeed upon automated retries, you may choose to monitor the environment. Keep a close eye on the backup statuses over the next few backup cycles.
Re-run the Backup: If failures reoccur, execute step 2 to ensure permissions are corrected, then manually initiate a backup and review the results.
If you continue to experience issues or need further assistance, please contact Druva support for additional help.