| MO546398 | Microsoft 365 suite | Admins editing or creating data loss prevention (DLP) rules in Microsoft Purview services may not see condition options |
|---|
| Status | serviceRestored |
|---|---|
| Classification | advisory |
| User Impact | Admins editing or creating DLP in Microsoft Purview services may not see the condition option. |
| Last Updated | 04/26/2023 00:24:52 |
| Start Time | 04/25/2023 01:30:00 |
| End Time | 04/25/2023 23:10:00 |
| Latest Message | Title: Admins editing or creating data loss prevention (DLP) rules in Microsoft Purview services may not see condition options
User impact: Admins editing or creating DLP in Microsoft Purview services may not see the condition option. More info: This issue only affected admins in organizations with Microsoft 365 E5 or A5 Premium licenses with Adaptive Protection for Microsoft Purview Insider Risk Management enabled. Specifically, admins editing or creating a rule scoped to Exchange Online, Microsoft Teams chat and channel messages, or device locations may not have seen the condition option in the condition drop down for Adaptive Protective Risk levels titled “User’s risk level for Adaptive Protection is”. More information on Adaptive Protection for Microsoft Purview Insider Risk Management is available here: techcommunity.microsoft.com/t5/security-compliance-and-identity/enable-adaptive-protection-with-microsoft-purview/ba-p/3731486. Final status: We’ve completed the development, validation and deployment of our fix and have confirmed via service health telemetry that impact was successfully resolved. Scope of impact: Impact may have occurred for admins when editing or creating a DLP rule in Microsoft Purview services scoped to Exchange Online, Microsoft Teams chat and channel messages, or device locations. Start time: Tuesday, April 25, 2023, at 1:30 AM UTC End time: Tuesday, April 25, 2023, at 11:10 PM UTC Root cause: A recent update to an API that facilitates license change and status data syncing with Azure Data Factory resulted in processing errors, causing impact. Next steps: This is the final update for the event. |