Forum Discussion
Impossible travel alerts on failed logins
I know this topic is about a year old but it's still an ongoing problem with our tenant.
Because the alert is a built in anomaly alert, we can't tune it to avoid this. Due to the size of our tenant and (faculty, students, alumni), I can see nearly 200 of these alerts open and almost every one of them is the result of a successful, legitimate, login in the US followed by a failed login elsewhere.
If any malicious actor wishes to overwhelm a security team with alerts, they could easily just begin generating failed logins from around the world.
Please tune the alert (or allow users to tune the alert) to exclude failed logins. Other than tracking possible brute force attempts there is zero useful intelligence gained from knowing there was a failed login at an impossible travel distance.
We are having the same issue. The Alert is not useful at all because 99% of the time it is a failed login. So after a while you start to ignore what could be a very useful and important alert.
Any help Microsoft guru type people?
Paul
Are we asking this question in the wrong place? This question has been sitting here since May with no response other than others having a different issue. Meanwhile I am still getting a bunch of impossible travel alerts from failed logins that aren't helpful because they are masking the real events that I should be paying attention to.
I have it set to text me when I get one of these alerts which is wonderful when I know that it is actually a successful login but I now just ignore these texts because there is so much to sift through.
Can we get any help here? Surely there is a way to change these options.
Thanks,
Paul
Hey Paul,
I should have updated on this but that got overlooked. I am now wondering if the solution is licensing related, and the inaction by MS is intentional to annoy users into paying for a higher tier. Over the summer we went from A3 to A5 licensing (Not sure what those are in non-educational plans) and one thing I found is that I suddenly *do* have the ability to tune the policy triggering the alert. Under advanced configuration there's "Analyze sign-in activities" and it can be set to only successful sign-ins, which has eliminated the problem for me.
the only change in my environment between me not having the option and having it is the licensing. If that's the case it's highly frustrating that they put such a basic thing behind a paywall that can add six figures to your licensing *and* a MS employee responded to this thread and just couldn't clarify that and has left everyone scrambling for over a year.
We have started receiving Impossible Travel alerts for AT&T via Puerto Rico for people using email on their AT&T mobile devices while located in Florida and Illinois. The IP comes through as
2600:387:9:5::c4, (matched the OP), because I have verified with the users and now know that this is legitimate work being done, I am likely going to alter the policy to known IP addresses.
This really doesn't solve the problem, just masks getting the error from reporting. The real issue is why is AT&T is saying this traffic is from PR.James Jones We had the same issue. Seems to be with AT&T IPv6 routing.
