The $0 cloud lab: how to practise Azure without a surprise bill
The thing that stops most beginners is not the difficulty — it is the fear of waking up to a bill. Here are the exact switches that turn Azure into a free lab, the always-free services you can build real projects on, and the one hidden meter that quietly catches people out.
New to cloud? CAMPUX is a free, build-first course. Start here →
Ask why someone who wants to learn cloud has not opened the Azure portal yet, and the honest answer is rarely "it looks hard." It is "I heard someone got charged $400." That fear is reasonable — Azure is a metered utility, and left unattended it will bill you. But it is also completely manageable. With five switches set before you build anything, you can run a personal lab for months and pay nothing, or close to it. This is the guardrail checklist, the always-free list, and the honest warning about the meters that do not announce themselves.
You can practise Azure for £0 by using the free account's one-time credit, turning on the spending limit, setting a $1 budget with alerts at 50, 80 and 100 percent, deallocating VMs when you stop, and sticking to always-free services. The one that catches people is Log Analytics ingestion — cap it.
The three layers of "free" in Azure
"Free" means three different things, and mixing them up is where the confusion starts.
| Layer | What it is | The catch |
|---|---|---|
| Starter credit | A one-time credit for your first 30 days on a new free account | Expires — after that, paid services bill normally |
| 12-month free | Popular services free for your first year (some VM hours, storage, etc.) | Only for 12 months, and only up to monthly limits |
| Always free | Services that stay free forever within a monthly allowance | The allowance is real — go past it and you pay |
Figures and inclusions change — confirm the current free-account terms on Microsoft Learn before you rely on them (checked August 2026). The always-free layer is the one that matters most for a long-term lab, because it does not expire. The other two are a head start, not a foundation.
The five guardrails — do these before you build
- Create the free account and note when the credit expires. The starter credit is a cushion, not a plan — treat it as expiring and build as if you are already on the always-free layer.
- Turn on the spending limit. On subscription types that support it, the spending limit suspends paid services the moment your credit runs out, so you cannot overspend the credit. Keep it enabled.
- Set a $1 budget with alerts. In Cost Management, create a budget at a deliberately tiny figure and add alerts at 50, 80 and 100 percent. The point is not the dollar — it is that you get an email the instant anything starts to cost, while it is still pennies. This is drilled in Class 32 — Cost Management & FinOps.
- Deallocate VMs, do not just stop them. A VM that is "stopped" in the portal can still bill for its allocated compute; only a deallocated VM stops the meter (the disk still costs a little). When you finish for the day, deallocate.
- Keep each project in its own resource group. A resource group you can delete in one click is your undo button. Build a project inside one, and when you are done, delete the whole group and everything in it goes with it — no orphaned resource billing quietly for months.
The hidden meters that bill quietly
The "I'm on the free account, why am I charged?" surprise almost always comes from a service that bills outside the free limits without making a fuss. The usual suspects:
- Log Analytics ingestion. The big one. A monitoring workspace ingesting logs past its free amount is the single most common surprise charge. Cap the ingestion or scope what you send it.
- Idle public IP addresses. A reserved static public IP that is not attached to anything still bills. Release IPs you are not using.
- Stopped-but-not-deallocated VMs and their disks. Covered above — the disk keeps costing even when the VM is off.
- Outbound bandwidth. Small for a lab, but it exists. Deleting finished projects keeps it near zero.
None of these announce themselves. The budget alert from guardrail three is what turns them from a month-end shock into a same-day email.
Azure will not surprise you if you have already told it where the ceiling is.
Three $0 portfolio projects you can build today
Guardrails set, here is what to actually build — each fits inside the always-free and free-account limits, and each is a real thing you can show:
- A static website on Blob Storage. Host an HTML page as a static site — pennies at most. See the cheapest way to host a static site on Azure.
- A serverless HTTP API on Azure Functions. The consumption plan has a large free monthly grant — plenty for a portfolio API.
- A nightly VM auto-shutdown. A tiny automation that saves money is itself a cost-awareness story worth telling in an interview.
Want the full set with the exact resume bullet each one earns? That is three Azure projects that prove you have experience, and the flagship build that ties them together is the Cloud Resume Challenge on Azure.
What to do if you do get charged
Say a meter slips past you anyway. Do not panic — it is almost always small and recoverable. Open Cost Analysis and sort by resource to find exactly what billed. Delete or deallocate the culprit (usually the whole resource group). If it is a genuine first-time mistake on a free account, you can open a support request and ask about a credit — Microsoft is often reasonable with beginners who acted quickly. Then re-check your budget alert is set. The goal is not perfection; it is that nothing bills for long enough to hurt.
Questions people also ask
Does Azure charge you automatically after the free tier ends?
It can, and this is what catches people out. Unlike some clouds, Azure has no automatic hard cap by default — once you pass a free limit or the credit expires, paid charges begin. The fix is to turn on the spending limit where available and set a budget alert. Do that before you build and the automatic bill stops being a surprise.
How do I set a spending limit in Azure?
Free and pay-as-you-go accounts often have a spending limit you can keep enabled in the billing settings, which suspends paid services when your credit runs out. Because it isn't available on every subscription type, also create a budget in Cost Management — set it to a low figure like $1 and add alerts at 50, 80 and 100 percent so you hear about spend early.
What Azure services are always free?
Several services stay free forever within monthly limits, regardless of your credit. Common ones for learners include Azure Functions (a generous monthly execution allowance), a small App Service tier, and Cosmos DB's free allowance. These are enough to host a static site, run a serverless API and store data for a portfolio project without paying. Always check the current limits, since they change.
Why did I get an Azure bill when I'm on the free account?
Usually because a service quietly billed outside the always-free limits. The classic culprits are a Log Analytics workspace ingesting logs past the free amount, an idle public IP, a stopped-but-not-deallocated VM still holding a disk, or bandwidth. None of them are obvious. Check Cost Analysis to find the resource, then delete or deallocate it — and cap Log Analytics ingestion.
Can I build a portfolio project on Azure for free?
Yes. A static website on Blob Storage, a serverless HTTP API on Functions, and a scheduled VM auto-shutdown can all be built inside the always-free and free-account limits if you follow the guardrails. The trick is deallocating anything you're not using and keeping each project in its own resource group so you can delete it cleanly when you're done.