![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-scaled.png\")
While working as a Dynamics 365 and Power Platform Consultant at a technology company, I was responsible for supporting and maintaining our Dataverse environments. Along with configuring tables, business processes, and user requirements, I also looked after environment health, data cleanup, and overall data management.<\/p>\n
As more teams started using the system, the amount of data in Dataverse kept growing. We had historical records that needed to be retained, but we also had temporary, integration-related, and older operational data that was no longer useful. We were already using the traditional Bulk Delete<\/strong> functionality, but as the data volume increased, managing deletion jobs became more challenging. When a job failed, investigating the reason could take time, and maintaining similar deletion configurations across development, testing, and production environments meant repeating the setup. I also had to consider the impact of deletion on plug-ins, workflows, integrations, and other custom processes running in the environment.<\/p>\n While looking into ways to improve this process, I came across Microsoft’s newer Bulk Delete capabilities: Run Details, Solution-aware Bulk Delete, Permanent Deletion, and Sandbox mode<\/strong>. The Run Details<\/strong> option gave me better visibility when a deletion job failed, making troubleshooting easier. Solution-aware Bulk Delete<\/strong> helped us manage deletion configurations more consistently across environments. Permanent Deletion<\/strong> provided an option for situations where we were completely certain that data was no longer required, while Sandbox mode<\/strong> was useful when cleaning up non-production environments, especially after production data was copied into a sandbox.<\/p>\n After exploring these improvements, I started looking at Bulk Delete as more than just a tool for removing old records. It gave me a more structured way to manage data cleanup, retention, troubleshooting, ALM, and sandbox maintenance<\/strong>. This helped us handle growing Dataverse data more efficiently while choosing the appropriate deletion approach based on the environment and the type of data we were managing.<\/p>\n As a prerequisite to use all features related to bulk delete, you need to enable the deleted records feature in your environment. To enable this, follow the steps below.<\/p>\n Environment > Settings > Product > Features > Check the box “Keep deleted records in Dataverse” and then click Save<\/strong>. Understanding Bulk Delete in Microsoft Dataverse<\/strong><\/p>\n Bulk Deletion is a built-in Dataverse feature that we can use when we need to clean up a large number of records without manually deleting them one by one. We simply define the conditions for the records we want to remove, and Dataverse takes care of the deletion in the background.<\/p>\n For example, if an environment has completed system jobs that are more than 90 days old, I can create a Bulk Deletion job to identify and remove those records automatically.<\/p>\n Depending on the requirement, the job can be run once for a quick cleanup or scheduled to run regularly, such as daily, weekly, monthly, or yearly. We can also configure email notifications so we know when the job has finished.<\/p>\n Another useful part is that Bulk Deletion can work with both standard and custom tables. It also follows the normal Dataverse deletion process, so things like security, cascading relationships, plug-ins, and workflows are considered.<\/p>\n In simple terms, we see Bulk Deletion as a practical way to keep unnecessary data from continuously building up in a Dataverse environment.<\/p>\n I would consider using Bulk Deletion whenever we have a large amount of data that needs to be removed based on a clear and repeatable condition. Instead of manually identifying and deleting records every time, we can define the rule once and let Dataverse handle the cleanup.<\/p>\n Some situations where I find Bulk Deletion particularly useful are:<\/p>\n The simple way I look at it is: if I can clearly define which records need to be deleted using a query or condition, Bulk Deletion is usually a good option to consider.<\/p>\n How to Plan Dataverse Data Cleanup With Bulk Delete From Day One<\/strong><\/p>\n One thing I learned while managing Dataverse environments is that data cleanup should be planned from the beginning, not after the environment has already accumulated a large amount of unnecessary data.<\/p>\n Whenever I work with a table that is expected to keep generating records, I try to understand three things early: what data will eventually become unnecessary, how long it needs to be retained, and how that data will be cleaned up.<\/strong><\/p>\n If we don’t plan this upfront, the same pattern usually starts to appear. Transactional and log data keeps growing, old system records remain in the environment, temporary processing tables slowly become permanent, and storage consumption continues to increase. Eventually, what could have been a simple recurring cleanup becomes a much bigger maintenance task.<\/p>\n That’s why I look at a Bulk Deletion job as part of the initial environment design, along with security, integrations, and solution architecture. Even a simple recurring job can make a big difference when it is configured according to the required retention period.<\/p>\n While working with multiple Dataverse environments, I also came across a few practical challenges with managing deletion jobs.<\/p>\n Sometimes a job didn’t complete as expected, and finding the actual reason wasn’t always straightforward. In other cases, when moving solutions from development to testing and production, I had to spend time setting up or checking the same deletion configuration again.<\/p>\n Large cleanup activities were another challenge, particularly after copying an environment into a sandbox. There could be a significant amount of data that wasn’t required for development or testing, and cleaning it up manually wasn’t an efficient approach.<\/p>\n The newer Bulk Deletion experience addresses some of these issues, particularly around troubleshooting and visibility.<\/p>\n One feature I found useful is the Run Details<\/strong><\/a> tab. Instead of having to guess what happened when a job doesn’t behave as expected, I can open the job and see information such as when it started and finished, its status, how many records were deleted, and whether any records failed.<\/p>\n The error information is also much easier to review. This makes it simpler to understand whether the job completed successfully, completed with some errors, or failed before it could properly run.<\/p>\n For me, the main benefit is simple: less guessing, easier troubleshooting, and better visibility into what is actually happening during a large data cleanup.<\/strong><\/p>\n Another one of the changes I found particularly useful is that Bulk Deletion jobs can now be managed as part of a solution-aware<\/a> environment. This is helpful when the same cleanup logic needs to be used across multiple environments.<\/p>\n For example, I can create and test a deletion job in my development or sandbox environment first. Once I’m happy with the filter, schedule, and overall behavior, I can include that job in a solution and move it to the next environment using the normal solution deployment process.<\/p>\n This saves me from having to manually recreate the same Bulk Deletion job in development, testing, and production. The job configuration, including its conditions, schedule, and name, moves along with the solution.<\/p>\n In my day-to-day work, I see this as a small change that can make environment management much easier. It also means the data-cleanup configuration can follow the same deployment process as the rest of the solution instead of being treated as a separate administrative task.<\/p>\n How I set it up:<\/strong><\/p>\n Step 1:<\/strong> Open the Power Apps maker portal, create or open the required solution, and choose the option to add an existing Bulk Deletion job to the solution.<\/p>\n From there, I can include the job with the other solution components and move it through the different environments using the usual solution deployment process.<\/p>\n Step 2:<\/strong> In the solution, select Add existing \u2192 More \u2192 Other \u2192 Data Life Cycle Config<\/strong>. From there, select the existing Bulk Deletion job that you want to include in the solution.<\/p>\n Step 3 <\/strong>\u2013 Select the bulk deletion job to add to the solution.<\/p>\n Step 4:<\/strong> Once the Bulk Deletion job has been added to the solution, export the solution using the same process you normally follow for other solution components. The Bulk Deletion configuration will be included as part of the solution and can then be moved to the required environment.<\/p>\n Another capability that caught my attention is the Permanent deletion<\/strong><\/a> option in the Bulk Deletion Wizard.<\/p>\n Normally, when deleted records are being retained in the environment, Dataverse keeps a copy of the deleted data for a period of time. This can be useful when an important record is deleted by mistake because there is a possibility of recovering it. For business-critical data, I would definitely prefer having that safety net.<\/p>\n However, there are also situations where I know the data has reached the end of its lifecycle and there is no business reason to keep it. For example, old system logs, expired workflow records, or temporary processing data may never need to be restored. Keeping deleted copies of this type of data only adds to storage usage.<\/p>\nPre-requisite<\/strong><\/h3>\n
\n<\/strong><\/p>\n![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-1.jpg\")
<\/p>\nWhen Should You Use Bulk Delete for Dataverse Data Cleanup?<\/strong><\/h3>\n
\n
Common Challenges With Managing Dataverse Bulk Delete Jobs<\/strong><\/h3>\n
1. What Changed with the New Capabilities<\/h3>\n
![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-2.jpg\")
<\/p>\n2. Solution-Aware Bulk Deletion Jobs<\/strong><\/h3>\n
![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-3.jpg\")
<\/p>\n![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-4.jpg\")
<\/p>\n![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-5.jpg\")
<\/p>\n![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-6.jpg\")
<\/p>\n![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-7.jpg\")
<\/p>\n3. Permanent Deletion in the Bulk Deletion Wizard<\/h3>\n
![\"Modernizing](\"https:\/\/www.inogic.com\/blog\/wp-content\/uploads\/2026\/08\/Modernizing-Dataverse-Data-Clean-up-With-New-Bulk-Delete-Capabilities-8.jpg\")
<\/p>\n