Back to latest version

MC700928 - Microsoft Purview Insider Risk Management: Public preview of policy wizard enhancements

Message Center

Metadata at Feb 7, 2024

Last Updated

Feb 7, 2024

Published Dec 22, 2023

Service

Microsoft 365 suite

Tag

Updated message
New feature
Admin impact

Platforms

Web

Metadata changes

End date
Aug 20, 2024Apr 30, 2024

Body changes

removed textadded text

Updated August 13,February 7, 2024: After further consideration, weWe have decided to not move forward withupdated the rollout at this time. We will communicate via Message center when we are ready to proceed. We apologizetimeline below. Thank you for any inconvenience this may have caused.your patience.

Coming soon, Microsoft Purview Insider Risk Management will be rolling out a public preview of policy wizard enhancements.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal

Learn more: Create and manage insider risk management policies | Microsoft Learn 

This message is associated with Microsoft 365 Roadmap ID 368825

[When this will happen:]

WeRollout will communicate via Message center when we are readybegin in the end of early February 2024 (previously January) and is expected to proceed.be complete by early March 2024 (previously early February). 

[How this will affect your organization:]

To enhance the user experience for editing and creating policies, we will be making improvements to the Trigger, Trigger threshold, Indicator threshold, and Summary pages of the policy wizard.

[What you need to do to prepare:]

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.