Dataverse Bulk Delete Upgrade: Run Details, ALM Solutions and Immediate Import Runs

Under AI at Work roadmap ID 576810 (also tracked in Microsoft 365 admin communications as MC1311990 ), Microsoft has rolled out an update titled Microsoft Dataverse: Improved enterprise experiences in Power Platform - Improve bulk delete user experience. After entering public preview on April 30, 2026, and reaching general availability on June 4, 2026, for Worldwide standard multi-tenant cloud instances, the update is now launched and enabled automatically for users. Rather than reinventing how Dataverse purges records, this release targets two long-standing operational headaches for enterprise administrators: opaque error reporting and the lack of application lifecycle management (ALM) portability.

Why Bulk Delete Needed an Enterprise Upgrade​

In Microsoft Dataverse, bulk deletion allows administrators with System Administrator permissions to define query-based rules that remove stale, irrelevant, or unneeded records in the background. Whether you are clearing out completed system jobs older than 90 days, scrubbing test records after a data migration, or purging expired leads to stay within Dataverse storage entitlements, bulk delete jobs can be run once on demand or scheduled on a recurring cadence (daily, weekly, monthly, half-yearly, or yearly) across both system and custom tables. Because standard bulk deletion respects security roles, cascading rules, plug-ins, and workflows, it acts like a standard platform delete at scale.

However, as Dataverse environments scaled up, two operational friction points became increasingly painful:

• The "Why Did My Job Stop?" Mystery: When a large cleanup job hit an issue or failed to delete specific records, the old user interface offered very little diagnostic feedback. Administrators frequently resorted to simply re-running jobs and hoping for a better outcome.
• Manual Multi-Environment Reconfiguration: While tables, flows, and apps traveled neatly inside Power Platform solutions, bulk delete jobs did not. Admins had to manually recreate the exact same query filters and schedules in development, sandbox, pre-production, and production environments—an error-prone ritual where a single mistyped filter in production could have costly consequences.

Section Summary: Standard Dataverse bulk deletion handles query-based cleanup across system and custom tables, but lacked clear inline failure diagnostics and required manual setup in each environment.

Improvement 1: Actionable Error Handling and the "Run Details" Tab​

The first pillar of roadmap item 576810 replaces generic failure states with job- and record-level error visibility inside the Power Platform admin center. Every bulk deletion job now includes a dedicated Run details tab.

When an administrator opens a bulk delete job and navigates to the Run details tab, the top summary section displays six key operational metrics:

• Job status
• Start time
• End time
• Number of records deleted
• Number of records failed
• Number of errors (with specific errors listed inline)

The Critical Distinction Between "Completed" and "Failed"​

According to Microsoft Learn’s operational documentation and the Microsoft Power Platform Blog, administrators need to pay close attention to how Dataverse defines job statuses in this updated interface:

Why does this matter in practice? In enterprise IT, a green "Completed" badge usually lulls admins into thinking everything went according to plan. In Dataverse bulk deletion, a job can finish its run while failing to delete hundreds of individual records due to cascading restrictions, plug-in exceptions, or lock contentions. Having the failed record count and inline error details front and center allows admins to diagnose whether a plug-in or relationship constraint blocked specific deletions without blindly re-running the entire batch. While Microsoft notes that this visibility is intended to speed up troubleshooting and reduce reruns, it is still up to the administrator to resolve the underlying data or logic dependency reported in the logs.

Section Summary: The new Run details tab exposes deleted and failed record counts alongside inline error details, and clarifies whether a job failed to start altogether (Failed) or finished its run with individual record errors (Completed).

Improvement 2: Solution-Aware Bulk Delete Configurations​

The second major enhancement in this release brings bulk deletion into proper Power Platform application lifecycle management (ALM). Bulk delete configurations are now solution-aware, meaning the full job definition—including its name, query filters, and recurring schedule—can be packaged into a solution and transported across environments.

Instead of rebuilding cleanup rules by hand in production, teams can author and validate a bulk delete job in a development or sandbox environment, package it, and promote it through pre-production and production using standard solution export and import workflows.

How to Add a Bulk Delete Job to a Solution​

