Dataverse bulk deletion jobs now move between environments
Reviewed by Helen Jones
Microsoft’s updated Dataverse bulk-deletion guidance says job definitions can be added to a solution and moved between environments. The same workflow now exposes job failures in Run details and offers an irreversible permanent-deletion option for one-time cleanups.
Cleanup rules are easy to test once and then accidentally rebuild differently in test and production. That creates inconsistent retention, skipped dependencies, and difficult investigations when a background job fails. Moving the definition through a solution makes the cleanup rule part of application lifecycle management, not an undocumented admin task. Permanent deletion is still a separate risk decision: it bypasses recoverable deleted records and should never be treated like a routine scheduled purge.
Analysis
In a sandbox, test one low-risk cleanup filter and its Run details, then add that job through Data Life Cycle Config before importing it to preproduction. Require a separate review for any permanent-deletion job.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Dataverse bulk deletion jobs can move with solutions", Collab365 Spaces.