MySQL Flexible Server stuck in Stopped - ProvisionNotSupportedForRegion blocks both start and point-in-time restore (Central US)

Fundación Colaboración y Esfuerzo 0 Reputation points
2026-08-12T02:17:52.2666667+00:00

A production MySQL Flexible Server has been down since 2026-08-11

14:37 UTC. A scheduled stop completed normally, but the server will no

longer start. Every operation that requires compute allocation now fails.

SERVER

Central US, Availability Zone 1

Standard_B1ms (Burstable), 20 GB Premium_LRS

MySQL 8.0.21, current state: Stopped

Backup retention 7 days, geo-redundant backup DISABLED

WHAT FAILS

  1. Start server: InternalServerError Tracking ID: b57af522-084f-4840-9796-c37b0c27bc25
  2. Scale compute (to move off the Burstable family): ServerNotExist - "The server does not exist or in unexpected status." ARM returns the resource properties correctly, but the MySQL RP cannot operate it.
  3. Point-in-time restore - tried AZ 1, AZ 2, AZ 3 and no zone preference, with both Burstable and GeneralPurpose tiers: ProvisionNotSupportedForRegion Async operation: 6d2b35d2-20f8-4f47-aef5-eb9a7fddbc35
  4. Creating a new server in Central US via the portal: same error - subscription is not allowed to provision in Central US.
  5. GET /providers/Microsoft.DBforMySQL/locations/centralus/capabilities returns 500 InternalServerError on both api-version 2023-12-30 and 2025-06-01-preview. This makes the Azure CLI restore command abort before it sends the restore request. Tracking ID: cccae9b8-83dd-4e2a-91de-e190402bb4b4

ALREADY RULED OUT

  • Storage: 3.5% used, autogrow enabled.
  • Permissions: same failures with an interactive user account, not only with the automation identity.
  • Quota exhaustion: Quotas page shows standardBSFamily at 1 of 64 (2%) and standardDADSv5Family at 0 of 128.
  • Availability zone capacity: all three zones fail identically.
  • Single SKU family: restore also fails with Standard_D2ads_v5, a family the Quotas page shows as unrestricted. This suggests the restriction is at subscription/region level, not per family.

The Quotas troubleshooting flow for standardBSFamily reports "Additional

quota isn't available for this family" and its "Contact Support" option

is greyed out, so regional access cannot be requested through that path.

Geo-restore is unavailable since geo-redundant backup was disabled, so

point-in-time restore within Central US is the only recovery

Azure Database for MySQL

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator
    2026-08-29T07:24:29.5866667+00:00

    Hi @Fundación Colaboración y Esfuerzo

    Apologies for the delay on our end - we want to make sure you have every available option to unblock this as quickly as possible.

    In addition to the internal escalation in progress, there is a self-service path you can try right now in parallel that may resolve the ProvisionNotSupportedForRegion error directly:

    Request Region Access for Central US via a Quota Support Request

    This is the correct path when the Quota UI's "Contact Support" button is greyed out - it bypasses that limitation entirely.

    Steps:

    1. Go to Create a Support Request in the Azure Portal
    2. Set Issue type to: Service and subscription limits (quotas)
    3. Set Service to: Azure Database for MySQL Flexible Server
    4. On the Additional details tab:
      1. Under Quota type, select: Region access
      2. Select Central US as the required region
      3. Specify the cores needed (at minimum 2 cores for Standard_B1ms, but request what you need for restore - e.g. 4-8 cores to cover both Burstable and GeneralPurpose)
    5. In the Description field, include:
      • Your server has been in Stopped state since Aug 11 and cannot start
      • Point-in-time restore is also failing with ProvisionNotSupportedForRegion
      • The /capabilities endpoint is returning 500 for Central US
      • This is a production outage - request expedited review
    6. Submit the request

    Why this may work: The ProvisionNotSupportedForRegion error, combined with the capabilities endpoint returning 500 and the greyed-out quota UI, is consistent with Central US not being in your subscription's approved region list for MySQL Flexible Server. A region access approval typically resolves all of these symptoms at once - including unblocking the point-in-time restore.

    This does not replace the internal escalation - please do both simultaneously. The quota support request may resolve faster since it goes directly to the capacity team.

    Please let us know once you have submitted the request and share the support request number so we can reference it in our internal escalation as well.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.