Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

How can we improve Azure Active Directory?

← Azure Active Directory

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.

88 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Siemon Roozendaal shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
started  ·  Azure AD Team responded  · 

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?

30 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Sam commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    I've had users with failed logins across multiple organizations in the last 3 days. Charter is using IPv6 and users are getting blocked.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Hi AAD Team, could I ask an approximate % status update and possible roadmap for a time for completion?

  • Frederic Martel commented  ·   ·  Flag as inappropriate

    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.

  • JayKay commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    We need an update on this please, this is security hole that is becoming bigger by the week. It cannot be ignored.

← Previous 1

Azure Active Directory: Identity Protection

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice