# Policy assignment

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

The Azure object that applies a policy definition or initiative to a scope and supplies its parameters. The assignment decides which resources are evaluated, the enforcement mode, the excluded scopes, and any overrides of the effect. It can also exclude subscopes.

## An example, sourced

Microsoft documents that "policy assignments define which resources are evaluated by a policy definition or initiative," and that the assignment can set parameter values at assignment time. The page describes notScopes for exclusions and says one assignment can hold up to 10 overrides, each covering up to 50 policy definition reference IDs. Microsoft also documents that exclusions set with notScopes can be added or updated after the assignment is created.

## Why it matters here

Most Azure guardrail behavior lives in the assignment, not the definition. Review the scope, mode and exclusions of an assignment before reading its rule. A definition can look right while its assignment is wrong. Read both when a guardrail fails to block, and check the assignment for the scope and mode first.

## Related pages

- [Policy exemption: meaning and an example](/glossary/policy-exemption/)
- [Policy initiative: meaning and an example](/glossary/policy-initiative/)
- [Management group: meaning and an example](/glossary/management-group/)
- [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/policy-assignment/
