Can't create Azure subscription - and need a support plan ...

Question

Can't create Azure subscription - and need a support plan ...

Matthias Fleschütz 26

Hi Folx,

I am running into an issue with our test Azure tenant to create a subscription...and strangely enough - I need a support plan to get support from MSFT on Subscription issues...

Sorry MSFT - I need to pay to get support to be able to purchase your stuff...really?

Does anybody has an idea?

I have a Billing account + Profile setup up with credit card
We created two invoice sections
I create a new subscription, pick all items and click create and receive an error

Failed to create "MYPREFIX_alz_pltf-connectivity" subscription.
Sorry, we couldn't create "MYPREFIX_alz_pltf-connectivity" subscription, please try again or contact Azure Support

All public resources, KB / Learn pages, even Copilot didn't help.

Thanks a lot for any ideas.

Sina Salam 20,106 Reputation points Moderator

2025-05-04T23:40:34.6566667+00:00
Hello Matthias Fleschütz,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you cannot create Azure subscription - and need a support plan.

To resolve the issue, try to follow the below steps:

Ensure that your billing and shipping details are correct and match your bank records - https://learn.microsoft.com/en-us/azure/cost-management-billing/troubleshoot-subscription/troubleshoot-azure-sign-up

Check that the billing address for the credit card registration matches your bank records - https://learn.microsoft.com/en-us/azure/cost-management-billing/troubleshoot-subscription/troubleshoot-azure-sign-up

If your account (email using for registration) is registered in an unmanaged directory, it might not be supported for Azure subscriptions. You may need to perform an IT Admin Takeover process to convert it into a managed directory - https://learn.microsoft.com/en-us/azure/cost-management-billing/troubleshoot-subscription/cannot-sign-up-subscription. For example, ******@gmail.com is an unmanaged directory. To use Azure services, Alice would need to perform an IT Admin Takeover to convert this directory into a managed one or signs up using your work email such as ******@company.com. Company email means you already has a managed directory.

If you are trying to create multiple subscriptions in a short period, you might receive a message stating: "Subscription not created. Please try again later." This is normal and expected - https://learn.microsoft.com/en-us/azure/cost-management-billing/troubleshoot-subscription/create-subscriptions-deploy-resources

About Azure Support Plans:

To get technical support, you might need to purchase a support plan. These are some options:

Developer Plan: $29 per month, suitable for trial and non-production environments.

Standard Plan: $100 per month, intended for production workload environments.

Professional Direct Plan: $1,000 per month, aimed at businesses with critical dependence on Azure.

For more detail use the link: https://azure.microsoft.com/en-us/support/plans/

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.
Matthias Fleschütz 26 Reputation points

2025-05-05T05:08:52.7666667+00:00

Hi @Sina Salam

thanks a lot. That is all set, we could create subs but adding a second is now failing.

Experienced the same by API now. There we get too many requests, so maybe there is some kind of rate limit of # of subscriptions you can create in one go?

about support plans: we know them and we have them in our prod environment. However, I thinking’s a little strange to have to have some for subscription issues! Again, you have to pay to get your issues resolved to be able to purchase things…what?

that’s like I need a paid entrance ticket for a shop to be allowed to buy stuff…
Sina Salam 20,106 Reputation points Moderator

2025-05-05T08:53:36.2166667+00:00

Hello Matthias Fleschütz,

Good that all is set.

Azure API Management does indeed have rate limits to prevent usage spikes. When the call rate exceeds the limit, you receive a 429 Too Many Requests response - https://learn.microsoft.com/en-us/azure/api-management/rate-limit-policy This is likely what's happening in your case.

Regarding support plans, I understand but don't let it frustrate you. Azure provides basic subscription management and billing support for all customers at no additional cost - https://azure.microsoft.com/en-us/support/legal/faq/. However, technical support for resolving issues typically requires a paid support plan - https://azure.microsoft.com/en-us/support/plans/ This structure ensures that more complex, technical issues are handled efficiently by dedicated support teams.

If you need help with subscription management or billing, you can access support without a paid plan. For technical issues, the support plans offer various levels of service to match different needs and budgets - https://azure.microsoft.com/en-us/support/plans

Success.
Matthias Fleschütz 26 Reputation points

2025-05-05T09:01:54.6966667+00:00

HI @Sina Salam , ok that makes technically sense - BUT: I was adding a second via API and got that...even now on the next day, 12 hours later...? And I couldnt find any public documentation on that limit.
Sina Salam 20,106 Reputation points Moderator

2025-05-05T09:30:08.49+00:00

Hello Matthias Fleschütz,

Regarding your feedback.

Review your API Management instance's rate limit settings to ensure they align with your usage needs. You can configure rate limits at different scopes: global, product, or API-specific.

If your current limits are too restrictive, consider increasing the allowed number of calls or extending the renewal period. This can be done by modifying the rate-limit policy in your API Management instance.

If you continue to experience issues, reaching out to Azure support can provide more personalized assistance. They can help you troubleshoot and adjust settings to better fit your needs.
Matthias Fleschütz 26 Reputation points

2025-05-05T10:23:31.57+00:00

