How to practise Azure without a surprise bill
Check your subscription, read every meter, and remove finished resources. A budget sends a warning; it does not switch the lab off.
A low-cost lab starts with a resource inventory. Before deploying, write down the VM, its disks, public IP, storage account, monitoring workspace, and any gateway the exercise creates. Give every resource an owner and a cleanup time. The bill follows the resources, including the ones a diagram leaves out.
Use a dedicated lab resource group. Check the offer attached to your subscription and the estimated cost of the exact configuration. Decide what you can afford if an alert arrives late. If the exercise is outside that amount, use a reading exercise or local simulation until you have a workable budget.
A credit, a free allowance, and a budget do different jobs
| Control | Purpose | What to check |
|---|---|---|
| Trial credit | A temporary balance for eligible usage | Expiry, remaining credit, and excluded purchases |
| Free service allowance | Included usage for a specific offer and configuration | SKU, region, billing period, and associated resources |
| Spending limit | A credit-linked restriction on eligible subscriptions | Whether your subscription supports it |
| Budget | Notifications about reported costs | Recipients, thresholds, scope, and reporting delay |
Microsoft's free account does not automatically become a paid account when its credit ends. Continued paid use requires an upgrade. Once upgraded, usage outside remaining free allowances can bill. Review that choice in the billing page before continuing an old lab.
Five checks before you build
- Confirm the subscription. Check the subscription ID, offer, remaining credit, and end date. A second subscription in the same directory can have different billing terms. Keep the lab separate from shared production resources.
- Check spending-limit eligibility. A qualifying credit-based subscription normally has a limit equal to its credit. You cannot set a custom amount. Pay-as-you-go and commitment subscriptions do not support it. Some separately billed Marketplace purchases can still charge outside the limit.
- Configure a budget. Choose a small amount you can afford, actual-cost thresholds, and an email you check. Costs typically arrive 8–24 hours later and budget evaluation runs daily. The alert does not stop consumption. Review Cost Analysis yourself during a lab.
- Record the shutdown and deletion plan. A stopped, allocated VM still charges for compute. Deallocation stops compute charges, while disks and other resources can keep billing. Identify which data to export before deleting anything.
- Set a finish time. Keep one exercise in its own resource group where practical. Review its contents before deleting it, then check for shared or separately created resources left elsewhere. Do not delete a group containing work you need.
Free VM offers depend on the exact configuration
A VM offer is an allowance, not permission to run any VM without charge. Confirm the eligible sizes and operating systems on the current free-services page. Check disk type, disk count, region, running hours, and the public IP separately. A resize can change the meter even when the VM name stays the same.
For a short exercise, record the initial configuration and the time it ran. For a machine you retain, add a reminder before the offer expires. Do not use a permanent server as your first cost experiment. A repeatable deployment you can remove is easier to reason about than an abandoned VM.
Monitoring and networking belong on the inventory
Log Analytics can charge for ingestion and retention. Its daily cap is a volume safeguard, not an exact financial ceiling: ingestion can overshoot, and the excess is billable. Reaching the cap also interrupts collection. Reduce unnecessary diagnostic categories and use an ingestion alert so you know when visibility is being lost.
- Disks and snapshots: check resources retained after the VM is removed.
- Networking: review public IPs, NAT Gateway, Bastion, gateways, and data transfer rather than assuming a quiet VM has no networking bill.
- Application dependencies: a function can use storage and monitoring with separate meters. A free execution grant does not cover the whole application.
- Purchased software: read any Marketplace purchase terms before accepting them.
Three practice projects with a clear finish line
Start with Class 32 and compare these exercise shapes. Each teaches something useful; each still needs its own estimate.
- Static page: deploy a small HTML file, inspect the storage and hosting meters, save the deployment instructions, and remove the resource when finished.
- Small HTTP function: send a bounded set of requests, inspect its associated storage and logs, then remove the app and dependencies.
- VM shutdown drill: capture the difference between stopped and deallocated states, list the remaining disks and IPs, then export your notes and remove the dedicated group.
Keep a deployment file, a resource inventory, and a cleanup checklist in the repository. Record actual observed costs after reporting catches up. Label a calculator estimate as an estimate; do not describe it as a measured bill.
If a charge appears
Use Cost Analysis to identify the subscription, resource, date, and meter. Stop the activity that creates more usage and preserve anything you need before deleting resources. Charges already incurred remain due. For a billing discrepancy, open a support request with the relevant IDs and dates; a refund is not guaranteed.
Common questions
Does a budget stop my Azure resources?
No. It warns about reported costs. Build cleanup into the exercise and allow for reporting delay.
Can I set a spending limit on pay-as-you-go?
No. Use an affordable configuration, budgets, resource-specific controls, and timely cleanup.
Is a deallocated VM completely free?
Compute stops charging, but retained disks and other resources can still cost money. Review the full resource inventory.
Sources and review
Reviewed 1 October 2026. Billing behavior was checked against Microsoft documentation. This is a cost-control checklist, not a promise of a zero bill; no paid lab was executed for this review.
- Azure spending limits
- Create and manage budgets
- Avoid charges with the free account
- Log Analytics daily cap
- Current Azure free-services offers
Every class is open to read. A free account saves your progress. Azure resources used for labs may incur charges.