Per Microsoft Learn documentation and the Power Platform Blog, packaging a bulk delete job requires using the Power Apps maker portal alongside the Power Platform admin center:

1. Create the Bulk Delete Job (if not already created): Sign in to the Power Platform admin center, navigate to Manage > Environments, select your source environment, choose Settings in the command bar, expand Data management, select Bulk deletion, and click New to configure the job via the Bulk Deletion Wizard.
2. Open Your Solution: Go to the Power Apps maker portal and create a new solution or open an existing unmanaged solution.
3. Add the Configuration Component: Inside the solution, select Add existing > More > Other > Data Life Cycle Config. (Note: Microsoft uses the Data Life Cycle Config component category to package both archival and deletion policies.)
4. Select and Export: Choose one or more existing bulk deletion jobs to add to your solution, then export and import the solution into your target environment just as you would any other solution component.

Crucial Operational Boundaries and the "Immediate Run" Warning​

Before you enthusiastically import a solution containing bulk delete jobs into your live production environment at 10:00 AM on a Tuesday, read the fine print from Microsoft Learn’s admin documentation. Solution-aware bulk deletion comes with four strict operational rules:

• Admin-Only Governance: Only administrators can create and import solutions that contain bulk deletion jobs.
• Environment Scope: Only bulk deletion jobs created in Power Platform environments can be made solution-aware.
• Definitions Only, Not Data: Only the job definitions travel inside the solution package; deleted data is never included.
• Immediate Execution on Import: Imported bulk deletion jobs run immediately upon import.

That fourth point is the single most important operational takeaway for Windows and Power Platform administrators. Importing a solution with a Data Life Cycle Config component does not merely stage a dormant job waiting for its next scheduled window—it triggers an immediate execution in the target environment. Administrators must verify the query filters thoroughly in a lower environment and schedule their production solution imports during appropriate maintenance windows so an immediate cleanup run does not catch business users or integrations off guard.

Section Summary: Administrators can now package bulk delete jobs inside solutions via Add existing > More > Other > Data Life Cycle Config, eliminating manual setup across environments—provided they plan around the fact that imported jobs execute immediately upon import.

Related Context: Permanent Deletion and Sandbox Refinements​

While roadmap item 576810 specifically covers the new error-handling UI and solution-aware portability, Microsoft’s June 10, 2026 Power Platform Blog post by Dataverse Product Manager Ritu Joshi also highlighted adjacent bulk deletion capabilities landing in the same June 2026 timeframe. To keep your governance strategy straight, it helps to distinguish the core roadmap update from these related features:

• Permanent Deletion Checkbox (One-Shot Jobs Only): In environments where "deleted records keeping" is enabled, Dataverse normally copies removed records into deleted-record tables so admins can restore them within a configured recovery window. For disposable data like old system logs or transient telemetry, the Bulk Deletion Wizard now includes a Permanent deletion checkbox. Available strictly for non-recurring, one-shot jobs, checking this box skips the deleted-records table copy, saving storage and speeding up execution—at the cost of making the deletion permanently unrecoverable.
• Sandbox Deletion Mode (API Option): For rapid cleanup after copying a production environment into a sandbox, Microsoft introduced a RunJobForSandbox option in the BulkDelete API. It permanently deletes records while skipping plug-ins, workflows, and deleted-record keeping, using the cascade engine directly to maintain referential integrity.

Best Practices for Dataverse Admins Moving Forward​

As Microsoft’s Dataverse team points out, data deletion should be treated like garbage collection in an application—a Day-1 design decision rather than an emergency project triggered when storage overage alerts start firing. With roadmap ID 576810 now generally available, administrators should consider three practical steps:

1. Audit "Completed" Jobs: Visit Settings > Data management > Bulk deletion in the Power Platform admin center and check the Run details tab on your recurring jobs to verify whether "Completed" jobs have been silently racking up failed record counts.
2. Standardize Cleanup in ALM Pipelines: Add your standard hygiene jobs (such as purging old workflow logs or plug-in trace logs) to a core governance solution under Data Life Cycle Config so every newly provisioned environment inherits consistent retention rules.
3. Gate Your Solution Imports: Update your deployment checklists so release managers know that importing a solution containing bulk delete definitions will trigger those deletion queries immediately upon import.