1. Resources
  2. Detection rules
  3. Trusted Named Location Added or Changed

Trusted Named Location Added or Changed detection rules

An attacker adds their IP range to a named location marked as trusted, or edits an existing one, so Conditional Access policies that exempt trusted locations stop requiring MFA or blocking their sign-ins.

Platform
Microsoft Entra ID
Severity
High
Log source
Microsoft Entra ID audit logs
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
Conditional Access Administrator, Security Administrator or Global Administrator, and Conditional Access policies that treat trusted locations differently.
Impact
The attacker's network is treated as a corporate location, so MFA and block policies scoped to untrusted locations no longer apply to their sign-ins.
Response
Remove the ranges that are not yours from the named location, then revoke the sessions of the accounts that signed in from them and treat them as compromised.
Mitigation
Protect named location changes as protected actions that require phishing-resistant MFA, and avoid broad MFA exemptions for trusted locations.
Audit activities
Add named locationUpdate named location

How the attack works

Named locations in Microsoft Entra ID are IP ranges or countries that Conditional Access policies include or exclude. Many tenants exempt locations marked as trusted from MFA, from block rules, or from risk policies, and Microsoft Entra ID Protection also uses trusted locations to lower risk detections. Changing a named location therefore changes the effect of every policy that references it, without touching the policies themselves.

An attacker with Conditional Access Administrator or Security Administrator rights adds their own IP range to a trusted location, creates a new trusted location, or removes a country from a blocked list. The Conditional Access service logs Add named location, Update named location and Delete named location; TargetResources holds the location definition, including its IP ranges and whether it is trusted.

What an attacker needs

  • A compromised identity with Conditional Access Administrator, Security Administrator or Global Administrator, or an application allowed to manage named locations.
  • Conditional Access policies that treat trusted or named locations differently.

Impact

The attacker's network is treated as a corporate location: MFA and block policies scoped to untrusted locations no longer apply to their sign-ins, and some risk signals are suppressed.

Detection rules

Named Location Added or Updated in Conditional Access

Detects a named location being created or modified. Check whether the location is marked as trusted and which IP ranges or countries it now contains, because policies that exempt the location change with it.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Named Location Added or Updated in Conditional Access
id: 16d428f1-9950-4969-96ab-53730977e274
status: experimental
description: >-
  Detects a named location being created or modified. Check whether the
  location is marked as trusted and which IP ranges or countries it now
  contains, because policies that exempt the location change with it.
references:
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-assignment-network
author: Forestall
date: 2026-11-10
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.t1556.009
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName:
      - Add named location
      - Update named location
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Network changes such as a new office or VPN egress range; confirm the range belongs to the organization and that a change record exists.
level: medium

False positives

  • Network changes such as a new office or VPN egress range; confirm the range belongs to the organization and that a change record exists.

Triage

  • Open the location definition in TargetResources and compare the new IP ranges and trust flag with your documented egress addresses.
  • Confirm the actor (InitiatedBy) and a change record; look up who owns any new range.
  • List the Conditional Access policies that reference the location to understand what the change exempts.
  • Check sign-ins from the new ranges after the change; if unauthorized, revert the location and investigate the actor.

Response

Once the attack is confirmed:

  1. Revert the named location. Remove the ranges that are not yours, remove the trusted mark from a location the attacker created and delete it, and put back a country that was taken out of a blocked list.
  2. Find the sign-ins from the added ranges while the change was in place, and do not expect risk detections for them, because trusted locations lower risk. Revoke the sessions of those accounts and treat them as compromised.
  3. Revoke the sessions and reset the credentials of the identity that changed the location, and remove its Conditional Access Administrator or Security Administrator role.
  4. Compare every named location with your documented egress addresses, and review the policies that reference the changed location.

Mitigation

  • Protect named location changes as protected actions that require phishing-resistant MFA.
  • Avoid broad MFA exemptions for trusted locations; use device-based controls instead of IP trust where possible.
  • Keep trusted ranges small and documented, and review them regularly against your egress IP inventory.

Frequently asked questions

No Conditional Access policy was edited, so why does this change matter?

A named location is referenced by policies, so changing it changes the effect of every policy that includes or excludes it. The policies themselves are untouched, and an alert on policy changes stays silent. The attacker's network is simply treated as a corporate location.

Does the rule match a named location being deleted?

No. The Conditional Access service logs `Add named location`, `Update named location` and `Delete named location`, and the rule matches the first two. Add the third activity if your policies depend on a location, for example a list of blocked countries.

Does a trusted location affect anything besides Conditional Access?

Yes. Microsoft Entra ID Protection uses trusted locations to lower risk detections. Sign-ins from a range the attacker added can therefore show less risk than they should, so review them by their IP address and not by their risk level.

What does a legitimate change look like?

A new office or a new VPN egress range that belongs to the organization and has a change record. Compare the new ranges and the trusted flag in TargetResources with your documented egress addresses, and look up who owns any range you do not know.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.