SHD / MC Checker

[serviceRestored] MO540640 | Microsoft 365 suite | Admins may experience delays in activating Adaptive Protection for Microsoft Purview services



MO540640 | Microsoft 365 suite | Admins may experience delays in activating Adaptive Protection for Microsoft Purview services

Status serviceRestored
Classification advisory
User Impact Admins may have experienced delays in activating Adaptive Protection for Microsoft Purview services.
Last Updated 04/19/2023 17:13:50
Start Time 04/12/2023 15:26:34
End Time 04/18/2023 07:00:00
Latest Message Title: Admins may experience delays in activating Adaptive Protection for Microsoft Purview services

User impact: Admins may have experienced delays in activating Adaptive Protection for Microsoft Purview services.

More info: This communication related to activating Adaptive Protection for Microsoft Purview, which leverages Insider Risk Management and Data Loss Prevention. Adaptive Protection is a capability of Microsoft Purview that leverages machine learning to understand how users interact with data, assign risk levels, and automatically tailor Microsoft Purview Data Loss Prevention controls. More information about Adaptive Protection can been found at techcommunity.microsoft.com/t5/security-compliance-and-identity/enable-adaptive-protection-with-microsoft-purview/ba-p/3731486.

Final status: We’ve confirmed that all activations have been processed as expected and that the code fix has successfully remediated the impact.

Scope of impact: Impact may have occurred for all admins that attempted to activate Adaptive Protection in Microsoft Purview between Saturday, February 25, 2023, and Friday, April 7, 2023.

Start time: Saturday, February 25, 2023, at 12:00 AM UTC

End time: Tuesday, April 18, 2023, at 7:00 AM UTC

Root cause: An update to Role Based Access Control (RBAC) introduced a code regression that impacted the Adaptive Protection activation flow for Microsoft Purview, which leverages Insider Risk Management and Data Loss Prevention.

Next steps: 
– We’re reviewing the impacting update to understand why it introduced a code regression so that we can improve our testing and validation cycles, detect and resolve such issues prior to deployment, and prevent similar impact from reoccurring in the future.

This is the final update for the event.