This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
![168115-capture1.png][1] [1]: /api/attachments/168115-capture1.png?platform=QnA
Hi anonymous user ,
any details if you click on Policy details ?
Is your user allowed to create new Resource Groups? Are there any policies related to "create new Resource Groups" defined?
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
Actually I use my official mail id for azure account is there way to change mail id for these with same subscription.
Hi anonymous user ,
it doesn't matter which email you are using to logon to the Azure subscription. It's just a question regarding the permission your account have in the subscription.
Also the error message is maybe pointing to a policy. For that reason I asked what are the details of the error message.
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten
![168289-capture3.png][1] [1]: /api/attachments/168289-capture3.png?platform=QnA It showing like this please check out this
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 39%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
anonymous user It seems like a transient issue. If you are still not able to verify the policy assignment. I would recommend you to raise a support request by following the steps mentioned in this document.