Hi @Sina Salam hm strange...I have the feeling that this particular throttling is not a generic one, because all other API calls are working. As I do not have any other direct API integration and use it "manually" I am also pretty sure nothing else uses the limits. It really seems it is only about creating a new subscription - the same way as I get the error in the portal.
Sina Salam 20,106 Reputation points Moderator

2025-05-05T10:36:17.8433333+00:00

Hi Matthias Fleschütz,

I don't understand what you mean by API throttling, you might need to recreate other queries for API, also do not forget to post screenshot and error you're having.

We have been able to solve subscription and support plan issue, thank you and let's close this thread.

Success.

Matthias Fleschütz 26

Hi @Sina Salam

"throttling" is just another term for "rate limit".
So basically I see:

no use of the Azure Management API at all from our end / my user for 12 hours
2 subscriptions created manually yesterday
--> could not add a third one manually in the portal
then added the 3rd subscription by API yesterday late the evening
--> cant add another one because of API error, all other API calls are working without any issue

{
    "error": {
        "code": "TooManyRequests",
        "message": "Subscription is not created. Please try again later. {\"error\":{\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"},\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"}"
    },
    "code": "TooManyRequests",
    "message": "Subscription is not created. Please try again later. {\"error\":{\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"},\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"}"
}

User's image

Best & Thanks again,
Matthias

Matthias Fleschütz 26 Reputation points

2025-05-05T20:11:36.51+00:00

Hi @Srinivasa Reddy Jaggavarapu

thanks for confirming my assumption. However, this is really bad. I now had to wait 25 hours to add another subscription. I can't believe that this is sufficient for any proper organization according to Microsoft's principle of subscription democratization :-(

Curious how this behaves with IaC subscription vending...

Best,
Matthias

P.S. Can't accept your answer as it is a reply.
Ashok Gandhi Kotnana 6,680 Reputation points Microsoft External Staff Moderator

2025-05-06T09:38:12.3366667+00:00

Hi @Matthias Fleschütz

Common Causes of Subscription Creation Errors:

1.Lack of proper billing role for the invoice section

Even if you’re a billing account owner, to create a subscription under a specific invoice section, you need to be assigned as:

Billing profile contributor and

Invoice section owner or contributor

2.Invoice section not active or misconfigured

If the section is closed, blocked, or over budget, it can reject new subscriptions.

3.Tenant lacks active Azure Sponsorship or permissions for subscription creation

Especially in test or dev tenants, Azure sometimes restricts subscription creation for non-verified tenants unless certain prerequisites are met.

4.Credit card issues

Even if saved, if the card can’t be charged during setup (some require a $0 or $1 verification), the subscription creation may fail.

Next Action Plan Please check the following:

1.Verify Invoice Section Permissions (Most Likely Fix)

Make sure you're an Invoice Section Contributor under:

Billing account > Billing profile > Invoice section

Without that role, subscription creation silently fails.

2.Try Manual Subscription Creation

Go to Cost Management + Billing > Subscriptions > +Add

Select the same billing profile and invoice section — does it still fail?

3.Open a Support Request – You Can Do This Without a Support Plan

Go to Help + Support > New Support Request

Use “Subscription Management” → “Can't create an Azure subscription with my account”

This category doesn’t require a support plan

References: -

https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/understand-mca-roles https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/programmatically-create-subscription-microsoft-customer-agreement?tabs=rest https://learn.microsoft.com/en-us/azure/cost-management-billing/microsoft-customer-agreement/troubleshoot-subscription-access

Please let me know if you face any challenge here, I can help you to resolve this issue further

Provide your valuable Comments.
Ashok Gandhi Kotnana 6,680 Reputation points Microsoft External Staff Moderator

2025-05-06T18:49:03.88+00:00

Hi Matthias Fleschütz,

You should be able to see now.

Thank you for letting us know. I will converted @Srinivasa Reddy Jaggavarapu comment into an answer. If you could kindly "accept answer"for the benefit of the community, it would be greatly appreciated and helpful to others.

Accepted answer

0 additional answers

Your answer

Matthias Fleschütz 26 Reputation points

2025-05-05T05:08:52.7666667+00:00

Hi @Sina Salam

thanks a lot. That is all set, we could create subs but adding a second is now failing.

Experienced the same by API now. There we get too many requests, so maybe there is some kind of rate limit of # of subscriptions you can create in one go?

about support plans: we know them and we have them in our prod environment. However, I thinking’s a little strange to have to have some for subscription issues! Again, you have to pay to get your issues resolved to be able to purchase things…what?

that’s like I need a paid entrance ticket for a shop to be allowed to buy stuff…
Sina Salam 20,106 Reputation points Moderator

2025-05-05T08:53:36.2166667+00:00

Hello Matthias Fleschütz,

Good that all is set.

Azure API Management does indeed have rate limits to prevent usage spikes. When the call rate exceeds the limit, you receive a 429 Too Many Requests response - https://learn.microsoft.com/en-us/azure/api-management/rate-limit-policy This is likely what's happening in your case.

Regarding support plans, I understand but don't let it frustrate you. Azure provides basic subscription management and billing support for all customers at no additional cost - https://azure.microsoft.com/en-us/support/legal/faq/. However, technical support for resolving issues typically requires a paid support plan - https://azure.microsoft.com/en-us/support/plans/ This structure ensures that more complex, technical issues are handled efficiently by dedicated support teams.

If you need help with subscription management or billing, you can access support without a paid plan. For technical issues, the support plans offer various levels of service to match different needs and budgets - https://azure.microsoft.com/en-us/support/plans

Success.
Matthias Fleschütz 26 Reputation points

2025-05-05T09:01:54.6966667+00:00

HI @Sina Salam , ok that makes technically sense - BUT: I was adding a second via API and got that...even now on the next day, 12 hours later...? And I couldnt find any public documentation on that limit.
Sina Salam 20,106 Reputation points Moderator

2025-05-05T09:30:08.49+00:00

Hello Matthias Fleschütz,

Regarding your feedback.

Review your API Management instance's rate limit settings to ensure they align with your usage needs. You can configure rate limits at different scopes: global, product, or API-specific.

If your current limits are too restrictive, consider increasing the allowed number of calls or extending the renewal period. This can be done by modifying the rate-limit policy in your API Management instance.

If you continue to experience issues, reaching out to Azure support can provide more personalized assistance. They can help you troubleshoot and adjust settings to better fit your needs.
Matthias Fleschütz 26 Reputation points

2025-05-05T10:23:31.57+00:00

Hi @Sina Salam hm strange...I have the feeling that this particular throttling is not a generic one, because all other API calls are working. As I do not have any other direct API integration and use it "manually" I am also pretty sure nothing else uses the limits. It really seems it is only about creating a new subscription - the same way as I get the error in the portal.
Sina Salam 20,106 Reputation points Moderator

2025-05-05T10:36:17.8433333+00:00

Hi Matthias Fleschütz,

I don't understand what you mean by API throttling, you might need to recreate other queries for API, also do not forget to post screenshot and error you're having.

We have been able to solve subscription and support plan issue, thank you and let's close this thread.

Success.
Matthias Fleschütz 26 Reputation points

2025-05-05T11:43:27.9833333+00:00

Hi @Sina Salam

"throttling" is just another term for "rate limit".
So basically I see:

no use of the Azure Management API at all from our end / my user for 12 hours

2 subscriptions created manually yesterday
--> could not add a third one manually in the portal

then added the 3rd subscription by API yesterday late the evening
--> cant add another one because of API error, all other API calls are working without any issue

{ "error": { "code": "TooManyRequests", "message": "Subscription is not created. Please try again later. {\"error\":{\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"},\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"}" }, "code": "TooManyRequests", "message": "Subscription is not created. Please try again later. {\"error\":{\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"},\"code\":\"TooManyRequests\",\"message\":\"Subscription is not created. Please try again later.\"}" }

