Skip to content

Commit a3a3596

Browse files
authored
Update disallowed-resources.md
1 parent 41af677 commit a3a3596

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/governance/policy/tutorials/disallowed-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ Now that you assigned a built-in policy definition, go to [All Services](https:/
8888
Now suppose that one subscope should be allowed to have the resource types disabled by this policy. Let's create an exemption on this scope so that otherwise restricted resources can be deployed there.
8989

9090
> [!WARNING]
91-
> If you assign this policy definition to your root management group scope, Azure portal is unable to detect exemptions at lower level scopes. Resources disallowed by the policy assignment will show as disabled from the **All Services** list and the **Create** option is unavailable. However, users may still create resources on the exempted scope using other clients such as CLI, PowerShell or ARM deployments.
91+
> If you assign this policy definition to your root management group scope, Azure portal is unable to detect exemptions at lower level scopes. Resources disallowed by the policy assignment will show as disabled from the **All Services** list and the **Create** option is unavailable. But you can create resources in the exempted scope with clients like Azure CLI, Azure PowerShell, or Azure Resource Manager templates.
9292
9393
1. Select **Assignments** under **Authoring** in the left side of the Azure Policy page.
9494

0 commit comments

Comments
 (0)