Conditional Access: Network assignment

Administrators can create policies that target specific network locations as a signal along with other conditions in their decision making process. They can include or exclude these network locations as part of their policy configuration. These network locations might include public IPv4 or IPv6 network information, countries/regions, unknown areas that don't map to specific countries/regions, or Global Secure Access' compliant network.

Note

Conditional Access policies are enforced after first-factor authentication is completed. Conditional Access isn't intended to be an organization's first line of defense for scenarios like denial-of-service (DoS) attacks, but it can use signals from these events to determine access.

Organizations might use these locations for common tasks like:

• Requiring multifactor authentication for users accessing a service when they're off the corporate network.
• Blocking access from specific countries your organization never operates from.

A user's location is found using their public IP address or the GPS coordinates provided by the Microsoft Authenticator app. Conditional Access policies apply to all locations by default.

Tip

The Location condition has moved and is renamed Network. At first this condition will appear at both the Assignment level, and under Conditions.

Updates or changes appear in both locations. The functionality remains the same and existing policies using Location continue to work without changes.

When configured in policy

When you configure the location condition, you can distinguish between:

• Any network or location
• All trusted networks and locations
• All Compliant Network locations
• Selected networks and locations

Any network or location

By default, selecting Any location causes a policy to apply to all IP addresses, which means any address on the Internet. This setting isn't limited to IP addresses you configure as named locations. When you select Any location, you can still exclude specific locations from a policy. For example, you can apply a policy to all locations except trusted locations to set the scope to all locations, except the corporate network.

All trusted networks and locations

This option applies to:

• All locations marked as trusted locations.
• Multifactor authentication trusted IPs, if configured.

Multifactor authentication trusted IPs

Using the trusted IPs section of multifactor authentication's service settings is no longer recommended. This control only accepts IPv4 addresses and should only be used for specific scenarios covered in the article Configure Microsoft Entra multifactor authentication settings.

If you have these trusted IPs configured, they show up as MFA Trusted IPs in the list of locations for the location condition.

All Compliant Network locations

Organizations with access to Global Secure Access features have another location listed that is made up of users and devices that comply with your organization's security policies. For more information, see the section Enable Global Secure Access signaling for Conditional Access. It can be used with Conditional Access policies to perform a compliant network check for access to resources.

Selected networks and locations

With this option, you can select one or more named locations. For a policy with this setting to apply, a user needs to connect from any of the selected locations. When you choose Select, you're presented with a list of defined locations opens. This list shows the name, type, and if the network location is marked as trusted.

How are these locations defined?

Locations are defined and exist in the Microsoft Entra admin center under Protection > Conditional Access > Named locations. Administrators with at least the Conditional Access Administrator role can create and update named locations.

Named locations might include locations like an organization's headquarters network ranges, VPN network ranges, or ranges that you wish to block. Named locations contain IPv4 address ranges, IPv6 address ranges, or countries.

IPv4 and IPv6 address ranges

To define a named location by public IPv4 or IPv6 address ranges, you must provide:

• A Name for the location.
• One or more public IP ranges.
• Optionally Mark as trusted location.

Named locations defined by IPv4/IPv6 address ranges are subject to the following limitations:

• No more than 195 named locations.
• No more than 2000 IP ranges per named location.
• Only CIDR masks greater than /8 are allowed when defining an IP range.

For devices on a private network, the IP address isn't the client IP of the user’s device on the intranet (like 10.55.99.3), it's the address used by the network to connect to the public internet (like 198.51.100.3).

Trusted locations

Administrators might optionally mark IP-based locations like your organization's public network ranges as trusted. This marking is used by features in several ways.

• Conditional Access policies can include or exclude these locations.
• Sign-ins from trusted named locations improve the accuracy of Microsoft Entra ID Protection's risk calculation.

Locations marked as trusted can't be deleted without first removing the trusted designation.

Countries

Organizations can determine a geographic country or region location by IP address or GPS coordinates.

To define a named location by country or region, you must:

• Provide a Name for the location.
• Choose to determine location by IP address or GPS coordinates.
• Add one or more countries/regions.
• Optionally choose to Include unknown countries/regions.

When selecting Determine location by IP address, Microsoft Entra ID resolves the user's IPv4 or IPv6 address to a country or region, based on a periodically updated mapping table.