Best & Thanks again,
Matthias
Matthias Fleschütz 26 Reputation points

2025-05-05T20:11:36.51+00:00

Hi @Srinivasa Reddy Jaggavarapu

thanks for confirming my assumption. However, this is really bad. I now had to wait 25 hours to add another subscription. I can't believe that this is sufficient for any proper organization according to Microsoft's principle of subscription democratization :-(

Curious how this behaves with IaC subscription vending...

Best,
Matthias

P.S. Can't accept your answer as it is a reply.
Ashok Gandhi Kotnana 6,680 Reputation points Microsoft External Staff Moderator

2025-05-06T18:49:03.88+00:00

Hi Matthias Fleschütz,

You should be able to see now.

Thank you for letting us know. I will converted @Srinivasa Reddy Jaggavarapu comment into an answer. If you could kindly "accept answer"for the benefit of the community, it would be greatly appreciated and helpful to others.

Answer 1

Hi Matthias Fleschütz,

Azure enforces rate limits on creating subscriptions to prevent abuse and ensure service availability. This is why you are encountering throttling (rate limit), after creating multiple subscriptions within a short time frame. The "TooManyRequests" error is Azure's way of signaling that you have hit this limit.

Azure rate limits are usually temporary. They reset automatically after a cooling period, which can range from minutes to several hours (sometimes longer for subscription creation). Since you already waited 12+ hours, try again after 24 hours.

When using the Azure Management API, implement retry logic with exponential backoff. This ensures your retries do not overwhelm the system.

Sometimes, limits may be specific to your test tenant or directory. If possible, try creating the subscription in another tenant or check if policies like Management Group limitations are affecting subscription creation.

Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.

Please click Accept Answer and upvote if the above was helpful.

Ashok Gandhi Kotnana 6,680 Reputation points Microsoft External Staff Moderator

2025-05-07T11:07:31.0966667+00:00

Hi Matthias Fleschütz,

You should be able to see now.

Thank you for letting us know. I have converted @Srinivasa Reddy Jaggavarapu comment into an answer. If you could kindly "accept answer" for the benefit of the community, it would be greatly appreciated and helpful to others.

Share via

Can't create Azure subscription - and need a support plan ...

0 additional answers

Your answer