Update - We are continuing to monitor for any further issues.
Jan 23, 2023 - 16:01 UTC
Monitoring - Since 14:00 UTC we no longer have backlogs, but we keep monitoring our backend infrastructure to make sure it's stable
Jan 23, 2023 - 16:01 UTC
Identified - User impact: Users may encounter delays of up to several hours for activities in Microsoft Defender for Identity.
More info: Affected users may encounter the delays for activities in the User Interface (UI) and in Advanced Hunting.
Current status: We've identified that a section of infrastructure, responsible for processing activities in Microsoft Defender for Identity, is unexpectedly performing below acceptable performance thresholds which is causing delays and a backlog of activity data. We've optimized traffic and performance parameters on the affected infrastructure to mitigate impact. However, we're monitoring the accumulation of backlogged data as it drains, and expect to have a full remediation timeline by our next scheduled update.
Scope of impact: Impact is specific to users who are served through the affected infrastructure.
Root cause: Root cause: A section of infrastructure, responsible for processing activities in Microsoft Defender for Identity, is unexpectedly performing below acceptable performance thresholds which is causing delays and a backlog of activity data.
Jan 23, 2023 - 14:44 UTC
Update - We are continuing to work on a fix for this issue.
Feb 07, 2022 - 16:38 UTC
Update - A fix to 400 error should be deployed in the next few days. the fix will be part of MDI 2.168 version.
Jan 09, 2022 - 11:24 UTC
Identified - Hi All, please note we have identified an access issue to our main portal.atp.azure.com that might result to some of you with error 400 due to cookie size, the issue is under investigation and as temporary workaround we ask to please use your dedicated workspace portal URL
Dec 02, 2021 - 11:57 UTC