The request did not have a subscription or a valid tenant level resource provider.

Question

The request did not have a subscription or a valid tenant level resource provider.

Arun Kumar 5

When i trying to run command

az ad sp create-for-rbac --role="Contributor" --scopes="/subscription/<<Subscription ID>>"

I am getting error as

(MissingSubscription) The request did not have a subscription or a valid tenant level resource provider.

Code: MissingSubscription

Message: The request did not have a subscription or a valid tenant level resource provider.

I just created a new azure account where Free Trial subscription is available with subscription ID

Sandeep G-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-09-13T10:56:18.35+00:00

@Arun Kumar

I am working on this thread. I am able to reproduce this issue on my lab. i will check for solution and will keep you updated.

5 answers

Your answer

Sandeep G-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-09-13T10:56:18.35+00:00

@Arun Kumar

I am working on this thread. I am able to reproduce this issue on my lab. i will check for solution and will keep you updated.

Answer 1

Staffan Hedström - HMS 100

Hello!

I just ran into this issue. This had worked before but for me the issue was the first forward slash / after --scopes. So this works:

az role assignment create --assignee <appId> --role Contributor --scope subscriptions/<subscriptionId>

But not:

az role assignment create --assignee <appId> --role Contributor --scope /subscriptions/<subscriptionId>

Christer Blomqvist 0 Reputation points

2025-06-24T09:43:15.59+00:00

In Git Bash you can solve this by setting MSYS_NO_PATHCONV=1 to tell it to not try and convert any absolute Unix style path to a Windows style path.

So, this will work fine:
MSYS_NO_PATHCONV=1 az role assignment create --assignee <appId> --role Contributor --scope /subscriptions/<subscriptionId>

Answer 2

Garsha Rostami 126

I ran into a similar situation as @Staffan Hedström - HMS reporting. I think this is a bug in some terminals such as git bash. Like Staffan, I had to remove the leading "/" in "/subscriptions".

Christer Blomqvist 0 Reputation points

2025-06-24T09:44:48.91+00:00

It is a feature where Git Bash must behind the scenes convert Unix style paths to Windows style paths.

Setting MSYS_NO_PATHCONV=1 tells Git Bash to not try and convert any absolute Unix style path to a Windows style path. So, this will work fine:
MSYS_NO_PATHCONV=1 az role assignment create --assignee <appId> --role Contributor --scope /subscriptions/<subscriptionId>

Answer 3

Sandeep G-MSFT 20,911 Microsoft Employee Moderator

@Arun Kumar

Command line az ad sp create-for-rbac --role="Contributor" --scopes="/subscription/<<Subscription ID>>" is incorrect.

You will have to mention as "Subscriptions" in the command line instead you have mentioned as Subscription.

You can use below command line to fix the issue,

az ad sp create-for-rbac --role 'Contributor' --scopes '/subscriptions/<<Subscription ID>>'

Let me know if you have any further questions on this.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Givary-MSFT 35,626 Reputation points Microsoft Employee Moderator

2023-10-06T07:29:18.9066667+00:00

@Arun Kumar Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back.

Please remember to "Accept Answer" if answer helped, so that others in the community facing similar issues can easily find the solution.

Answer 4

Luis Cantero 10

According to the following SO thread, using a double slash just before subscription should work, e.g.: --scopes="//subscription/<<Subscription ID>>" https://stackoverflow.com/questions/69453392/az-tag-update-error-missingsubscription-the-request-did-not-have-a-subscripti

João Pedro Bervalt 5 Reputation points

2024-02-06T16:34:19.02+00:00

As you said, this "double slash" should work. However, I tried using the subscription ID with double and single slash. In my case, both worked fine, I think it was corrected in some update.

Answer 5

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

3 deleted comments

Comments have been turned off. Learn more

Share via

The request did not have a subscription or a valid tenant level resource provider.

5 answers

Your answer