1. Resources
  2. Detection rules
  3. Conditional Access Policy Weakened or Deleted

Conditional Access Policy Weakened or Deleted detection rules

An attacker with Conditional Access rights disables, deletes or edits a policy (excluding their account, dropping MFA, switching it to report-only) so their sign-ins stop being challenged or blocked.

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
The Conditional Access Administrator, Security Administrator or Global Administrator role, or an application that can manage Conditional Access policies.
Impact
MFA, device and location requirements no longer apply to the attacker's sign-ins, and a deleted or disabled baseline policy can expose every user in the tenant.
Response
Restore the policy from the old value in the audit log or from your export, then revoke the sessions and reset the credentials of the identity that changed it.
Mitigation
Protect Conditional Access changes as protected actions that require phishing-resistant MFA, and limit the administrator roles to a few PIM-managed accounts.
Audit activities
Update AuthenticationContextClassReferenceDelete AuthenticationContextClassReferenceDelete named locationUpdate continuous access evaluationAdd Conditional Access policyUpdate Conditional Access policyDelete Conditional Access policyUpdate security defaults

How the attack works

Conditional Access is where a Microsoft Entra tenant enforces MFA, device compliance, location and risk requirements. A Conditional Access Administrator, Security Administrator or Global Administrator can change any policy. Attackers who reach one of these roles rarely delete policies outright; they add their account or a group they control to the exclusions, remove a grant control, narrow the targeted applications, or set the policy to report-only, which keeps it visible but stops enforcement.

Every change is logged by the Conditional Access service as Add Conditional Access policy, Update Conditional Access policy or Delete Conditional Access policy in the Policy category. TargetResources carries the full policy JSON before and after the change, so the exact difference can be reviewed. Tenants without Conditional Access rely on security defaults instead; turning them off is logged as Update security defaults. New policies are read by a rule of their own. Another rule reads changes to what the policies depend on: authentication contexts, named locations and the continuous access evaluation setting.

What an attacker needs

  • A compromised identity holding Conditional Access Administrator, Security Administrator or Global Administrator, or an application with permission to manage Conditional Access policies.

Impact

MFA, device and location requirements no longer apply to the attacker's sign-ins, which keeps stolen credentials and tokens usable and makes later persistence steps easier. A deleted or disabled baseline policy can expose every user in the tenant.

Detection rules

Conditional Access Dependency Changed or Deleted

Detects changes to three things Conditional Access policies depend on, none of which is a change to a policy itself: an authentication context is updated or deleted, a named location is deleted, or the continuous access evaluation setting is updated. An authentication context is the label that ties a policy to sensitive data, to an action in an application or to a protected action in Microsoft Entra ID. Microsoft warns that deleting a context that applications still use leaves access to their data without that protection. A named location that is deleted can no longer be used by the policies that block or trust it. Continuous access evaluation enforces a disabled account, a password reset or a change of network location in near real time. Microsoft lists the four activities for the Conditional Access service in the Policy category and documents their names only, so the rule matches the names. The object and its old and new values are in TargetResources. Additions and updates of named locations are covered by the page on trusted named locations.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Conditional Access Dependency Changed or Deleted
id: e45edc07-a085-4079-a66c-4bb63c43c17f
status: experimental
description: >-
  Detects changes to three things Conditional Access policies depend on, none
  of which is a change to a policy itself: an authentication context is
  updated or deleted, a named location is deleted, or the continuous access
  evaluation setting is updated. An authentication context is the label that
  ties a policy to sensitive data, to an action in an application or to a
  protected action in Microsoft Entra ID. Microsoft warns that deleting a
  context that applications still use leaves access to their data without
  that protection. A named location that is deleted can no longer be used by
  the policies that block or trust it. Continuous access evaluation enforces a
  disabled account, a password reset or a change of network location in near
  real time. Microsoft lists the four activities for the Conditional Access
  service in the Policy category and documents their names only, so the rule
  matches the names. The object and its old and new values are in
  TargetResources. Additions and updates of named locations are covered by the
  page on trusted named locations.
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-conditional-access-cloud-apps
  - https://learn.microsoft.com/en-us/entra/identity/role-based-access-control/protected-actions-overview
  - https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-continuous-access-evaluation
  - https://attack.mitre.org/techniques/T1556/009/
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.t1556.009
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName:
      - Update AuthenticationContextClassReference
      - Delete AuthenticationContextClassReference
      - Delete named location
      - Update continuous access evaluation
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Planned cleanup of authentication contexts and named locations that are no longer used, and the move of the continuous access evaluation setting into Conditional Access policies. Match the event to a change record.
level: medium

