Provisioning errors with MySQL Flexible Server

Question

Provisioning errors with MySQL Flexible Server

JD Robinson 0

An existing Azure Database for MySQL Flexible Server is running in East US 2. A password-only update fails with ProvisionNotSupportedForRegion. The subscription already has 64 Burstable-family vCores in East US 2, with only 2 in use. Please enable or repair the subscription’s Microsoft.DBforMySQL regional provisioning entitlement for East US 2. This request is for an update to an existing server, not additional vCore quota.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-07-14T01:12:00.1+00:00

Hi @JD Robinson ,
Is the failing action a password-only update via portal, CLI, or Terraform/ARM?

Do you see the same error when you try the update in another region (or is this server pinned to East US 2)?

If the issue still exists, please share the requested details in a private message so we can investigate further.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-07-18T08:09:51.94+00:00

Hi @JD Robinson ,
To help us continue the backend investigation and review the service logs, could you please share the requested details via private message, including the server resource ID, correlation ID (if available), UTC timestamp of the failed operation, and any recent deployment changes?

Once we receive the information, we will coordinate with the relevant team and provide you with further updates.

1 answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-07-14T01:12:00.1+00:00

Hi @JD Robinson ,
Is the failing action a password-only update via portal, CLI, or Terraform/ARM?

Do you see the same error when you try the update in another region (or is this server pinned to East US 2)?

If the issue still exists, please share the requested details in a private message so we can investigate further.
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator

2026-07-18T08:09:51.94+00:00

Hi @JD Robinson ,
To help us continue the backend investigation and review the service logs, could you please share the requested details via private message, including the server resource ID, correlation ID (if available), UTC timestamp of the failed operation, and any recent deployment changes?

Once we receive the information, we will coordinate with the relevant team and provide you with further updates.

Answer 1

Hi, because even a password-only update is returning ProvisionNotSupportedForRegion, this is unlikely to be your password or ARM syntax. It normally points to the server's current SKU/availability-zone combination or a regional subscription entitlement/capacity restriction. Please export the server properties and activity-log failure, then try a harmless update through CLI only once to capture the correlation ID. Do not delete the server as a workaround. Open a MySQL Flexible Server support case with the server resource ID, region, SKU, zone, API version, operation name, correlation ID, and UTC time, and ask the service team to check the regional provisioning stamp/entitlement for that existing server.