Azure Free Tier and Billing Overview

How the Azure free account's credit, spending limit and free services work, how billing is organized, and how to set budgets and alerts.

Cloud

The Azure free account is safe for exactly 30 days. During that window a spending limit stops anything from reaching your card. After it, you either upgrade to pay-as-you-go, which removes the limit, or your subscription is disabled. Most Azure billing surprises come from not knowing which side of that line you’re on.

This article explains what the free account gives you, how the credit, the spending limit and the free services interact, how Azure organizes billing around subscriptions and resource groups, and which guardrails to set before you build anything.

What the free account includes

The free account bundles three separate things, each with its own clock:

  • A $200 credit to spend on almost any Azure service, usable for the first 30 days.
  • Services free for 12 months, with monthly allowances, such as burstable virtual machines.
  • Always-free services, with monthly allowances that continue on any pay-as-you-go subscription, not just free accounts.

The credit is the only part that can pay for things outside the free list. The two free-service groups are allowances: usage up to the monthly amount costs nothing, and usage above it is paid from the credit during the first 30 days, or billed after you upgrade.

$200 credit12-month free servicesAlways-free services
Who gets itNew Azure customers, onceFree accounts, and upgraded ones for the rest of the 12 monthsFree accounts and pay-as-you-go subscriptions
What it coversMost services, or usage above free amountsA set list, each with a monthly limitA longer list, each with a monthly limit
How long30 days or until spent12 months from sign-upNo end date announced
Unused amountExpiresResets monthly, doesn’t roll overResets monthly, doesn’t roll over
Needs an upgrade to keepNoYes, after the first 30 daysNo

Sign-up asks for a phone number and a card for identity verification. Microsoft may place a small temporary authorization on the card, which is reversed. Setting Up Free Accounts on AWS, GCP, and Azure walks through sign-up step by step, along with the AWS and Google Cloud equivalents.

The free virtual machine allowance

The 12-month allowance most people use is for virtual machines: 750 hours a month of the burstable B1s, B2pts v2 (Arm-based) and B2ats v2 (AMD-based) sizes, for both Linux and Windows. A few details matter:

  • It is a pool of hours, not a free VM. 750 hours covers one VM running all month. Two running all month use the allowance twice over, so you pay for roughly one of them. Five VMs at 150 hours each also fit.
  • Only those sizes count. Azure suggests other sizes by default when you create a VM. If you pick a B2s or a D-series machine, it is billed in full.
  • The VM isn’t the whole cost. Disks, public IP addresses and outbound data are metered separately. Some of these have their own allowances on the free services list; anything beyond them is billed.
  • Burstable means CPU credits. B-series machines run at a low baseline and bank credits to burst above it. A VM that runs flat out drains its credits and slows to the baseline. That is fine for learning and small sites, not for sustained work.

Understanding Azure Virtual Machines explains the B-series and other families, and Creating Your First Azure Virtual Machine walks through creating one.

Always-free allowances worth knowing

The always-free list is long and changes, so check the free services page for current amounts. Two allowances are useful on almost any subscription:

  • Azure SQL Database free offer. Each subscription can have up to 10 free General Purpose databases, each with 100,000 vCore seconds of compute, 32 GB of data and 32 GB of backup storage a month. When you create one, you choose whether it pauses until next month when the allowance runs out or keeps running and bills the overage. Choose auto-pause on a personal account; the other option can’t be switched back.
  • Outbound data transfer. The first 100 GB a month of data sent from Azure to the internet is free for every customer, aggregated across services and regions. Inbound data is free.

The always-free list also includes small allowances for serverless and AI services. Older guides, including an earlier version of this article, refer to these AI services as Cognitive Services; Microsoft has renamed them more than once since, and the current names and free amounts are on the free services page.

In the third month of your 12-month free services, you run two B1s VMs around the clock. What do you pay for?

  • Nothing, each VM gets 750 free hours
  • Roughly one VM's worth of hours, plus anything else they use beyond the free amounts
  • Both VMs in full, because the free hours ended with the credit

Correct! The 750 hours are shared across all eligible VMs, and disks, IPs and egress are metered separately.

The spending limit and the 30-day decision

A free account subscription has a spending limit equal to the credit. While it is in place, Azure can’t charge your card. If usage reaches the limit, Azure disables the subscription: running resources are stopped and you can’t create new ones, but your data isn’t deleted straight away.

At the end of the 30 days, or as soon as the credit runs out, you have to decide. Upgrading to pay-as-you-go removes the spending limit and keeps your 12-month free services for the rest of their year. Not upgrading leaves the subscription disabled. If you never upgrade, Microsoft eventually deletes the subscription and its resources.

