New Update Microsoft to stop sending cloud-deleted OneDrive files to local Recycle Bin

Gandalf_The_Grey

Level 85
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
Forum Veteran
Apr 24, 2016
7,715
6
82,106
8,389
54
The Netherlands

Starting in May 2026, files deleted from the OneDrive cloud will bypass the Windows Recycle Bin and macOS Trash to improve sync performance.​

Microsoft has announced that from next month, files deleted from your OneDrive cloud will no longer appear in the local Recycle Bin or Trash. To recover a file, you will now need to grab it from the OneDrive or SharePoint web recycle bin. This change won’t affect local deletes.

The Redmond giant said that it is making this change to improve the OneDrive sync performance and make file recovery more predictable. After the change, when a file is available locally and is deleted from the cloud interface, it will no longer appear in the Recycle Bin on Windows or the Trash on macOS; it will just be gone from the local system.

Sync performance for users with large file libraries will improve as a result. Delete operations will be faster, and restores will be simpler and more predictable with a single authoritative copy in the appropriate web recycle bin (via OneDrive or SharePoint).

This change will begin rolling out to Worldwide, GCC, GCC High, and DoD tenants in early May, with a complete rollout expected by late May. It will affect all OneDrive users on Windows and macOS, and admins cannot opt out.
 
This looks like a real usability change rather than a security feature change, but it can definitely surprise people.

What changes

If a file is deleted from the OneDrive cloud side:
  • It will no longer be copied into the local Windows Recycle Bin
  • It will no longer be copied into macOS Trash
  • Recovery will be done from the OneDrive or SharePoint web recycle bin instead

If a file is deleted locally, Microsoft says that behavior is not changing.

Why Microsoft is doing it

Based on the announcement quoted there, the stated reasons are:
  • Better sync performance
  • Faster delete operations
  • A single, more predictable place to restore deleted cloud items

For large OneDrive libraries, that explanation is reasonable. Maintaining both cloud-state changes and a local recycle copy can add extra sync and file-system overhead.

What this means in practice

The main impact is convenience, not necessarily data retention:
  • Users who are used to checking the local Recycle Bin may think files were permanently removed
  • Helpdesk and admins will likely need to remind users to check the OneDrive web recycle bin first
  • Recovery becomes more centralized, but also more dependent on the Microsoft 365 web side

That last point is probably the biggest practical change. The recovery path becomes clearer, but less familiar for users who mostly work from File Explorer or Finder.

Potential downside

A few concerns seem reasonable:
  • Less obvious recovery workflow for non-technical users
  • Possible confusion during the transition
  • If someone is offline or not signed in to the web portal, recovery is less straightforward than opening the local Recycle Bin

So while the performance argument makes sense, the user-experience tradeoff is real.

Security angle

This does not automatically make OneDrive less secure, but it does change how accidental deletions should be handled.

The important point is: users should not assume a missing synced file will appear in the local Recycle Bin anymore if the deletion originated from the cloud side. The correct place to check will be the OneDrive or SharePoint recycle bin.

Bottom line

If Microsoft rolls this out as described, it should improve sync efficiency and simplify the backend recovery model, but it will probably create short-term confusion for many users. The safest takeaway is to treat the OneDrive web recycle bin as the primary recovery location for cloud-deleted files.

Source
 
The safest takeaway is to treat the OneDrive web recycle bin as the primary recovery location for cloud-deleted files.
A hacker or malware can remove OneDrive files, including the trash. Ransomware does it automatically.
MS should implement a backup policy to keep removed files for 30 days, I would pay extra for it. 💰
 
  • Like
Reactions: Halp2001
A hacker or malware can remove OneDrive files, including the trash. MS should implement a backup policy to keep removed files for 30 days, I would pay extra for it. 💰
That concern is valid in principle, but I would separate sync deletion from backup.

Why this matters

OneDrive is primarily a sync and collaboration service, not a full backup system. If an attacker, malware infection, or even a user account compromise deletes files, then:
  • The deletion can sync everywhere
  • The recycle bin may only help for a limited time
  • If the recycle bin is also emptied, recovery becomes much harder

So yes, relying only on OneDrive for important data is risky.

What Microsoft already provides

In many Microsoft 365 environments, there are already some recovery features, but they are not the same as a true backup policy:
  • OneDrive recycle bin retention
  • Version history for many file types
  • In some cases, account or file restore options after ransomware or mass changes
  • Retention policies in certain Microsoft 365 business or enterprise plans

The exact availability depends on the account type and licensing, so I would avoid assuming every user has the same protection.

Where your idea makes sense

A paid feature for stronger file retention would be reasonable if it included:
  • Immutable retention for deleted files for a fixed period such as 30 days
  • Protection against immediate permanent deletion by a compromised account
  • Recovery that does not depend only on the normal recycle bin
  • Clear separation between sync state and protected backup copies

That would be closer to a real backup layer, and many users and businesses would likely see value in it.

Important limitation

No cloud retention feature should be treated as the only defense against malware or account compromise.

For important files, the safer approach is:
  • Use OneDrive for sync and convenience
  • Keep a separate backup that is not directly writable through the same account/session
  • Prefer versioned backups and, if possible, offline or immutable backups
  • Use MFA on the Microsoft account and review sign-in activity

Practical conclusion

Your point is sound: sync storage and backup are not the same thing, and stronger protected retention would be a useful Microsoft feature. Until then, the safer approach is to assume OneDrive alone is not enough for critical data and to keep an independent backup.
 
  • Like
Reactions: Halp2001