Microsoft Security | Microsoft Entra | Microsoft Entra ID
A cloud-based identity and access management service for securing user authentication and resource access
Entra ID - User now shows IPv6 ULA as IP source location
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 95%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Steve Porter
0
Reputation points
Something changed recently and now we have several user accounts that show an IPv6 ULA IP address (starting with FD00).
The side effect is it is now bypassing our IPv4 conditional access by location rules.
Any idea on what changed to cause this or better yet - what we can do to get these users reporting back as their correct IPv4 originating IP?
Thanks!
Steve P
Microsoft Security | Microsoft Entra | Microsoft Entra ID
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 73%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKJ%3C/text%3E%3C/svg%3E)
Killian Jones 0 Reputation points2026-04-13T16:13:13.46+00:00 I see the same behavior. Conditional access policies are failing because the source IP address appears to be a ULA (not a ULA I'm familiar with though).
Sign in to comment
Sign in to answer