Share via

how to fix You do not have permissions to create resource groups under subscription

Jeffrey Wilds 25 Reputation points
Mar 15, 2024, 2:30 PM

You do not have permission to create resource groups under subscription

Azure Resource Mover
Azure Resource Mover
An Azure service used for moving multiple resources between Azure regions.
241 questions
0 comments No comments
{count} vote

Accepted answer
  1. Adrian Chirtoc 116 Reputation points
    Mar 20, 2024, 2:37 PM

    I think I have the same issue.. any fix? Is there a bug?

    1 person found this answer helpful.

5 additional answers

Sort by: Most helpful
  1. Michael Taylor 55,216 Reputation points
    Mar 15, 2024, 2:35 PM

    Please provide more information about your situation. The error itself indicates you do not have the necessary permissions in Azure for your subscription to create resource groups. Someone with admin rights in your subscription would need to grant you permissions to create resource groups as discussed here.

    You used a tag of Azure Resource Mover which leads me to believe that there is more to your situation then just a simple permissions issue but without further details we'd only be guessing.

    0 comments No comments

  2. Jeffrey Wilds 25 Reputation points
    Mar 15, 2024, 5:32 PM

    IAM at the subscription level settings are as follows:

    Current Role Assignments -> Classic Administrator -> Service Administrator ->

    Has full access to all resources in the subscription.

    I am still unable to create a resource group to deploy Azure resources in.


  3. Jeffrey Wilds 25 Reputation points
    Mar 15, 2024, 5:35 PM

    That was the only tag available that was close to my situation.

    0 comments No comments

  4. Jeffrey Wilds 25 Reputation points
    Mar 15, 2024, 5:38 PM

    I did until yesterday. I wonder if this has anything to do with this (see below):

    Transition to role-based access control (RBAC) in Azure by 31 August 2024

    You're receiving this notice because you use Azure classic administrator roles.

    On 31 August 2024, Azure classic administrator roles will be retired. If your organization has active Co-Administrator or Service Admin roles, you'll need to transition to using Azure RBAC roles by then. (All Azure classic resources and Azure Service Manager will also be retired on that date.)

    You may continue using these Azure classic admin roles until they're retired. However, starting 3 April 2024, you'll no longer be able to add new Co-Administrator roles through the Azure portal.


Your answer

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