Published Jun 24, 2024
The message details an upcoming feature in the Microsoft Purview compliance portal: a new cmdlet, 'Invoke-ComplianceSecurityFilterAction', for managing compliance boundary properties for mailboxes and sites. It is associated with Microsoft 365 Roadmap IDs 397091 and 398451, with rollout starting early August 2024 and completing by late August 2024. The feature will simplify compliance management and is off by default. Organizations are advised to review the cmdlet documentation and prepare compliance admins for the update.
Updated July 26, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon to Microsoft Purview compliance portal: A new compliance boundary cmdlet Invoke-ComplianceSecurityFilterAction will be available as part of the Security & Compliance PowerShell. This cmdlet allows user to check if a given mailbox or site has the compliance boundary property value set. If the property is not set or if the object is in arbitration, compliance admins can use this cmdlet to assign the property value for the mailbox or site for compliance boundary to take effect.
This message is associated with Microsoft 365 Roadmap ID 397091 and 398451
When this will happen:
General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early August 2024 (previously mid-July) and expect to complete by late August 2024.
How this will affect your organization:
Before this rollout: Admins had no single solution to check or set mailbox properties and arbitration status, requiring complex steps with Exchange PowerShell for different mailbox types.
After this rollout: This cmdlet will enhance your organization's ability to manage compliance boundaries. It will be especially beneficial in situations where a Microsoft OneDrive site needs to be brought back into compliance following a user's departure, or when an inactive mailbox is not correctly assigned. This cmdlet allows for the straightforward setting of the compliance boundary property, based on user input, to address these issues.
This new feature is off by default.
What you need to do to prepare:
This rollout will happen automatically by the specified date. To prepare for this update, we recommend reviewing the Compliance boundary cmdlet documentation at New-ComplianceSecurityFilter (ExchangePowerShell) | Microsoft Learn. Additionally, ensure that your compliance admins are informed about the upcoming changes and are ready to incorporate the cmdlet into your organization’s process such as departed employees to ensure compliance boundary stay in effect.