An Azure service that provides fine-grained access management for Azure resources, enabling you to grant users only the rights they need to perform their jobs.
Hello Puttisate
Thank you for reaching out to the Microsoft Q&A forum.
We understand that your Resource Group delete is being blocked by a Deny assignment. Deny assignments in Azure are generally created by a Policy or Blueprint and can’t be manually removed from the Access control (IAM) blade. You’ll need to find and unassign or update the policy/blueprint that’s enforcing that deny.
Here’s what to try:
Check for Policy assignments
- In the Azure portal, go to Policy > Assignments.
- Filter the scope to your subscription or the Resource Group in question.
- Look for any assignment whose “Effect” is set to “Deny.”
- If you find one, click it and choose Unassign (or edit the assignment’s scope/exclusions so it no longer covers your RG).
Check for Blueprint assignments
- If your organization uses Azure Blueprints, go to Blueprints > Blueprint assignments.
- See if there’s an assignment targeting your subscription/RG that includes a deny policy.
- Unassign or delete that blueprint assignment.
(Optional) Use PowerShell/CLI to locate the deny assignment source
PowerShell example:
Get-AzRoleAssignment -Scope "/subscriptions/<subId>/resourceGroups/<rgName>" -IncludeDenyAssignments
CLI example:
az role assignment list --scope /subscriptions/<subId>/resourceGroups/<rgName> --include-deny
Note the DefinitionId or assignment name, then cross-reference that in your Policy or Blueprint blades.
Once the underlying policy or blueprint assignment is removed (or updated to exclude your RG), you should be free to delete the resource group as usual.
Hope that helps! Let me know if you don’t see any matching policy/blueprint and we’ll dig deeper.
References: