Skip to content
Cloud Governance Tools

Not allowed resource types

Not allowed resource types is an Azure guardrail written in Azure Policy. Denies deployment of the resource types you list, for example expensive or high-risk services. What it breaks: a deny effect returns 403 for any create or update of a listed type, and compliance results are shown only for non-compliant resources.

More resource and cost guardrails ยท About Azure Policy

Built-in policy definition: Not allowed resource types
Definition ID: 6c112d4e-5bc7-47ae-a041-ea2d9dccd749
Category: General
Supported effects: Audit, Deny, Disabled
policyRule (copied from the repository file):
{
    "if": {
      "allOf": [
        {
          "field": "type",
          "in": "[parameters('listOfResourceTypesNotAllowed')]"
        },
        {
          "value": "[field('type')]",
          "exists": true
        }
      ]
    },
    "then": {
      "effect": "[parameters('effect')]"
    }
  }
Blocks
Denies deployment of the resource types you list, for example expensive or high-risk services.
Breaks
A deny effect returns 403 for any create or update of a listed type, and compliance results are shown only for non-compliant resources. (source)
Test before applying
As for every Azure Policy guardrail: how to test before enforcing
Mechanism
Azure Policy (built-in definitions): Resources at the scope of the assignment (management group, subscription, resource group) and their children, except notScopes and exemptions
Taken from
open source set, MIT License, Azure/azure-policy repository, https://raw.githubusercontent.com/Azure/azure-policy/master/LICENSE

What the source says

"Restrict which resource types can be deployed in your environment." (read 10 Nov 2026).

On what it breaks: "Compliance results are only shown for non-compliant resources."

Sources

  1. Not allowed resource types, read 10 Nov 2026
  2. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.