# Policy effect

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

The single action an Azure Policy definition takes when its rule matches: deny, audit, modify, deployIfNotExists and others. The effect decides whether a request is blocked, logged, changed or followed by a deployment. Each definition carries exactly one effect, and parameters can let assignments choose among several.

## An example, sourced

Microsoft documents that each policy definition "has a single effect in its policyRule." The listed effects include addToNetworkGroup, append, audit, auditIfNotExists, deny, denyAction, deployIfNotExists, disabled, manual, modify and mutate. The order of evaluation puts disabled first, then append and modify, then deny, then audit, then denyAction last. Microsoft also notes that audit, deny, and either modify or append are often interchangeable, while manual is not, and disabled can replace any effect.

## Why it matters here

Because modify runs before deny, a policy can change a request so that a deny never fires. Define the effect order for each definition you stack. The effect is the setting you change when you move from reporting to blocking. Treat it as a parameter, not as a redesign.

## Related pages

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

## Sources

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

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/glossary/policy-effect/
