Graph API permanentDelete sends files to the SharePoint recycle bin

Question

Good afternoon.

We have a problem deleting files from SharePoint using Graph API.

The context is a document management application that externally handles files located on SharePoint sites. This application uses the endpoint ‘POST /drives/{drive-id}/items/{item-id}/permanentDelete’ to delete files from SharePoint without sending them to the first or second level recycle bin.

The problem is that we have detected that in massive executions (around 300K permanent delete requests) there are some cases (around 20 files) where files deleted with ‘POST /drives/{drive-id}/items/{item-id}/permanentDelete’ are sent to the SharePoint recycle bin (first or second level).

How is this possible? What is the internal operability of the endpoint?

Thanks in advance, Fernando

Answer 1

Hello Fernando J. Belizón,

Thank you for reaching out to Microsoft!!

For the issue mentioned when deleting the items from SharePoint, I tried replicating it and the items which are deleted permanently are not found in any of the recycle bins.

Please try again once in test environment and if the issue still persists, I recommend you raising a support case with Microsoft Graph, a Support Engineer will be able to look into this issue and assist you better. You can raise support ticket from New support request - Microsoft Entra admin center or https://admin.microsoft.com/#/support/requests.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.

Answer 2

If you test from Microsoft Graph with a single request you will not reproduce the problem. As I told you, the problem occurs in 20 requests out of 300000 requests launched in a massive process.

I will pass the problem to the Microsoft Graph team. Thank you.

Answer 3

If you test from Microsoft Graph with a single request you will not reproduce the problem. As I told you, the problem occurs in 20 requests out of 300000 requests launched in a massive process.

I will pass the problem to the Microsoft Graph team. Thank you.