flowchart TD
    A["Sign up"] --> B["$200 credit, spending limit on"]
    B --> C{"Upgrade to pay-as-you-go?"}
    C -->|"Yes, any time"| P["Pay-as-you-go, no spending limit"]
    C -->|No| D{"Credit spent or 30 days passed?"}
    D -->|No| B
    D -->|Yes| E["Subscription disabled"]
    E --> F{"Upgrade later?"}
    F -->|Yes| P
    F -->|No| G["Subscription and resources deleted"]
    P --> H["12-month and always-free services continue"]
    P --> I["Usage above free amounts billed to card"]

Two details often catch people out:

  • Upgrading early doesn’t cost you credit. Whatever is left stays usable until the end of the original 30 days, then expires.
  • The spending limit doesn’t come back. Pay-as-you-go subscriptions have no spending limit, so after upgrading your protection is a budget alert and the habit of cleaning up. Set the budget before you upgrade, not after.

Upgrading doesn’t charge you on its own. Your card is billed only for usage beyond the free allowances, after the credit has expired or run out. If you only want to learn for a month, you can skip the upgrade entirely and let the subscription be disabled.

If you’re a full-time university student, Azure for Students is worth checking first: it gives $100 of credit for 12 months without a card, renewable each year while you’re eligible.

On day 20 of your free account, a large VM uses up the last of your $200 credit. You haven't upgraded. What happens?

  • Azure disables the subscription and stops its resources, without charging your card
  • Your card is charged for further usage until day 30
  • The VM keeps running until the 30 days are up

Correct! The spending limit stops the subscription when the credit runs out. Upgrading to pay-as-you-go would remove the limit and re-enable it.

How Azure billing is organized

Azure separates who pays from where resources live. Resources sit in resource groups, resource groups sit in a subscription, and the subscription is the unit that gets billed. Above it, a billing account holds the payment method and receives invoices. When you sign up as an individual, Azure creates the billing account and the first subscription for you, along with a Microsoft Entra ID tenant that holds your identities.

flowchart TD
    BA["Billing account"] --> S1["Subscription: Azure subscription 1"]
    BA --> S2["Subscription: dev and test"]
    S1 --> RG1["Resource group: rg-blog"]
    S1 --> RG2["Resource group: rg-lab-vm"]
    S2 --> RG3["Resource group: rg-sql-test"]
    RG1 --> R1["App Service, storage account"]
    RG2 --> R2["VM, disk, public IP"]
    RG3 --> R3["SQL database"]

Depending on your region and how you signed up, the billing account is either a Microsoft Online Services Program account, where each subscription has its own invoice, or a Microsoft Customer Agreement account, which adds billing profiles and invoice sections between the account and its subscriptions. For a personal account the difference is mostly where things appear in the portal.

This structure has practical effects:

  • Free allowances belong to the subscription. The free account’s credit, spending limit and free services apply to that one subscription, not to every subscription you create later.
  • Resource groups are the unit for cleanup. Deleting a resource group deletes everything in it. One resource group per experiment means you can remove the whole thing in one step.
  • Billing access and resource access are separate. Azure roles such as Owner and Contributor control resources. Billing roles on the billing account control invoices and payment methods. Azure Identity and Access Management (Microsoft Entra ID) explains how roles and scopes work.

Where charges come from

Azure meters each resource separately: compute per second or hour, storage per GB-month, transactions by count, and outbound data per GB. Prices vary by region. These patterns cause most unexpected charges:

ResourceWhat keeps billingWhat stops it
Virtual machine shut down from the OSCompute, because the VM is stopped but still allocatedStop it from the portal or CLI so it is deallocated
Deallocated virtual machineIts managed disksDelete the VM and its disks
Static public IP addressThe address, attached or notDelete it
App Service plan above the Free tierThe plan, even with no apps or trafficDelete the plan or scale it to Free
Databases outside the free offer, gateways, firewallsTime provisioned, not traffic servedDelete them
Data sent to the internetEvery GB above 100 GB a monthCache, compress or keep traffic in-region

The first row deserves emphasis. A VM shut down from inside the guest OS shows as Stopped, and you keep paying for compute. A VM stopped from the portal, CLI or auto-shutdown shows as Stopped (deallocated), and compute charges end:

az vm deallocate --resource-group rg-lab-vm --name lab-vm

Seeing what you spend

Billing tools live under Cost Management + Billing in the Azure portal. If you’re new to the portal, Navigating the Azure Portal covers how to find your way around.

ToolWhat it shows or does
Subscription overviewRemaining credit on a free account, and a grid of free-service usage and expiry dates
Cost analysisCosts over time, grouped by resource group, service, resource, region, meter or tag, with a forecast
BudgetsThresholds that send alerts when actual or forecast spend crosses them
Cost alertsBudget and anomaly alerts in one list
Advisor recommendationsIdle and oversized resources you could shut down or resize
ExportsScheduled cost data files written to a storage account
InvoicesMonthly invoices and payment history, once you are on pay-as-you-go

Cost analysis is the place to start. Grouping by resource group for the last 30 days answers “which experiment is this?”, and grouping by meter answers “what exactly am I paying for?”. Cost data isn’t real-time: charges can take several hours to a day to appear, so a report shows where you were, not where you are.

