Here’s how to avoid hitting the limits on free Codespaces

Posted by

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Community Hub.

Before going through the suggestions, there are two key aspects to understand how quotas are affected:

  1. Every Codespace that has been created and not deleted can consume your included quota.
  2. Running Codespaces will use both CPU core-hours and storage, while stopped Codespaces will consume your storage quota only.


Although it can be tricky to find out how exactly your Codespaces are consuming your monthly quotas, here are four solid suggestions to reduce your spending on your personal account.


1. Delete Codespaces aggressively

Delete Codespaces instances after each use and change the default retention period to 1 day (default is 30). Go to “Default retention period” section in the Codespaces settings page to make that change.


Screenshot 2023-01-09 at 5.43.16 PM.png



2. Don't enable pre-builds

Pre-builds consume storage and it's difficult to track what pre-builds are enabled to delete them later.


Screenshot 2023-01-09 at 5.46.02 PM.png


3. Monitor usage closely

Use Billing Settings to closely monitor Codespaces consumption and make sure you aren't spending quota that you don't need.


Screenshot 2023-01-09 at 5.47.10 PM.png



4. Use granular reporting

For granular reporting and debugging consumption on CPU, Storage, and Pre-builds use the “Get usage report” button in the billing page next to the “Usage this month” section. This will create a CSV report that gets emailed to your account.


Screenshot 2023-01-09 at 5.49.46 PM.png




Want to learn more about Codespaces? Here are some useful resources:


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.