An Azure service that automates the access and use of data across clouds without writing code.
Hello Nate Chapman,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
I understand that you're having Service Disruption: OneDrive Delete Operation Failing in Azure Logic Apps (HTTP 502/500).
The failure is caused by a breaking change in the OneDrive Logic Apps connector, where the DELETE operation no longer correctly maps to the backend Microsoft Graph API. Evidence shows the OneDrive UI can still delete files, but Logic Apps DELETE calls return 500/502, confirming a regression in the connector layer rather than the service itself. See Graph API file deletion model: https://learn.microsoft.com/graph/api/driveitem-delete.
The best practice solution is to bypass the faulty connector and invoke Microsoft Graph DELETE directly through a Logic Apps HTTP action, which uses the supported API path. Retrieve the file ID (GET /me/drive/root:/path/to/file) and authenticate using Managed Identity or OAuth 2.0, then issue:
DELETE https://graph.microsoft.com/v1.0/me/drive/items/{item-id}
Add 3–5 retry attempts with exponential backoff per Azure Logic Apps guidance: https://learn.microsoft.com/azure/logic-apps/logic-apps-workflow-actions-triggers.
If Graph requests also fail, verify Microsoft 365 service health for OneDrive/SharePoint in the Admin Center, as backend outages can propagate to DELETE operations. For edge scenarios, validate file locks, version conflicts, or DriveItem states, although these are rare since UI deletion succeeds. Official service health and SharePoint backend behavior: https://learn.microsoft.com/microsoft-365/admin/service-health.
I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.