An Azure service that is used to provision Windows and Linux virtual machines.
B2ats v2 is one of the VM sizes that’s eligible as a free service for new Azure free accounts, up to 750 hours per month. However, “free services eligible” doesn’t mean it’s always free in every subscription or scenario:
- The free 750 hours apply only:
- In an Azure free account (or a subscription upgraded from that free account), and
- While the 12‑month free period is still active, and
- As long as total usage of eligible VMs (B1S, B2pts v2, B2ats v2) stays within the free limits.
- Quotas and “free” are separate:
- vCPU/VM-family quotas only control how much capacity can be deployed.
- Increasing quotas (for example, via a support request) doesn’t grant or extend free benefits; it only allows more cores/VMs to be created.
- Why the dashboard shows “not in use” for B2ats v2:
- The “free services” grid in the subscription view tracks usage of services that are part of the Azure free account benefits.
- If the subscription isn’t an Azure free account (or the 12‑month free period has ended), that grid can show “not in use” or no usage even though a VM is running, because the VM is being billed at pay‑as‑you‑go rates instead of consuming free-tier benefits.
- It can also show “not in use” if the VM is created outside the “Free services” flow and the configuration doesn’t match the exact free tier being tracked.
- How to ensure a VM is actually free:
- Confirm the subscription is an Azure free account or an upgraded free account still within the 12‑month free period.
- Create the VM from the Free services page in the Azure portal and explicitly select the free tier/size.
- Keep total usage of eligible VMs within the 750 hours/month limit.
If any of these conditions aren’t met, the B2ats v2 VM will be billed at normal pay‑as‑you‑go rates even though it is “free services eligible” in principle.
References: