Accidental deletions in Dynamics 365 and Power Platform used to mean support tickets, environment restores or lost data. Restoring deleted Microsoft Dataverse records is now generally available, from late April 2026.
How it works
According to Microsoft:
- Keeping deleted records is managed at environment level through a single setting, which applies to all tables in that environment.
- Admins set a retention period of up to 30 days.
- Parent and child records are kept together, so related data can be recovered completely.
- Admins can purge everything, delete selectively and see how much storage deleted records consume in the Power Platform admin center.
Microsoft's documentation also notes that you can only restore records deleted after the setting is turned on, and that records deleted through cascade relationships can be restored.
The storage catch
Deleted records consume Dataverse storage. Microsoft states this plainly and shows the usage in Power Platform admin center reporting. If you delete large volumes, for example through data clean-up, migrations or bulk deletes, the retained records can push an environment towards or over its storage allocation.
Recommendations
- Turn it on for production environments where data recovery matters, such as customer, case and financial data.
- Right-size retention. If 7 or 14 days covers your recovery needs, don't keep 30.
- Watch storage after bulk operations. Purge deleted records after planned clean-ups, once you've verified the results.
- Keep proper backups. This is a safety net for accidental deletes, not a replacement for your backup and retention policy.
- Mind custom logic. If plugins delete related records, plan how restores will rebuild them.
We help organisations design secure, resilient Dataverse environments. See our article on Dataverse security in regulated industries or talk to us.
Source: Microsoft Power Platform Blog — Safeguard, restore and manage deleted records in Microsoft Dataverse



