# IAM deny policy

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

A Google Cloud IAM policy of deny rules attached to a project, folder or organization. Each rule names principals and permissions the principals cannot use. IAM evaluates deny policies before allow policies, so a role grant cannot override one. It is evaluated first.

## An example, sourced

Google documents that deny policies "let you set guardrails on access to Google Cloud resources by creating deny rules that prevent certain principals from using certain permissions." When a principal is denied a permission, they cannot use it regardless of the roles they hold, because IAM always checks relevant deny policies before allow policies. A deny on an organization applies to every resource inside it.

## Why it matters here

IAM deny is the Google Cloud equivalent of an SCP deny for permissions. A deny at the organization level cannot be loosened by a more permissive policy below it. IAM deny is Google's counterpart of an SCP deny for permissions. A deny at the organization level cannot be loosened by a more permissive policy below it, so keep exceptions in conditions.

## Related pages

- [VPC Service Controls perimeter: meaning and an example](/glossary/vpc-service-controls-perimeter/)
- [Principal access boundary: meaning and an example](/glossary/principal-access-boundary/)
- [Guardrail: meaning and an example](/glossary/guardrail/)
- [All of them](/glossary/)

## Sources

- https://cloud.google.com/iam/docs/deny-overview (read 10 Nov 2026)

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