Azure Database for MySQL flexible server: Quota limitations prevent upgrade — Request for quota increase

Question

Azure Database for MySQL flexible server: Quota limitations prevent upgrade — Request for quota increase

webdev-2380 0

Problem description

I am attempting to upgrade my existing Azure Database for MySQL Flexible Server from version 8 to version 8.4 using an ARM template that deploys both the server and database together. Since August 14, 2026, each deployment attempt fails with a ResourceOperationFailure and the message "Not enough quota to provision or update the server for your subscription," leaving the provisioning state as "Failed." I am seeking assistance to resolve this quota issue.

Environment

Azure Database for MySQL Flexible Server, region not specified in the case information.

What I've already tried

I have submitted an ARM template deployment including the MySQL Flexible Server resource and its database, but each attempt results in a failure due to quota limitations.

Current status

The deployment continues to fail with the quota error. I am requesting guidance on verifying current quotas, submitting a quota increase request, and re-running the deployment once the quota is increased. The support ticket is useless and I am getting only AI responses.

Karnam Venkata Rajeswari 5,255 Reputation points Microsoft External Staff Moderator

2026-09-08T23:30:08.2666667+00:00

Hello @webdev-2380 ,

Thank you for reaching out to us

We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.

Thank you
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-09-09T04:36:18.1766667+00:00

Hi @webdev-2380
1. Navigate to this link to start the process:

https://portal.azure.com/#create/Microsoft.Support

2. Enter quota in the box and click Go

3. Select Others / Service and subscription limits (quotas) and click Next

4. Click Create a support request button, as shown

5. Select Issue type: Service and subscription limits (quotas), Subscription, Quota type: Azure Database for MySQL Flexible Server, click Next

6. Now you should be on Additional details tab. Click Enter details

7. Select Region access or Region access with zonal dependency, select Location you need, enter number of cores needed, click Save and continue

8. Finish filling out Additional details tab, click Next, review and click Create. You should receive an automated email within a few minutes.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-09-10T01:42:20.0233333+00:00

Hi @webdev-2380
Could you please let us know if you face any queries regarding,we are happy to help you.

1 answer

Your answer

Karnam Venkata Rajeswari 5,255 Reputation points Microsoft External Staff Moderator

2026-09-08T23:30:08.2666667+00:00

Hello @webdev-2380 ,

Thank you for reaching out to us

We have begun looking into it and will share our suggestions with you as soon as possible. If you have any additional details or concerns in the meantime, please let us know. We appreciate your patience while we work on this.

Thank you
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-09-09T04:36:18.1766667+00:00

Hi @webdev-2380
1. Navigate to this link to start the process:

https://portal.azure.com/#create/Microsoft.Support

2. Enter quota in the box and click Go

3. Select Others / Service and subscription limits (quotas) and click Next

4. Click Create a support request button, as shown

5. Select Issue type: Service and subscription limits (quotas), Subscription, Quota type: Azure Database for MySQL Flexible Server, click Next

6. Now you should be on Additional details tab. Click Enter details

7. Select Region access or Region access with zonal dependency, select Location you need, enter number of cores needed, click Save and continue

8. Finish filling out Additional details tab, click Next, review and click Create. You should receive an automated email within a few minutes.
Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-09-10T01:42:20.0233333+00:00

Hi @webdev-2380
Could you please let us know if you face any queries regarding,we are happy to help you.

Answer 1

The error message points to a quota or capacity validation failure rather than an ARM template syntax issue.

One angle that has not been mentioned yet is how the upgrade is being executed. Azure MySQL Flexible Server supports in-place major version upgrades from MySQL 8.0 to 8.4, but Microsoft recommends not combining the major version upgrade with other server property changes in the same REST API, SDK, or infrastructure deployment operation. If your ARM template updates the server configuration and database resources while also changing the engine version, Azure may reject the request during validation. [learn.microsoft.com], [docs.azure.cn]

I would check the deployment history and determine whether the template is changing anything other than the MySQL version, such as:

Compute tier or SKU
vCore count
Storage settings
High availability configuration
Network settings
Server parameters

If so, try separating the operation into steps:

Upgrade the existing Flexible Server from 8.0 to 8.4 only.
After the upgrade completes successfully, apply any other infrastructure or configuration changes in a separate deployment.

Also, verify whether the failure is truly a subscription quota issue or a regional capacity restriction. Microsoft documents both scenarios separately, and similar provisioning errors can occur when a region or SKU family is temporarily capacity constrained even when the deployment itself is valid. [learn.microsoft.com], [learn.microsoft.com]

Finally, check the Azure Portal -> Quotas blade for Azure Database for MySQL Flexible Server and confirm that sufficient vCore quota exists for the server's SKU family and region. Microsoft recently introduced self-service quota visibility and management specifically for MySQL Flexible Server, making it easier to verify the current limits before retrying the deployment. [learn.microsoft.com]

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.