On a free account, check the free-services grid on the subscription page as well. It shows how much of each monthly allowance you’ve used, which tells you whether you’re about to start drawing on the credit.

Guardrails to set up on day one

These take a few minutes and prevent most mistakes.

Create a budget with alerts

A budget compares actual or forecast spend for a scope, usually a subscription or resource group, with an amount you set. It sends email alerts at thresholds you choose, and at subscription and resource group scope it can also trigger an Azure Monitor action group to send texts or call a webhook or Logic App.

Create one in the portal under Cost Management > Budgets: set a small monthly amount, then add alerts at 50 and 90 percent of actual cost and 100 percent of forecast cost. The forecast alert is the most useful, because it can warn you mid-month before the money is spent. The Azure CLI also has az consumption budget create, but that command group is in preview; the portal, Bicep or ARM templates are the documented routes for budgets with alert rules.

A budget doesn’t stop anything. It notifies, and your resources keep running. You can attach an action group that runs automation, for example to deallocate VMs, but because cost data lags, the automation reacts hours after the spend. On pay-as-you-go there is no switch that caps spending.

You upgraded to pay-as-you-go and set a $10 monthly budget with an alert at 100 percent. A forgotten VM pushes spend to $25. What did the budget do?

  • Stopped the VM at $10
  • Restored the free account spending limit
  • Sent an alert, while the VM kept running

Correct! Budgets only notify, unless you connect your own automation through an action group.

Turn on anomaly alerts

Cost Management runs anomaly detection on your daily costs and highlights unusual changes in cost analysis. To be told by email, create an anomaly alert for the subscription under Cost alerts. It catches what a monthly budget misses: a small but sudden jump, such as a new service you didn’t mean to start.

Tag what you create

Resource groups answer most cost questions for a personal account, but tags help once resources are shared. Tags are key-value pairs such as project=blog or env=dev, and cost analysis can group and filter by them. Tags don’t flow down from a resource group to its resources by default, so apply them to the resources themselves, or enable tag inheritance in Cost Management. Keep the scheme to two or three keys used consistently.

az group create --name rg-lab-vm --location eastus --tags project=lab env=dev

Set auto-shutdown on lab VMs

Every VM has an auto-shutdown setting that deallocates it at a set time each day. For a learning VM, a nightly shutdown means a forgotten machine costs you hours, not a month.

A cleanup habit

Most surprise charges come from resources left behind after a tutorial. A short routine after each experiment prevents them:

  1. Delete the experiment’s resource group. That removes the VM, its disks, network interface, public IP and anything else inside it.

    az group delete --name rg-lab-vm --yes
  2. List what’s left in the subscription and look for anything you don’t recognize, especially disks and public IPs that ended up outside the group.

    az resource list --output table
  3. Check cost analysis grouped by resource group and location for the last few days. Anything in a region you weren’t working in deserves a look.

How this compares with AWS and Google Cloud

All three providers combine a short-lived credit with longer-term allowances, but they differ in what happens at the end. Google Cloud’s trial gives more credit over 90 days and stops your resources rather than billing you. AWS’s free plan can’t bill you either, and its paid plan bills beyond the credits. Azure’s credit is the shortest, and keeping its 12-month services requires an upgrade that removes the spending limit. GCP Free Tier and Billing Overview and AWS Free Tier and Billing Overview cover the other two in the same detail.

If you get stuck on a billing question, Microsoft offers billing and subscription support to every Azure customer, including those without a paid support plan. Azure Support and Documentation Resources explains where to ask.

Further reading

Key takeaways

  • The free account gives a $200 credit for 30 days, 12 months of selected free services and a set of always-free services, each with its own clock.
  • A spending limit protects you during the first 30 days; reaching it disables the subscription rather than charging your card.
  • Keeping the 12-month services means upgrading to pay-as-you-go, which removes the spending limit for good, so create a budget first.
  • The free VM allowance is 750 hours a month shared across B1s, B2pts v2 and B2ats v2 VMs; disks, IPs and egress beyond their free amounts are billed separately.
  • Subscriptions are billed, resource groups are deleted: one resource group per experiment makes cleanup a single command.
  • Budgets and anomaly alerts only notify. Deallocate VMs rather than shutting them down from the OS, and set auto-shutdown on lab machines.

Part 5 of 7 · Diving into Microsoft Azure

  1. 01Introduction to Microsoft Azure
  2. 02Navigating the Azure Portal
  3. 03Azure Global Infrastructure: Regions and Availability Zones
  4. 04Mastering Microsoft Entra Identity and Access Management
  5. 05Azure Free Tier and Billing Overview
  6. 06Creating Your First Azure Virtual Machine
  7. 07Azure Support and Documentation Resources
Ready to check your understanding?Take the Fluffy Computing quiz
esc

Type to search all articles · ↑↓ to move · ↵ to open