Long wait times on subscription limit increases

Question

Hi, I have several tickets open for increasing my customer's subscription creation limit beyond the default 5, as we're building them out an Azure Landing Zone and they are keeping billing within an MCA / corporate card on demand invoice under a new section.

These tickets are seeing no responses or traction after multiple weeks, and this customer is on a tight timeline to exit their current data centers.

Any advice?

The customer is currently on the basic support plan but from what I can tell upgrading the plan doesn't seem to help the turnaround time for billing or subscription issues.

Answer 1

Hello Evan, I hear you—waiting weeks for subscription-limit increases when you’re on a tight datacenter exit timeline is super painful. Here’s what you can try to speed things up:

1. Make sure you’re opening the right kind of support request
   • In the Azure portal go to Help + support → New support request
   • Issue type: “Service and subscription limits (quotas)”
   • Subscription: pick your MCA billing account
   • Quota type: “Subscription creation limits”
   • In the details, spell out how many subscriptions you need, why (landing-zone build-out + datacenter exit), and your target date
2. Explicitly call out the business impact
   • Under the “Severity” or “Business impact” section, note that this is blocking your customer’s migration off legacy datacenter infrastructure—ask for a Priority 2 or billing-escalation handling
3. If you’re still not seeing movement after you submit or update the ticket:
   • Use the Azure billing support phone line for your region (go to Help → Support + troubleshooting → Contact us, then choose “Billing” and “Phone”)
   • If you have an Azure account team or Technical Account Manager, loop them in and ask them to escalate on your behalf
4. In the meantime, evaluate whether you can consolidate dev/test workloads into resource groups or management groups instead of separate subscriptions—this can buy you time if you only need logical isolation

Reference docs for your engineer response:

• Message appears when you try to create multiple subscriptions (explains the default 5-per-MCA and 1-per-24 h limits): https://learn.microsoft.com/azure/cost-management-billing/troubleshoot-subscription/create-subscriptions-deploy-resources
• Azure subscription and service limits, quotas, and constraints (shows subscription creation limits section): https://learn.microsoft.com/azure/azure-resource-manager/management/azure-subscription-service-limits
• How to create an Azure support request (walks you through the portal steps): https://docs.microsoft.com/azure/azure-portal/supportability/how-to-create-azure-support-request

Hope that helps get those extra subscriptions unlocked a bit faster—let me know how it goes or if you need more help!

Answer 2

For Microsoft Customer Agreement (MCA) subscriptions created directly through Azure.com, subscription creation is intentionally throttled and limited:

• Maximum of five subscriptions per MCA billing account purchased directly through Azure.com.
• Only one new subscription can be created per 24-hour period.
• The ability to create additional subscriptions beyond these defaults is determined individually based on the customer’s Azure usage history.
• All existing subscriptions should generate consumption history before creating another one.

When hitting these limits, the expected behavior is that subscription creation is delayed and may show messages like “Subscription not created. Please try again later.” This is by design and not directly controlled by the support plan level.

For a landing zone build-out under tight timelines, the only supported escalation path in this context is via support requests to Microsoft, but the platform still enforces the above constraints. The guidance is:

1. Ensure existing subscriptions are actually being used so they generate consumption history; this is a prerequisite before additional subscriptions are allowed.
2. Plan around the one-subscription-per-24-hours behavior and the five-subscription cap when designing the landing zone rollout.
3. If the current tickets are stalled, continue working through Azure support, as subscription creation limits and exceptions are handled on a case-by-case basis by Microsoft based on the customer’s history with Azure.

Support plan upgrades do not bypass these MCA subscription-creation rules; they only affect support responsiveness for technical issues, not the underlying subscription-governance policies.

For broader landing zone planning, use the Cloud Adoption Framework guidance on subscription vending and billing design to structure how subscriptions are requested and managed under the MCA.

---

References:

• Message appears when you try to create multiple subscriptions
• Plan for the Microsoft customer agreement service