# Enforcement mode

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

A property of an Azure Policy assignment that controls whether the effect is applied. In DoNotEnforce the assignment is evaluated and compliance is reported, but the effect is not enforced on create or update and no activity log entry is written for it.

## An example, sourced

Microsoft documents the enforcementMode property with the values Default, DoNotEnforce and Enroll. DoNotEnforce is described as useful when you want to evaluate the assignment before enforcement, for testing a new assignment or validating policy logic. Remediation tasks for deployIfNotExists policies can still be started when the mode is DoNotEnforce. The Enroll value applies the effect only to resources enrolled in the assignment, which suits adding subscopes in batches.

## Why it matters here

DoNotEnforce is Azure's built-in report-only phase. Run it for a full evaluation cycle before switching an assignment to Default. It is the lowest-risk way to see the effect of an Azure guardrail on real resources. A policy in DoNotEnforce is easy to forget, so give each such assignment a review date and an owner.

## Related pages

- [Policy assignment: meaning and an example](/glossary/policy-assignment/)
- [Policy exemption: meaning and an example](/glossary/policy-exemption/)
- [Policy initiative: meaning and an example](/glossary/policy-initiative/)
- [All of them](/glossary/)

## Sources

- https://learn.microsoft.com/en-us/azure/governance/policy/concepts/assignment-structure (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/enforcement-mode/