When selecting Determine location by GPS coordinates, users must have the Microsoft Authenticator app installed on their mobile device. Every hour, the system contacts the user’s Microsoft Authenticator app to collect the GPS location of their mobile device.

• The first time the user must share their location from the Microsoft Authenticator app, they receive a notification in the app. The user must open the app and grant location permissions. For the next 24 hours, if the user is still accessing the resource and granted the app permission to run in the background, the device's location is shared silently once per hour.
• After 24 hours, the user must open the app and approve the notification.
• Every time the user shares their GPS location, the app does jailbreak detection using the same logic as the Microsoft Intune MAM SDK. If the device is jailbroken, the location isn't considered valid, and the user isn't granted access.
  • The Microsoft Authenticator app on Android uses the Google Play Integrity API to facilitate jailbreak detection. If the Google Play Integrity API is unavailable, the request is denied and the user isn't able to access the requested resource unless the Conditional Access policy is disabled. For more information about the Microsoft Authenticator app, see the article Common questions about the Microsoft Authenticator app.
• Users might modify the GPS location as reported by iOS and Android devices. As a result, the Microsoft Authenticator app denies authentications where the user might be using a different location than the actual GPS location of the mobile device where the app is installed. Users who modify the location of their device get a denial message for GPS location-based based policies.

Note

A Conditional Access policy with GPS-based named locations in report-only mode prompts users to share their GPS location, even though they aren't blocked from signing in.

GPS location can be used with passwordless phone sign-in only if MFA push notifications are also enabled. Users can use Microsoft Authenticator to sign in, but they also need to approve subsequent MFA push notifications to share their GPS location.

GPS location doesn't work when only passwordless authentication methods are set.

Multiple Conditional Access policies might prompt users for their GPS location before all are applied. Because of the way Conditional Access policies are applied, a user might be denied access if they pass the location check but fail another policy. For more information about policy enforcement, see the article Building a Conditional Access policy.

Important

Users may receive prompts every hour letting them know that Microsoft Entra ID is checking their location in the Authenticator app. This feature should only be used to protect very sensitive apps where this behavior is acceptable or where access must be restricted for a specific country/region.

Include unknown countries/regions

Some IP addresses don't map to a specific country or region. To capture these IP locations, check the box Include unknown countries/regions when defining a geographic location. This option allows you to choose if these IP addresses should be included in the named location. Use this setting when the policy using the named location should apply to unknown locations.

Common questions

Is there Graph API support?

Graph API support for named locations is available, for more information, see the namedLocation API.

What if I use a cloud proxy or VPN?

When you use a cloud hosted proxy or VPN solution, the IP address Microsoft Entra ID uses while evaluating a policy is the IP address of the proxy. The X-Forwarded-For (XFF) header that contains the user’s public IP address isn't used because there's no validation that it comes from a trusted source, so would present a method for faking an IP address.

When a cloud proxy is in place, a policy that requires a Microsoft Entra hybrid joined or compliant device can be easier to manage. Keeping a list of IP addresses used by your cloud hosted proxy or VPN solution up to date can be nearly impossible.

We recommend organizations utilize Global Secure Access to enable source IP restoration to avoid this change in address and simplify management.

When is a location evaluated?

Conditional Access policies are evaluated when:

• A user initially signs in to a web app, mobile or desktop application.
• A mobile or desktop application that uses modern authentication, uses a refresh token to acquire a new access token. By default this check is once an hour.

This check means for mobile and desktop applications using modern authentication, a change in location is detected within an hour of changing the network location. For mobile and desktop applications that don’t use modern authentication, the policy applies on each token request. The frequency of the request can vary based on the application. Similarly, for web applications, policies apply at initial sign-in and are good for the lifetime of the session at the web application. Because of differences in session lifetimes across applications, the time between policy evaluation varies. Each time the application requests a new sign-in token, the policy is applied.

By default, Microsoft Entra ID issues a token on an hourly basis. After users move off the corporate network, within an hour the policy is enforced for applications using modern authentication.

When you might block locations?

A policy that uses the location condition to block access is considered restrictive, and should be done with care after thorough testing. Some instances of using the location condition to block authentication might include:

• Blocking countries/regions where your organization never does business.
• Blocking specific IP ranges like:
  • Known malicious IPs before a firewall policy can be changed.
  • Highly sensitive or privileged actions and cloud applications.
  • Based on user specific IP range like access to accounting or payroll applications.

Related content

• Configure an example Conditional Access policy using location.