Subscription 'Microsoft Azure Sponsorship' is not allowed to provision in 'xxxx'.

Question

Subscription 'Microsoft Azure Sponsorship' is not allowed to provision in 'xxxx'.

Russell Dudley 0

Hi,

I'm currently getting the following error trying to deploy a new MySQL db:

Subscription 'Microsoft Azure Sponsorship' is not allowed to provision in 'UK South'.

I've tried several different regions UK, Europe and US and receive the same error.
How can I tell what regions this subscription has access to? Copilot in Azure Portal thinks we should have access to all?

Do I need to request access to a specific region?
Any help is greately appreciated.

Many thanks

Russ

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-07-18T22:07:47.9933333+00:00
Hi @Russell Dudley ,

Thanks for raising on PCS. This "not allowed to provision" on a Sponsorship subscription is usually an offer-level regional entitlement issue on the MySQL RP, not a standard quota problem. A few quick asks to pinpoint the exact block before we escalate.

Please share (privately in this case, not on the public thread):

Subscription ID and full offer / quotaId: az account show --subscription

Full deployment error blob from Deployment logs, including: correlationId and x-ms-request-id UTC timestamp of the failed attempt Exact MySQL Flexible Server SKU you're trying to deploy (tier + vCores, e.g. Burstable/GP, MySQL version, storage size, HA on/off)

Output of: az provider show -n Microsoft.DBforMySQL --query "registrationState" az mysql flexible-server list-skus --location uksouth -o table (if output is empty, run for another region you tried too)

Output of: az policy assignment list --scope /subscriptions/ --query "[?contains(displayName, 'location')]" (to rule out a tenant-level policy pinning allowed locations).
Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-07-19T22:53:44.6633333+00:00

Hi @Russell Dudley

Quick note on why the four asks matter, so it's clear this isn't just a data dump each output points at a different root cause and lets us route the case correctly on first touch:

What each check tells us

Subscription ID + offer/quotaId confirms this is truly the MS-AZR-0143P (Sponsorship) offer. Sponsorship has a smaller regional footprint on Azure Database for MySQL Flexible Server than PAYG/CSP, and the "not allowed to provision" wording is the RP-level offer entitlement check firing.

Full error blob + correlationId + x-ms-request-id lets the MySQL backend team look up the exact denial reason and which regional entitlement gate rejected the request. Without this, they can only guess.

az provider show -n Microsoft.DBforMySQL + az mysql flexible-server list-skus --location <region> if registrationState isn't Registered, that's a self-serve fix and no escalation needed. If SKU list comes back empty in every region you tried, that confirms Sponsorship regional entitlement gap on the MySQL RP that's the path where we escalate to the Azure Database for MySQL PG.

az policy assignment list for location policies rules out a tenant admin having pinned "Allowed Locations" via Azure Policy at MG/subscription scope. If a policy is denying the region, it's a tenant governance fix, not a Microsoft-side entitlement issue.

Ranked most-likely causes

Sponsorship offer regional entitlement gap on Microsoft.DBforMySQL/flexibleServers needs backend/PG action.

Microsoft.DBforMySQL RP not registered on the subscription self-serve: az provider register --namespace Microsoft.DBforMySQL.

Azure Policy "Allowed Locations" assignment at MG or subscription scope needs tenant admin to update/exempt.

Region genuinely not offered on Sponsorship for MySQL Flexible Server today switch to a supported region (which we'll confirm from list-skus output).

Once you share the four outputs privately, I'll map straight to which of the four this is and either give you the fix or route to the MySQL backend team with the correlationId.
Vinodh247-1375 43,746 Reputation points Volunteer Moderator

2026-07-29T04:31:58.0033333+00:00
Please confirm if you had a chance to try any of the suggestions provided for your question.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful.

If in case you have any resolution please share the same here with the community as it can be helpful to others. Else, please respond with more details and we will try to see if we can help further.

2 answers

Your answer

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-07-18T22:07:47.9933333+00:00

Hi @Russell Dudley ,

Thanks for raising on PCS. This "not allowed to provision" on a Sponsorship subscription is usually an offer-level regional entitlement issue on the MySQL RP, not a standard quota problem. A few quick asks to pinpoint the exact block before we escalate.

Please share (privately in this case, not on the public thread):

Subscription ID and full offer / quotaId: az account show --subscription

Full deployment error blob from Deployment logs, including: correlationId and x-ms-request-id UTC timestamp of the failed attempt Exact MySQL Flexible Server SKU you're trying to deploy (tier + vCores, e.g. Burstable/GP, MySQL version, storage size, HA on/off)

Output of: az provider show -n Microsoft.DBforMySQL --query "registrationState" az mysql flexible-server list-skus --location uksouth -o table (if output is empty, run for another region you tried too)

Output of: az policy assignment list --scope /subscriptions/ --query "[?contains(displayName, 'location')]" (to rule out a tenant-level policy pinning allowed locations).
Vinodh247-1375 43,746 Reputation points Volunteer Moderator

2026-07-29T04:31:58.0033333+00:00

Please confirm if you had a chance to try any of the suggestions provided for your question.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful.

If in case you have any resolution please share the same here with the community as it can be helpful to others. Else, please respond with more details and we will try to see if we can help further.

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

This is expected behaviour for a azure sponsorship subs, not a regional discovery issue. Sponsorship (creditbased) subscriptions have restricted SKUs and regions, and services like azure db for MySQL are often blocked entirely or limited to specific tiers/regions, which is why every region you try fails. There is no direct “allowed regions list” exposed for this subscription type; the limitation is enforced at deployment time. You cannot request region access for Sponsorship, your options are to either try a different pricing tier (ex: Flexible Server vs Single Server if applicable), switch to a Payg subscription, or use an alternative service that is permitted under Sponsorship.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Answer 2

This is not a vCore quota error. Microsoft documents that program subscriptions, including Sponsorship and Microsoft for Startups offers, can have a limited set of regions for MySQL Flexible Server, and regional capacity can further restrict a subscription.

First confirm the Microsoft.DBforMySQL resource provider is registered under Subscriptions > Resource providers. You can also run az mysql flexible-server list-skus --location uksouth -o table for each region. That shows available SKUs, but it does not guarantee your sponsorship subscription is entitled to deploy there.

Because the same error appears in several regions, open an Azure support request using Service and subscription limits (quotas), select Azure Database for MySQL Flexible Server, then request Region access. Include the subscription ID, target region, SKU, vCore count, HA/zone choice, failed deployment timestamp, and correlation ID. Requests are reviewed against capacity and are not guaranteed. Meanwhile, test an alternate region or smaller SKU without zone-redundant HA.