False positives

  • Planned cleanup of authentication contexts and named locations that are no longer used, and the move of the continuous access evaluation setting into Conditional Access policies. Match the event to a change record.

Conditional Access Policy Added

Detects the creation of a Conditional Access policy. Microsoft's security operations guide for infrastructure tells defenders to monitor new policies created by actors who are not approved to change Conditional Access (activity "Add Conditional Access policy", category Policy) and rates the event as medium risk. A new policy can do harm in two ways. A policy that blocks access for administrators or for all users locks the organization out of its own tenant. A policy that looks like protection, for example one in report-only mode or with wide exclusions, can be put in place before the real one is removed, so that a review of the policy list notices nothing. The full policy is in TargetResources. The rule matches every new policy, so it is rated low: alert on actors outside the team that owns Conditional Access.

LevelLowStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Conditional Access Policy Added
id: bcff5f8d-fbc6-4ff7-81e9-6a281cc7ecc0
status: experimental
description: >-
  Detects the creation of a Conditional Access policy. Microsoft's security
  operations guide for infrastructure tells defenders to monitor new policies
  created by actors who are not approved to change Conditional Access (activity
  "Add Conditional Access policy", category Policy) and rates the event as
  medium risk. A new policy can do harm in two ways. A policy that blocks
  access for administrators or for all users locks the organization out of its
  own tenant. A policy that looks like protection, for example one in
  report-only mode or with wide exclusions, can be put in place before the
  real one is removed, so that a review of the policy list notices nothing.
  The full policy is in TargetResources. The rule matches every new policy, so
  it is rated low: alert on actors outside the team that owns Conditional
  Access.
references:
  - https://learn.microsoft.com/en-us/entra/architecture/security-operations-infrastructure
  - https://learn.microsoft.com/en-us/entra/identity/conditional-access/troubleshoot-policy-changes-audit-log
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://attack.mitre.org/techniques/T1556/009/
author: Forestall
date: 2026-11-18
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.t1556.009
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName: Add Conditional Access policy
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - The identity team rolling out a new policy, often in report-only mode first. Match the event to a change record and exclude the accounts that are approved to manage Conditional Access.
level: low

False positives

  • The identity team rolling out a new policy, often in report-only mode first. Match the event to a change record and exclude the accounts that are approved to manage Conditional Access.

Conditional Access Policy Updated or Deleted

Detects an update to or deletion of a Conditional Access policy. Review the old and new values in TargetResources for new exclusions, removed grant controls or a switch to disabled or report-only.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Conditional Access Policy Updated or Deleted
id: cb9dcd0d-15bf-4185-9bb0-ea1069709aa9
status: experimental
description: >-
  Detects an update to or deletion of a Conditional Access policy. Review the
  old and new values in TargetResources for new exclusions, removed grant
  controls or a switch to disabled or report-only.
references:
  - https://learn.microsoft.com/en-us/entra/identity/conditional-access/troubleshoot-policy-changes-audit-log
  - https://learn.microsoft.com/en-us/entra/architecture/security-operations-infrastructure
author: Forestall
date: 2026-11-10
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.t1556.009
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName:
      - Update Conditional Access policy
      - Delete Conditional Access policy
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Routine policy maintenance by the identity team; filter the approved administrators or automation accounts in InitiatedBy and keep alerting on everyone else.
level: medium

False positives

  • Routine policy maintenance by the identity team; filter the approved administrators or automation accounts in InitiatedBy and keep alerting on everyone else.

Security Defaults Setting Changed

Detects a change to the tenant's security defaults. In tenants that rely on security defaults rather than Conditional Access, turning them off removes the MFA requirement and the legacy authentication block for every user.

LevelMediumStatusExperimentalLog sourceMicrosoft Entra ID audit logs
title: Security Defaults Setting Changed
id: 8e4051d8-36c5-42b3-9559-9a339c4b4b9c
status: experimental
description: >-
  Detects a change to the tenant's security defaults. In tenants that rely on
  security defaults rather than Conditional Access, turning them off removes
  the MFA requirement and the legacy authentication block for every user.
references:
  - https://learn.microsoft.com/en-us/entra/identity/monitoring-health/reference-audit-activities
  - https://learn.microsoft.com/en-us/entra/fundamentals/security-defaults
author: Forestall
date: 2026-11-10
tags:
  - attack.defense-impairment
  - attack.persistence
  - attack.t1556.009
logsource:
  product: azure
  service: auditlogs
detection:
  selection:
    OperationName: Update security defaults
  filter_failed:
    Result: failure
  condition: selection and not filter_failed
