| DZ783225 | Microsoft Defender XDR | Users may be unable to load the email remediation side panel in Microsoft Defender for Office 365 Threat Explorer |
|---|
| Status | serviceDegradation |
|---|---|
| Classification | advisory |
| User Impact | Users may be unable to load the email remediation side panel in Microsoft Defender for Office 365 Threat Explorer. |
| Last Updated | 04/23/2024 20:51:29 |
| Start Time | 04/22/2024 22:30:24 |
| End Time | |
| Latest Message | Title: Users may be unable to load the email remediation side panel in Microsoft Defender for Office 365 Threat Explorer
User impact: Users may be unable to load the email remediation side panel in Microsoft Defender for Office 365 Threat Explorer. More info: As a workaround, affected users may be able to perform email remediation actions by following the steps below to the advanced hunting page instead: Using the Microsoft Defender for Office 365 portal, go to the left navigation bar ‘Hunting’ and select the ‘Advanced Hunting’ option and select the ‘Take Action’ button. Also, users could choose “Take action” from the email entity or summary panel. For further information, affected users can review our ‘Learn More’ additional resources: Roadmap details: www.microsoft.com/en-in/microsoft-365/roadmap?filters=&searchterms=393937 Current status: Our investigation has determined that a recent update to the service upon which this process relies introduced an issue which is resulting in impact. We’re developing a code fix to address this, and we’re in the initial stages of preparing it for deployment. In parallel, we’re continuing to enable the new “Take action” feature in the Office 365 Threat Explorer by request on a case-by-case basis while we pursue resolution. Scope of impact: Impact is specific to some users, who are served through the affected infrastructure, attempting to load the email remediation side panel in Threat Explorer within Microsoft Defender for Office 365. Start time: Monday, April 22, 2024, at 10:14 AM UTC Root cause: A recent update to the service upon which this process relies introduced an issue which is resulting in impact. Next update by: Wednesday, April 24, 2024, at 6:30 AM UTC |