MC1194077 Low
Microsoft Purview | Data Lifecycle Management - New cmdlet to remove retention holds from inactive mailboxes
Summary AI-generated
Admins can now use new cmdlet parameters in Purview Data lifecycle management to remove specific retention holds from inactive Exchange mailboxes, enabling permanent deletion if no legal holds remain.
Suggested actions AI-generated
- Review compliance requirements
- Obtain compliance team approval
- Update internal documentation
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1183292 Microsoft Purview | Data Lifecycle Management - Introducing secure priority cleanup workflows for OneDrive/SharePoint
- MC1261587 Microsoft Purview | Data Lifecycle Management - Hard delete OneDrive and SharePoint files with priority cleanup workflow
- MC1472601 Microsoft Purview: Archive OneDrive and SharePoint files under retention policies
- MC1261586 Microsoft Purview: Data Lifecycle Management - Retention support Microsoft Teams call logs
- MC1213770 (Updated) Microsoft Purview | Data lifecycle Management cmdlet connectivity change
- MC1455013 (Updated) Microsoft Purview: Data Lifecycle Management- Azure PST Import
Original post from Microsoft
We’re introducing new opt-in cmdlet parameters in Microsoft Purview Data lifecycle management that help administrators remove retention holds from inactive mailboxes. The new ExcludeFromAllHolds parameter removes all applicable holds except eDiscovery holds, litigation hold, and restrictive retention policies, enabling permanent deletion of mailboxes while continuing to respect compliance requirements.
The RemoveComplianceTagHold switch, in contrast, removes only the Compliance Tag–based hold (ComplianceTagHoldApplied) from a mailbox. This gives administrators more granular control when they want to adjust Compliance Tag enforcement without excluding the mailbox from other holds.
This message is associated with Microsoft 365 Roadmap ID 537204.
[When this will happen]General Availability (Worldwide, GCC, GCC-High, DoD): Rollout begins in early December 2025 and completes by late December 2025.
[How this affects your organization]Who is affected: Admins managing inactive mailboxes in Exchange Online and on-premises Exchange.
What will happen:
- Admins can use the new cmdlet to remove multiple types of retention holds from inactive mailboxes in a single operation.
- Mailboxes can be permanently deleted after holds are removed, provided no legal or restrictive retention policies remain.
- This feature is opt-in and requires explicit execution of the cmdlet.
- Review compliance requirements before using the cmdlet.
- Obtain approval from your compliance team prior to execution.
- Update internal documentation to reflect this new capability.
| Question | Answer |
| Does the change alter how existing customer data is processed, stored, or accessed (such as documents, emails, chats)? | Yes, Once the holds are removed, the data will no longer be preserved. Inactive mailboxes will transition to a soft-deleted state and will be permanently deleted after 30 days. |
| Does the change modify, interrupt, or disable capabilities in Purview such as retention policies, holds, or deletion workflows? | Exchange administrators can remove organization-wide retention policies, user-specific retention policies, delay holds, delay-release holds, and Compliance Tag holds. This enables them to permanently delete mailboxes, provided no other legal or restrictive holds are applied. |
| Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? | After removing the permitted holds from mailboxes, users can permanently delete them, provided no other legal or restrictive holds remain in place. |
Additional details from Microsoft
- RoadmapIds
- 537204
- Summary
- Microsoft Purview introduces new opt-in cmdlet parameters to remove retention holds from inactive mailboxes, enabling permanent deletion while respecting compliance. The ExcludeFromAllHolds parameter removes most holds except eDiscovery and litigation holds, and RemoveComplianceTagHold targets only Compliance Tag holds. Rollout begins December 2025.
- Platforms
- Web