General Availability of the MySQL Flexible Server Quota Management Self-Service Experience

What’s New? 

The updated experience introduces a dedicated Azure Database for MySQL Flexible Server Quotas blade in the Azure portal, offering a streamlined and intuitive interface to: 

• View current usage and limits across the various SKU families and regions 
• Request quota increases tailored to your MySQL Flexible Server deployment needs 

This new experience empowers developers, DBAs, and IT admins to proactively manage resources, avoid deployment failures, and optimize database performance — all without needing to file a support ticket for most scenarios.  

Benefits at a Glance 

How It Works 

1. Each MySQL Flexible Server compute tier is represented as a separate SKU family. If you intend to scale up or down within a specific tier, ensure you have sufficient quota for each applicable SKU family in that tier. 
2. You can filter by region, subscription, provider, or usage. Note that your portal will show "Azure Database for MySQL Flexible Server" for the Provider name. 
3. You can also group the results by usage, quota (SKU family), or location (region). 
4. Current usage is represented as vCores. This allows you to quickly identify which SKU families are nearing their quota limits. 
5. Adjustments can be made inline: there is no need to visit another page. This is covered in detail in the next section. 

Step-by-Step: Viewing Usage and Requesting a Quota Increase 

Step 1: Navigate to the Quotas Blade 

• Sign in to the Azure portal at https://portal.azure.com. 
• In the search bar at the top, type "Quotas". 
• Select "Quotas" from the search results under Services. 

Alternative navigation: You can also navigate via Subscriptions > select your subscription > Usage + quotas in the left-hand menu. 

Step 2: Select the Azure Database for MySQL Provider 

• On the Quotas page, locate and select "Azure Database for MySQL" from the list of resource providers. 

• Use the Subscription filter at the top to select the subscription you want to review and apply additional filters for regions as needed. 

Step 3: Review Your Quota Usage and Limits 

• The quota details page displays a table with the following information: 
  • Quota Name — The SKU family name (e.g., "Burstable BS Series vCores", "General Purpose DS Series vCores", "Business Critical DS Series vCores"). 
  • Region — The Azure region where the quota applies. 
  • Current Usage — The number of vCores currently in use. 
  • Limit — The maximum quota limit for that SKU family. 
  • Usage Bar — A visual indicator showing how much of the quota is consumed.
• Review the usage bars to identify quotas that are nearing their limits. Use the search box to find specific SKU families quickly. 

Step 4: Request a Quota Increase 

• Clicking the pen icon next to a quota opens a fly-out window to capture the quota request. 

Step 5: Enter the New Limit 

• The quota type (MySQL Flexible Server SKU family) is already populated, along with current usage. Note that your request is not incremental: you must specify the new limit that you wish to see reflected in the portal. 
• For example, to request an additional 10 vCores for Burstable Series (BS family), and your current limit is 35, you would enter 45 as the new limit. 
  • Enter the desired new limit in the "New limit" field. 
  • The portal will indicate whether the request can be automatically approved or if it requires manual review. 

Step 6: Submit and Monitor the Request 

• Click Submit to send the request for automatic processing. 
• Immediately upon submitting a quota request, you will see a processing dialog: 

• If the quota request can be automatically fulfilled, then no support request is needed. You should receive confirmation within a few minutes of submission: 

• If the request cannot be automatically fulfilled, then you will be given the option to file a support request with the same information: 

Step 7: Verify the Quota Increase 

• Navigate back to the Quotas blade and select the Azure Database for MySQL provider. 
• Confirm that the Limit column now reflects the new, increased value. 
• If you forget the region or SKU family that was requested, you can reference them in your notifications pane. 

Filing a Support Ticket 

• When creating a support ticket, you will need to repopulate the Region and MySQL Flexible Server SKU family details; the new limit has already been populated for you. 
• If you choose to create a support ticket, you will interact with the capacity management team for that region. This is a 24x7 service, so requests may be created at any time. Once you have filed the support request, you can track its status via the Help + support dashboard. 
• If your deployment requires quota for many subscriptions, then we recommend filing a support ticket with issue type "Service and subscription limits (quotas)" and quota type “Quota increase”: 

Known Limitations 

• Closing the quota request fly-out window will stop meaningful notifications for that request. You can still view the outcome of your quota requests by checking actual quota, but if you want to rely on notifications for alerts, we recommend leaving the quota request window open for the few minutes that it is processing. 

Feedback 

If you notice any aspect of the experience that does not work as expected or you have feedback on how to make it better, please share your thoughts! Your feedback is critical as we work toward an improved quota management self-service experience.