Announcement ID | MC765808 | Published Date | 04-02-2024 | |
Service | Microsoft 365 suite | Last Updated | 06-28-2024 | |
Category | Stay informed | Expiration Date | 08-30-2024 | |
Roadmap ID | 161829 | Action Required by Date | ||
Tags | Updated message, New feature, Admin impact |
Summary |
---|
Microsoft Purview Communication Compliance will introduce enhanced policy conditions for precise detection, custom logic, and seamless testing. Public Preview begins late April 2024, with General Availability starting late May 2024. Updates include detection of external email communications, support for the OR operator, and condition testing before implementation. |
More Information |
---|
Coming soon: Microsoft Purview Communication Compliance is introducing enhanced policy conditions that enable empowering precise detection, custom logic, and seamless testing for compliance needs. When this will happen: Public Preview: We will begin rolling out late April 2024 and expect to complete by mid-May 2024. General Availability Worldwide: We will begin rolling out late May 2024 and expect to complete by late July 2024 (previously late June). How this will affect your organization: After the rollout, three updates will enhance policy conditions in Communication Compliance:
The new condition features are in the same position in the Compliance Portal as before the rollout: What you need to do to prepare: Microsoft Purview Communication Compliance provides the tools to help organizations detect business conduct and regulatory compliance violations (e.g. SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy. This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate. |