My Resource Group not deleting. But I can't access Permissions.

GA 0 Reputation points
2025-11-24T15:41:28.5366667+00:00

I have created multiple resource groups and now I want to delete them. But now allowing me to delete. Says I have to check my Permissions. But I can't get to Permissions for that resource group.

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-11-24T15:41:36.18+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To delete a resource group in Azure, you need to have the appropriate permissions, specifically the permission to perform the delete action on the resource group. If you are unable to access the permissions for that resource group, it may be due to a lack of access rights or roles assigned to your account.

    Here are some steps you can take:

    1. Check Role Assignments: If you have access to the Azure portal, check if you have been assigned a role that includes the necessary permissions to delete resource groups. You typically need at least the Contributor role.
    2. Contact an Administrator: If you do not have the required permissions, you may need to contact someone with administrative rights in your Azure subscription to either grant you the necessary permissions or delete the resource group on your behalf.
    3. Check for Locks: Sometimes, resource groups can be locked, preventing deletion. Ensure there are no locks applied to the resource group that might be causing the deletion to fail.
    4. Resource Dependencies: Make sure that there are no dependencies preventing the deletion. For instance, if resources within the group are linked to resources in other groups, this can also block deletion.

    If you have the necessary permissions but the deletion still fails, it might be due to one of the issues mentioned above.


    References:

    0 comments No comments

  2. Praneeth Maddali 2,350 Reputation points Microsoft External Staff Moderator
    2025-11-25T04:41:26.6533333+00:00

    Hi @GA

    Thanks for reaching out this is a very common situation when you're a Global Administrator in Microsoft Entra ID but haven’t yet turned on the “elevate access” switch for Azure resources. Without that, Azure RBAC treats you as having no permissions on subscriptions or resource groups, which explains both the deletion error and why the Access control (IAM) blade is completely greyed out for you.

    Could you please follow below steps to fix the issue :

    1. Sign in to the Azure Portal.
    2. Navigate to Microsoft Entra ID and select Properties from the Manage section in the left menu.
    3. Find Access management for Azure resources by scrolling down.
    4. Change the toggle from No to Yes and save. This will grant you Owner rights for all subscriptions in the tenant immediately.

    After completing that step, refresh the portal or sign out and back in, then try deleting the resource group again—it should work immediately. If you still encounter an error after elevation, the next likely cause is a CanNotDelete lock on the resource group or subscription. To check and remove the lock, go to Resource Group > Locks and delete any lock you find.

    Once you have completed the cleanup, please remember to set the elevation toggle back to 'No' to maintain adherence to the least-privilege principle.

    Reference:

    https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin?tabs=azure-portal%2Centra-audit-logs

    https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources?tabs=json

    Kindly let us know if the above comment helps or you need further assistance on this issue.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.