Forum Discussion
Unable to find the security alert in M365 Defender referenced in an email alert.
This happens a lot. I get these emails from Office365Alerts notifying our team that "A medium-severity alert has been triggered". At the bottom of the email is a link to "View alert details". When I ...
I have noticed the very same issue on several tenants. This is still present as of February 2024.
Same pattern here:
- alert is received with a URL "https://security.microsoft.com/alerts/unique_alert_ID_here"
- when followed opens up Security Admin Center and shows an error "Can't find it. Either what you are looking for doesn't exist or you need to use a different search string." not being able to locate the alert
- when I substitute security to compliance in the URL like this "https://compliance.microsoft.com/alerts/unique_alert_ID_here" it goes straight away to the details of the alert in question in the right - Compliance - Admin Center
I have raised a ticket with Microsoft but I'm getting nowhere.
I'm being asked to open up the alert again and records logs with Fiddler and Steps Recorder and provide sample alerts on and on, which I did once a week ago.
Now I'm being asked to do the same again. It seems that the engineer completely disregards the nature of the issue, symptoms and doesn't want to acknowledge that this is 100% a fault at the core of the internal template at the time of alert creation, not related to tenant, browser, user, whatever.
Seems like they haven't updated it after Security & Compliance ACs were separated into two.
It feels like I'm talking to a robot.
Hope we can get this resolved eventually.
Ok, got an update.
I had to close the first ticket because I wasn't getting anywhere.
Then I raised another one with Premium Support and after 10 days of no update been told they are gathering info and will update me. After few days the case has been closed without a word and the engineer and his superiors from signature never replied to my emails.
Then I had raised yet another Premier Support ticket with the same info, sample alert emails from test tenant and got contacted by an engineer that also hopped on a remote. He said they are aware of this and this problem is being investigated with a high priority. We have agreed to close it.
The engineer gave me 3 workarounds:
- create a custom policy as a copy of the default one that should have correct URL
- looks for alert in Compliance/Purview
- if the URL from the alert ID starts with "fa" eg. https://security.microsoft.com/alerts/fa1234512345 simply remove the "fa" like this:
https://security.microsoft.com/alerts/1234512345
this way the alert will open in Security Admin Center, yay
I had to close the first ticket because I wasn't getting anywhere.
Then I raised another one with Premium Support and after 10 days of no update been told they are gathering info and will update me. After few days the case has been closed without a word and the engineer and his superiors from signature never replied to my emails.
Then I had raised yet another Premier Support ticket with the same info, sample alert emails from test tenant and got contacted by an engineer that also hopped on a remote. He said they are aware of this and this problem is being investigated with a high priority. We have agreed to close it.
The engineer gave me 3 workarounds:
- create a custom policy as a copy of the default one that should have correct URL
- looks for alert in Compliance/Purview
- if the URL from the alert ID starts with "fa" eg. https://security.microsoft.com/alerts/fa1234512345 simply remove the "fa" like this:
https://security.microsoft.com/alerts/1234512345
this way the alert will open in Security Admin Center, yay
- The problem we ran into with the "fa" fix, is that we cannot manage the alert, in other words, we cannot assign the alert to a team member, nor are we able to mark it as resolved.
We've given up with trying to manage these Purview alerts in Defender, and are now exclusively managing these alerts in Purview (https://compliance.microsoft.com/compliancealerts)- Ran into this for first time today (5/30/24). Glad I came across this thread.
- Issue still exists. Thanks for the workaround!
I spoke with a Microsoft support agent and did a screenshare, today. After showing them the email and broken link, they directed me to "report an issue" (which I believe is synonymous with "bug report"), providing both the broken link and the link the email should have instead.
