Azure Database for MySQL flexible server: Regional provisioning issue in UK South — ProvisionNotSupportedForRegion error

Question

Azure Database for MySQL flexible server: Regional provisioning issue in UK South — ProvisionNotSupportedForRegion error

D C 20

Problem description

I am attempting to enable Accelerated Logs on an existing Azure Database for MySQL Flexible Server in the UK South region.

When enabling Accelerated Logs in the Azure portal, the operation fails with:

ProvisionNotSupportedForRegion

The error states that provisioning in the requested region is not supported and that the subscription may not have access to provision the requested configuration in that region.

Environment

Azure Database for MySQL Flexible Server
Region: UK South
Existing server
Service tier: General Purpose
Compute: Standard_D2ds_v4 (2 vCores)
Storage: 85 GB
High availability / redundancy: Locally redundant

The only configuration change being attempted is enabling Accelerated Logs.

What I've already tried

I confirmed that the Microsoft.DBforMySQL resource provider is registered for the subscription.

I also ran:

az mysql flexible-server list-skus --location uksouth -o table

This consistently returns:

(InternalServerError) An unexpected error occured while processing the request.
Code: InternalServerError

I have repeated the command several times and received the same error with different tracking IDs.

For comparison, running the same command against another region such as eastus succeeds and returns the available MySQL Flexible Server SKUs.

Current status

The issue continues to occur when enabling Accelerated Logs in UK South.

UK South is required for this workload, so moving the server to another region is not an appropriate workaround.

I am trying to determine whether:

Accelerated Logs is currently supported for this configuration in UK South.
There is a regional restriction or capacity issue affecting this operation.
The InternalServerError returned by list-skus for UK South is related to the same underlying issue.

Himaja Y 560 Reputation points Microsoft External Staff Moderator

2026-09-28T16:32:40.7733333+00:00

Hi @D C ,

Thank you for your patience. We are currently coordinating with our internal engineering team regarding the ticket that was raised for this issue. We are actively tracking the investigation and will share an update with you as soon as we receive further information from the team. We appreciate your understanding and will keep you informed of any progress.
D C 20 Reputation points

2026-10-06T16:10:23.01+00:00

@Himaja Y Hello! Hope you are doing well, is there an update on this?
D C 20 Reputation points

2026-10-12T10:25:03.12+00:00

Hi @Himaja Y - Is there any update on this?

This issue has now been ongoing for over two weeks without any further update.

As this appears to require investigation on the Azure side, is it possible for this PCS request to be referred directly to Azure Support so I can track the case and request updates there?

At the moment, I’m concerned the request has effectively stalled with no clear next step or owner.

Thanks!

2 answers

Your answer

Himaja Y 560 Reputation points Microsoft External Staff Moderator

2026-09-28T16:32:40.7733333+00:00

Hi @D C ,

Thank you for your patience. We are currently coordinating with our internal engineering team regarding the ticket that was raised for this issue. We are actively tracking the investigation and will share an update with you as soon as we receive further information from the team. We appreciate your understanding and will keep you informed of any progress.
D C 20 Reputation points

2026-10-06T16:10:23.01+00:00

@Himaja Y Hello! Hope you are doing well, is there an update on this?
D C 20 Reputation points

2026-10-12T10:25:03.12+00:00

Hi @Himaja Y - Is there any update on this?

This issue has now been ongoing for over two weeks without any further update.

As this appears to require investigation on the Azure side, is it possible for this PCS request to be referred directly to Azure Support so I can track the case and request updates there?

At the moment, I’m concerned the request has effectively stalled with no clear next step or owner.

Thanks!

Answer 1

Hi D C & thx for join me at Q&A platform,

UK South is listed as a supported region for Accelerated Logs, and the General Purpose tier is supported too. So ur Standard_D2ds_v4 configuration isn't obviously unsupported just because of the region or compute tier. One thing I'd check first is whether the existing server has an availability zone assigned. Accelerated Logs requires one, and Microsoft specifically recommends opening a support case for servers that don't have a zone allocated. U can check the server's availabilityZone property using az mysql flexible-server show.

The InternalServerError from list-skus is also interesting. That command should return SKU availability information, not fail with an internal error. The fact that it works in East US but consistently fails in UK South suggests there may be a regional resource-provider issue, although it doesn't prove that both errors have the same cause.

I'd also check the Activity Log for the failed Accelerated Logs update and capture the full error response, including the operation and correlation IDs. If the server already has an availability zone assigned, I'd avoid changing its compute size or storage configuration just to work around this error. At this point, I'd raise a case with the Azure Database for MySQL Flexible Server team and ask them to check Accelerated Logs eligibility for this specific server, any UK South provisioning restrictions, and the backend failures from list-skus. Include the tracking IDs from both operations.

I wouldn't assume this is a capacity shortage or subscription restriction yet. The feature is documented as supported in UK South, but only Microsoft can confirm whether there's a current service-side restriction affecting ur subscription or server.

rgds,

Alex

D C 20 Reputation points

2026-10-12T11:14:54.8933333+00:00

Hi Alex!

Thanks for your response. Someone had posted a very similar answer on this previously, but it looks like that response has since been removed.

I originally raised this through Azure Support, which redirected me here under Priority Community Support. If I try to raise it again, I’m directed back to creating a new Q&A post.

So I think at this stage I’m really waiting for this to be picked up and referred back to the Azure/MySQL support team for further investigation.

Thanks!

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

1 deleted comment

Comments have been turned off. Learn more