An Azure managed MySQL database service for app development and deployment.
Welcome to Microsoft Q&A.
Hello @Jan , I hope you are doing well.
This likely appears to be a regional capacity or subscription access restriction rather than an issue with the User Assigned Managed Identity itself. What is happening is that when Azure Database for MySQL Flexible Server attempts to associate the managed identity for Microsoft Entra authentication, the platform performs a regional validation check and is unable to provision the required backend resources in the selected region.
The fact that the Managed Identity already has the Directory Readers role assigned suggests that the identity configuration is likely correct.
To resolve this issue, please check the following:
- Verify that the MySQL Flexible Server is deployed in North Europe and that the issue occurs consistently when assigning the User Assigned Managed Identity.
- Create a support request under Service and subscription limits (quotas) and select Azure Database for MySQL Flexible Server.
- Choose Region access and request access for the North Europe region.
- Include the server name, subscription ID, region, and timestamp of the failed operation in the support request.
If Microsoft confirms a regional constraint, they will either:
- Enable the required regional access for your subscription, or
- Recommend an alternative supported region for this scenario.
For additional information, please review:
- Azure Database for MySQL regional constraints: https://learn.microsoft.com/azure/mysql/flexible-server/resolve-capacity-errors#regional-constraints
- Microsoft Entra authentication for Azure Database for MySQL: https://learn.microsoft.com/azure/mysql/flexible-server/how-to-azure-adT
I hope this information helps.
If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!