Blog Post

Microsoft Purview Blog
4 MIN READ

Priority Cleanup V2: Faster, Simpler Data Purging for Exchange Online

Victor Legat's avatar
Victor Legat
Icon for Microsoft rankMicrosoft
Mar 18, 2026

Planned enhancements, seeking customer feedback and collaboration during private preview before implementation

Enhancements Achieved with Exchange Priority Cleanup V2

Priority Cleanup (Use priority cleanup to expedite the permanent deletion of sensitive information from mailboxes | Microsoft Learn) was introduced to provide administrators with a powerful tool for permanently deleting mailbox content, even when under retention or eDiscovery hold, to address scenarios such as data spillage and urgent removals. Priority Cleanup addressed a key need in Exchange Online by allowing hold overrides. Through real-world use, we received valuable insights regarding the approval process, deletion speed, and reviewer experience. These learnings have guided our ongoing enhancements, ensuring that the solution evolves to better meet customer needs for efficiency and ease of use while maintaining robust security and compliance standards.

What's New in Priority Cleanup V2

Priority Cleanup V2 is currently in the planning stage. We’re sharing the proposed updates early to gather feedback before we begin implementation. The goal is to address the core limitations of V1 with enhancements focused on speed and simplicity.

Faster Data Deletion & Simplified Approval Workflow: We’re proposing to streamline the process to two key checkpoints:

  1. Policy enforcement approval when moving from simulation to active mode (requires approval from a different Priority Cleanup admin).
  2. We’re proposing to minimize approval overhead by removing unnecessary review stages. Disposition review by eDiscovery admins will be required only for mailboxes under eDiscovery hold. For other mailboxes, items will be permanently deleted soon after the Priority Cleanup policy is applied to speed up processing from days to hours. This would reduce the number of required users with admin privileges from four to two.

Controlled Purge Limits: 

Administrators will be able to efficiently manage substantial purges by securely processing deletions in batches, with a configurable limit of up to 100 items per mailbox per ELC run. A default limit of 100 items is applied, with the ability to adjust this value through an organization‑level configuration. This configurable limit provides an additional safeguard for system operations while offering flexibility to meet varying organizational needs.

Note: A default limit of 100 items will apply, with the ability to adjust this value via an organization-level configuration.

V1 vs V2 Feature Comparison

Feature

V1 Behavior

V2 Improvement

Deletion Speed

Multi-stage process taking 6+ days for small purges

Significantly faster with immediate deletion for non-hold mailboxes

Approval Workflow

3-stage approval (Priority Cleanup Admin, Retention Admin, eDiscovery Admin)

2-stage approval (policy enforcement + eDiscovery review only when needed)

Proposed Improvements in Admin Experience and Control

  1. Streamlined Policy Management: We are considering making policies easier to enable or disable directly from the main list view, potentially through a simple toggle, so administrators would no longer need to use the setup wizard for this task.
  2. Enhanced Review Interface: Proposed updates include adding new, informative columns to the interface, such as a dedicated Mailbox/Site column to help identify the source location. We are also looking at providing clearly labeled date fields to indicate when items were received or created, which would replace the potentially confusing ExpiryDate label.
  3. Comprehensive Audit Trails: It is proposed that every action would be thoroughly documented with a unique Cleanup ID. This ID could then be used in Audit Search to locate all events related to a specific cleanup operation, helping to simplify verification and post-incident analysis.

Note: Priority Cleanup V2 enhancements are specific to Exchange Online. These changes do not affect Priority Cleanup for OneDrive and SharePoint (PC ODSP), including its rollout timelines or behavior.

Key Benefits for Administrators

Priority Cleanup V2 delivers tangible improvements across the entire data purging workflow.

  1. Accelerated Deletion: Requests for data removal are fulfilled much faster, enabling urgent incidents to be resolved within hours rather than days, and minimizing risk exposure.
  2. Reduced Administrative Overhead: Coordination requirements are simplified, decreasing the number of users involved from four to two in most cases, which makes Priority Cleanup V2 more practical for smaller teams.
  3. Enhanced Transparency: Improved user interface labels and robust audit logs help administrators clearly understand what data is being deleted and who authorized the action.
  4. Maintained Security and Compliance: Segregation of duties is preserved so that no single individual can delete protected content alone, supporting security and compliance requirements.

Availability and Rollout

Priority Cleanup V2 is currently in development with rollout planned for the end of 2026. As with all Exchange Online features, we will publish a Microsoft 365 Roadmap item and send Message Center notifications to affected tenants before general availability

We Want Your Feedback

Priority Cleanup V2 represents a significant evolution based on customer feedback from V1 users who emphasized the need for faster, simpler data purging without compromising security. We've addressed the core pain points around speed, approval complexity, and admin experience, but we know there's always room for improvement.

