Beginning February 2026, Microsoft Dataverse will no longer support configuring deleted-records keeping at the individual table level. Deleted records will now be managed consistently at the environment level for all tables.
How does this affect me?
You will no longer be able to configure deleted‑records keeping per table. All supported tables will follow the single environment‑level setting accessible from Feature Management, helping improve governance, consistency, and reliable data management.
What do I need to do to prepare?
No action is required on your part. When the table‑level option is removed, keeping deleted records will be automatically enabled for all supported tables if your environment‑level setting is turned on for deleted records. Environments where the environment‑level setting is off will remain unchanged.
Source: Microsoft
Latest Posts
- Amazon CloudWatch Logs Insights adds new query commands and functions

- SageMaker Unified Studio automates Glue connector provisioning for cross-subnet job retries

- Cloudflare Fundamentals, Cloudflare One, Cloudflare Tunnel for SASE, Cloudflare Tunnel, Cloudflare Mesh – Granular permissions for Cloudflare Tunnel and Cloudflare Mesh

- AI Gateway – Call any AI model through AI Gateway’s new REST API

![Microsoft Dataverse - Ending Support for configuring Table‑Level Deleted-Records Keeping [MC1215681] 1 Microsoft Dataverse – Ending Support for configuring Table‑Level Deleted-Records Keeping [MC1215681]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-googledeepmind-25626520-1024x683.webp)




