Show location for Azure AD sign-ins from IPv6 addresses
Please add location information to sign-ins from IPv6 addresses. Currently there is no location information associated with IPv6 so it is circumventing all the Azure AD Identity Protections you have in place.
Siemon Roozendaal
shared this idea
Thanks for your feedback, folks. We have been working towards resolving the locations for IPv6 logins. Currently, a subset of such logins are getting resolved for location and the % will gradually go up. Are you seeing some of your IPv6 logins with resolved location?
29 comments
-
Laszlo
commented
2021 and still not solved. shame
-
Adrian Jöri
commented
Please resolve this fast
-
Patrick Lubbers
commented
How hard can it be for Microsoft with this information?:
-
Rob Milman
commented
Upvoted
-
Patrick Lubbers
commented
Please get this resolved, we need this to keep controll on our userlogins and conditional access
-
Sam
commented
Just put in a ticket and got this as a reply so our protection for users by blocking logins from foreign countries isn't working correctly any more. And as a lot of carriers are switching to IPv6 this will be a continues problem. For now this already is a big issue but this will keep on getting bigger. Please resolve this
-
Jacqueline Sirmon
commented
We attempted to protect users by blocking logins from foreign countries. It works...until a user has a phone that is accessing the internet with an IPV6 address. Their access to Office 365 apps is blocked on their phone. Microsoft, please resolve!
-
Robert White
commented
Just opened a ticket and they pointed me here. More and more carriers are moving to IPv6 and this is causing a major issue.
-
Jon Webster
commented
I've had users with failed logins across multiple organizations in the last 3 days. Charter is using IPv6 and users are getting blocked.
-
Andrew
commented
Any update on this as the following KB is pointless if you don't have all the IPv6 addresses since more and more ISP companies are moving to IPv6 when connecting to Microsoft.
-
Anonymous
commented
Hi AAD Team, could I ask an approximate % status update and possible roadmap for a time for completion?
-
Frederic Martel
commented
Conditionnal access is a must for our customers as a first line of defence in cloud. Right now we have some ISP in Canada that are enabling IPv6 for mobile and residential links. Geolocation for IPv6 is a must, because without it conditionals access block the users. Checking the allow all unknow locations is not an option and a huge secuirty risk.
-
DRobertson
commented
Still an issue today, user locked out while on mobile, device using IPv6.
Any updates? -
JayKay
commented
I too am seeing Bedminster Township, New Jersey, US on a lot of IPV6. I need to know if this is a security breach or some traffic routing!
-
Neil
commented
I have a bunch of sign ins from Bedminster Township, New Jersey, all under an IPv6 address. Is that something to do with Azure syncing with a user's 365 on their phone?
-
Andrew
commented
fix it... need to block signins from non-us where are users never are...conditional access policies can't do it right now.
-
James Summerlin
commented
We need an update on this please, this is security hole that is becoming bigger by the week. It cannot be ignored.
-
Al
commented
Update please!
-
Jeremy Bradshaw
commented
This has not improved in almost a year since the "STARTED" status.
-
Woodward, William
commented
Is there a timeline on when the majority of these will start getting resolved? We are seeing maybe 1/8 so far. This needs to be an ASAP issue.