We'd love to hear your thoughts: Does the simplified approval workflow meet your security requirements?  What visibility or reporting capabilities would make you more confident in using Priority Cleanup for urgent data removal scenarios?

Your feedback directly shapes how we prioritize future enhancements. Please share your experiences and suggestions through your regular Microsoft support channels or customer success contacts. Together, we can continue refining Priority Cleanup to better serve your data governance needs.

 

Aniket Gupta, Mehul Kaushik, Victor Legat & Purview Data Lifecycle Management Team

Updated Apr 20, 2026
Version 2.0

13 Comments

  • Gadget34's avatar
    Gadget34
    Copper Contributor

    We have a purview retention policy applied to our Exchange online mailboxes for a set period of time to retain and then delete emails which I assume is standard in most companies? This policy applies to the main Exchange online mailbox and also the archive mailbox. Priority clean up is only supported for the Exchange online mailbox so we are unable to delete emails from user Archive mailboxes? How do other companies deal with this? TonyRedmond​  have you got any experience of this scenario? We get rights to deletion under UK GDPR and currently can't fulfil these.

    • I wonder if lack of support for the archive mailbox is associated with lack of Graph API support for archive mailboxes... CRUD support for archive mailboxes is supposed to be coming as part of the project to deprecate EWS. Perhaps we'll see some movement then.

      I can't speak for the developers, but the logic as to why support for archive mailboxes is not present is that the intention is to remove information from view that is current rather than the long-term storage in the archive.

      • Gadget34's avatar
        Gadget34
        Copper Contributor

        Thanks TonyRedmond​, so at the moment there isn't a technical solution to permanently delete emails from an Archive mailbox if we use Purview retention policies without first removing the retention policy and then deleting the data before re applying the policy? I assumed other companies would have the same requirement under UK GDPR?

  • MaxRivera's avatar
    MaxRivera
    Copper Contributor

    Was v1 ever rolled out to GCC? And we're already talking about v2?

  • The requests to bring back Search-Mailbox speak to the need for speed when resolving something like a data spillage. Priority Cleanup is just too slow and ponderous in its current form - and I suspect that it will still be even with the enhancements being contemplated. One suggestion is have an initial "hide" pass where the search finds and hides mailbox items pending investigation. Removing items from user sight is a great start for many scenarios where Priority Cleanup might be used and it allows investigators and administrators the time to review items and decide on their final disposition without coming under pressure to resolve a problem. 

    • srfndoc's avatar
      srfndoc
      Brass Contributor

      Amen Tony.  These requests always come with super high urgency as we race to remove the messages in a timely fashion.  We had many pre-built search-mailbox queries that we could re-use (just changing the details) so could process these requests very quickly.  Priority cleanup is just way to slow/bulky.  

  • srfndoc's avatar
    srfndoc
    Brass Contributor

    Another vote to bring back search-mailbox with the ability to delete items on hold.  It worked quickly, was able to test first and could be scoped with many different options.  We know this is possible as search-mailbox existed in EXO for a while. 

     

    Do the right thing MS, bring it back, even if it can't delete on hold items.  

     

     

  • GrzeWier's avatar
    GrzeWier
    Brass Contributor

    All of these improvements are waste of your time.

    Just bring back Search-Mailbox command and allow it to delete items even if they are on hold(s).

    Done

  • jonobond's avatar
    jonobond
    Copper Contributor

    There is no way to scope administrative authority. Any user assigned the Priority Cleanup role can create policies targeting any mailbox in the tenant, regardless of business unit or ownership model.

    In large, federated organizations, this prevents safe delegation to BU or regional admins and forces Priority Cleanup to operate as a fully centralized service, reducing responsiveness for legitimate local incidents.

    Requested enhancement: support admin‑level scoping (for example, by adaptive scope, mailbox set, or Entra Administrative Unit), separate from policy targeting, similar in concept to Exchange RBAC or Administrative Units—while retaining existing approval and audit controls.

  • Speed of processing is mandatory. Priority Cleanup is desperately slow and clumsy (over complicated). 

    Reporting what's going on with a summary going back to the people who created a cleanup policy would be a good thing. The report should identify how many matching items have been found, where they are located, and the progress to cleanup.

     

    BTW, with my editor hat on, I can't see how you can claim achievements for the V2 solution when it's still being designed.

    BTW2, Did the V2 solution ever exit Preview and reach GA? I can't find a GA announcement.

  • nhawk258's avatar
    nhawk258
    Iron Contributor

    We've yet to get the approval process for Priority Cleanup to work properly. It doesn't seem to respect PIM Eligible roles for Purview Admin access. If an admin is defined as one of the approvers but does not have their role active when the request is submitted, no notification is generated. 

    That's a huge miss in my mind and should be part of any sort of v2 that is rolled out.