Skip to main content
daily-triage/entra-id-conditional-access-blocks-users-named-location-edit.md
Daily Triage Briefing

Entra ID Conditional Access Blocks Users After Named Location Edit

Impact Summary

In a fictional Microsoft Entra ID exercise, users are blocked after a named location edit. Sign-in logs and the Conditional Access What If tool identify the policy and location responsible. Confirm product behaviour in vendor documentation before acting.

SeveritySEV-2
StatusResolved simulation
PlatformSecurity & Identity
Incident TypeSecurity & Identity
Published7 Nov 2026
Technologies Involved
Microsoft Entra ID

Simulation Label

Fictional simulation. This exercise is a bounded, invented training scenario for practising operational reasoning. No real organisation, incident, telemetry, credentials or production identifiers are involved or implied.

Operational Summary

Root Cause

A named location edit cleared the trusted flag, so a block policy that excluded trusted locations began matching office users.

Detection Method

Evidence-led guided investigation

Current Status

Resolved simulation

Affected Services

Microsoft Entra ID

Incident Overview

At the start of a fictional working day, staff at the invented company Contoso Example report that sign-in fails with a message saying access has been blocked. A colleague edited a named location the previous evening to add a new office range.

Help desk reports say the problem affects office users and some remote users, but not everyone.

Investigation Options

Review the available operational moves and select the best immediate action.

A

Review the audit entry and What If result, then restore the trusted flag through change control with peer review

B

Disable the block policy for all users immediately without further investigation

C

Add every affected user to a policy exclusion list

D

Reset passwords and MFA methods for all affected users

Tags:Microsoft Entra ID