Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
MySQL Flexible Server — firewallRules PUT returns HTTP 500 on api-version 2025-06-01-preview
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 60%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAV%3C/text%3E%3C/svg%3E)
Andy Veal
0
Reputation points
Creating/updating a firewall rule on an Azure Database for MySQL Flexible Server fails 100% of the time with HTTP 500 InternalServerError when the request uses API version 2025-06-01-preview. The same server responds normally to GET on the same API version, and the same PUT succeeds on GA API version 2023-12-30. The error body carries only a Tracking ID and no actionable detail. This is not transient — it reproduces on every attempt across multiple days and survives a 5× retry with exponential backoff.
Affected resource
| Resource type | Microsoft.DBforMySQL/flexibleServers (+ child firewallRules) |
| -------- | -------- |
| Resource type | Microsoft.DBforMySQL/flexibleServers (+ child firewallRules) |
| Server name | ctdev |
| Resource group | devtest |
| Region | UK South (from x-ms-routing-request-id: UKSOUTH:...) |
publicNetworkAccess |
Enabled (no VNet delegation; delegatedSubnetResourceId / privateDnsZoneResourceId both null) |
| Server state | [confirm: Ready] |
(InternalServerError) An unexpected error occured while processing the request. Tracking ID: '<guid>'
Code: InternalServerError
Message: An unexpected error occured while processing the request. Tracking ID: '<guid>'
No inner error.code, no x-ms-failure-cause surfaced to the client. Request fails during FirewallRules_CreateOrUpdate long-running-operation initiation (_create_or_update_initial).
Azure Database for MySQL
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 49%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESJ%3C/text%3E%3C/svg%3E)
SAI JAGADEESH KUDIPUDI 3,645 Reputation points Microsoft External Staff Moderator2026-09-05T22:05:00.84+00:00 Hi @Andy Veal ,
Could you please share the requested details in a private message so we can take a closer look and assist you further? -
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 71%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
Smaran Thoomu 35,870 Reputation points Microsoft External Staff Moderator2026-09-10T05:47:26.0533333+00:00 Hi @Andy Veal
Thank you for providing the detailed information and troubleshooting results.Based on the observations shared, we understand that the FirewallRules CreateOrUpdate (PUT) operation consistently fails with HTTP 500 InternalServerError when using the 2025-06-01-preview API version, while:
- GET operations succeed using the same preview API version.
- The same PUT operation succeeds using the GA API version 2023-12-30.
- The issue is consistently reproducible and not transient in nature.
Given these findings, this behavior may indicate an issue specific to the 2025-06-01-preview API implementation rather than a configuration problem on the MySQL Flexible Server itself.
To investigate further, could you please provide details in private message:
- The complete Tracking ID(s) returned in the error response.
- A sample request payload (with any sensitive information masked).
- Correlation ID / x-ms-request-id from the failed request, if available.
- Approximate timestamp of a recent failed attempt (UTC).
As a temporary workaround, we recommend continuing to use the supported GA API version 2023-12-30, which appears to successfully perform the firewall rule creation/update operation.
Once we receive the above information, we can validate whether this is a known issue or a potential regression in the preview API and engage the product group if required.
We appreciate your patience and look forward to your response.
Sign in to comment
Sign in to answer