falsepositives:
  - Migration from security defaults to Conditional Access, which requires turning them off; confirm equivalent Conditional Access policies are enabled.
level: medium

False positives

  • Migration from security defaults to Conditional Access, which requires turning them off; confirm equivalent Conditional Access policies are enabled.

Detection logic

Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.

Member added to a group that a Conditional Access policy excludes

Detection hypothesisNeeds your own lists

An attacker who cannot or does not want to change a policy adds their account to a group the policy excludes. The policy stays untouched and the account is exempt. Microsoft's guidance asks for monitoring of the groups used to scope critical policies, which needs the list of those groups.

  1. Keep a list of the groups that your Conditional Access policies exclude, and of the groups your strictest policies include.
  2. Audit log, category GroupManagement: activity Add member to group for an excluded group, or Remove member from group for an included group, with the user as the target.
  3. Alert when the group is on the list, and check the actor in InitiatedBy and the sign-ins of the account afterwards.

EventsAdd member to groupRemove member from group

LimitsThe list has to follow every policy change. Exclusion groups for emergency access and service accounts change rarely, so start with those. A policy that excludes single users instead of groups is not covered here and shows as a policy update.

Policy weakened and restored shortly after

Detection hypothesisSequence of eventsCompares with an earlier value

An attacker who needs one sign-in to pass switches a policy to report-only or adds an exclusion, signs in, and puts the policy back, so that a later review finds it unchanged. Two updates of the same policy within a short time, where the second undoes the first, are that window.

  1. Audit log: Update Conditional Access policy, with the policy in TargetResources and its old and new value in the modified properties.
  2. Within 24 hours: a second Update Conditional Access policy for the same policy.
  3. Compare the new value of the second event with the old value of the first. If they are equal, the policy was changed and restored.
  4. Review the sign-ins between the two events that the policy would otherwise have blocked or challenged.

EventsUpdate Conditional Access policy

LimitsAdministrators who test a change and roll it back produce the same pair, so match it to a change record. The 24 hours are a starting point. A policy that stays weakened is covered by the single-event rule.

Triage

  • Compare the old and new policy JSON in TargetResources modifiedProperties; look for new exclusions, removed grant controls, a state change to disabled or report-only, or narrowed applications.
  • Confirm the actor (InitiatedBy) normally manages Conditional Access and that a change record exists.
  • Check sign-ins after the change for accounts that are no longer challenged, especially the actor's own and any newly excluded identity.
  • If unauthorized, restore the policy from your export and investigate the actor's session and other changes.

Response

Once the attack is confirmed:

  1. Restore the policy. Use the old value in TargetResources or your export to remove the new exclusion, put the grant control back and set the state to on. A deleted policy can be restored from the deleted policies list for 30 days.
  2. If security defaults were turned off in a tenant without Conditional Access, turn them back on.
  3. Revoke the sessions and reset the credentials of the identity that made the change, and remove its Conditional Access Administrator or Security Administrator role.
  4. Find the sign-ins that succeeded only because the policy was weakened, such as those of a newly excluded account. Revoke the sessions of those accounts and treat them as compromised.
  5. Compare every policy with your export, because the same actor may have changed others, and check the membership of the groups that policies exclude.

Mitigation

  • Protect Conditional Access changes as protected actions that require phishing-resistant MFA and an authentication context.
  • Limit Conditional Access Administrator and Security Administrator to a few PIM-managed accounts.
  • Keep exclusions in dedicated, monitored groups (break-glass accounts only) and review them with access reviews.
  • Export policies regularly (or manage them as code) so unexpected drift is visible.

Frequently asked questions

Can a deleted Conditional Access policy be restored?

Yes. Microsoft keeps a deleted policy for a 30 day soft-delete period, and a Conditional Access Administrator can restore it from the deleted policies list. During the restore you can choose report-only mode or the state the policy had when it was deleted. Review the restored policy before you rely on it.

Why is a switch to report-only treated like a deletion?

A policy in report-only mode stays visible in the list but is no longer enforced. Attackers prefer this and other quiet edits, such as a new exclusion or a removed grant control, to deleting a policy outright. Read the state of the policy in the old and the new values of the event.

Does the rule see an account added to a group that a policy excludes?

No. The rules match changes to the policy itself and to the objects it refers to. Adding a member to a group that a policy already excludes changes who is exempt without changing the policy, so it is logged as a group membership change. Keep exclusions in dedicated groups and monitor their membership.

How do I find what exactly changed in a policy?

TargetResources carries the full policy JSON before and after the change. Compare the two and look for new exclusions, removed grant controls, a state change to disabled or report-only, or a narrower list of applications.

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.