Hi NLE JB
Azure Database for MySQL Flexible Server offers a stop/start feature that is designed specifically for development and test environments to help reduce costs when the server isn’t actively in use. When you stop the server:
Compute Costs: The server’s compute resources are not billed while it is stopped, which means you won't incur compute charges during downtime.
Storage Costs: You will still be charged for storage, as the data files and backups continue to be maintained.
Please note that if a server remains stopped for 30 consecutive days, it will automatically start, so you'll need to plan accordingly if you intend to keep it inactive for extended periods.
For more details on how to stop and start your MySQL Flexible Server and manage cost optimization for development environments, please refer to the>> Stop/Start an Azure Database for MySQL Flexible Server instance documentation.
I hope this answers your question. Please let me know if you need any further clarification or assistance.
If this answers your query, do click "Accept the answer” for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.