liveBook · Manning

Policy effect

A policy effect is the outcome specified for a resource or authorization request when a policy applies, such as allowing, denying, or modifying it.

How 2 Manning books explain it

Azure Security

A policy effect is the outcome Azure Policy applies when evaluating a resource against a policy definition.

How it is used
Controls whether Azure Policy reports, blocks, or changes resource deployments that match a policy rule.
How deep it goes
Defines effect selection and request ordering, then details Audit, Deny, and Modify without enumerating every available effect.
Examples
Uses allowed virtual machine SKUs, required tags, noncompliance messages, and resource-group exemptions as operational examples.
What you can do after
Operate/configure Azure Policy by observing compliance, preventing noncompliant deployments, or applying missing configuration.

Read how Azure Security explains policy effect →

Authorization in Action

An effect is the policy element that specifies the outcome produced when a policy applies, such as allowing or denying access.

How it is used
Defines whether an applicable authorization policy grants or denies an action.
How deep it goes
Explains permit, forbid, and deny-overrides, but defers detailed Cedar syntax and deeper evaluation mechanics.
Examples
Uses deployment restrictions, confidential-document access, ownership, and managed-device conditions to contrast permit and forbid policies.
What you can do after
Apply it via Cedar by distinguishing granting rules from overriding denial constraints in an authorization policy.

Read how Authorization in Action explains policy effect →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.