Azure MySQL Flexible Server Burstable Tier Opportunity
The burstable tier prices a baseline with credit-funded peaks, which is cheaper than a General Purpose tier sized for a peak that arrives rarely.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Move the MySQL flexible server to a burstable tier. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- MySQL Flexible on Azure
- The fix, by hand
- Open Portal → Azure Database for MySQL flexible servers → the resource → Metrics, capture CPU baseline over the last 14 days.
- Confirm the baseline stays well under each Burstable tier's credit baseline (e.g. B2s ≈ 40% credit baseline).
- Open Compute + storage, switch tier to Burstable, pick the smallest size that satisfies baseline + headroom.
- Acknowledge the restart prompt and Save.
- Watch CPU Credits Remaining for the first week.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-244- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.