Free and cheap Azure database options: what you can actually run on $0–5 a month

Every learner and side-project builder eventually asks the same question: can I have a real database without a real bill? The answer is yes, with conditions — and the conditions are exactly where people get burned. Here is the whole menu, the honest limits, and the traps that turn a $0 lab into a $40 surprise.

New to cloud? CAMPUX is a free, build-first course. Start here →

Yes — you can run a real database on Azure for $0: the Azure SQL Database free offer gives you a serverless database with a monthly compute cap, and the Cosmos DB free tier gives a permanent free throughput allowance — but every free tier has limits that change, so verify the current pricing page before you build on one.

Most "free Azure database" guides are a list of marketing tiers copied from Microsoft's site, and they skip the part where a learner's subscription bills $38 in a month they thought was free. I have watched that happen to students more than once, and the cause is almost never the database they chose — it is the behavior around it: a health check that never lets a serverless database pause, provisioned throughput left running over a weekend, backup storage growing while nobody looks. So this is two articles in one: what to pick, and how not to get bitten.

One hedge up front that applies to every number below: free-tier terms change. Microsoft has adjusted caps, regions, and eligibility on these offers before and will again. Everything here is accurate to the best of my knowledge as of September 2026; treat the specific figures as directions, not contracts, and confirm on the official pages I link before you depend on any of them.

The menu, on one table

The table hides the interesting parts, so here is each in detail.

Azure SQL Database: the always-free offer

This is the headline option and the one most learners should start with. As of 2026, Azure SQL Database has an always-free offer: one serverless database per subscription, with a monthly grant of compute (measured in vCore-seconds) and a chunk of free storage. It is a different thing from the 12-month free services you get with a new Azure account — this one does not expire after a year. The grant refreshes every month.

The mechanics matter. The database runs on the serverless tier, which means it auto-pauses when nothing is talking to it and wakes up on the next connection. While paused, it burns none of your monthly compute grant. For a learner who opens SQL a few evenings a week, the grant is generally plenty — you would have to work hard to exhaust it with hand-typed queries. Where it gets used up fast is anything that keeps the database awake continuously, which we will get to in the traps section.

When you do hit the monthly cap, one of two things happens, and you choose which at setup: either the database pauses until next month's grant arrives (truly free, but your app goes dark), or it keeps running and starts billing at normal serverless rates. If your goal is a guaranteed $0, pick the pause behavior and treat the darkness as a feature. Check the exact grant size and terms on the official free-offer page — the numbers have shifted before and I would not print a figure here and promise it survives the year.

If you are working through the AZ-104 or DP-900 material, this is also the cheapest possible way to do the database portions of the databases class against a live resource instead of screenshots.

Cosmos DB: the free tier that is genuinely free, once

Cosmos DB is Microsoft's globally-distributed NoSQL database, and its free tier is unusually generous for what the product normally costs. As of 2026 the shape of it is: the first slice of throughput (historically 1,000 RU/s) and a chunk of storage free, on one Cosmos DB account per subscription, permanently. You tick a box at account creation — it cannot be added later to an existing account — and that account carries the discount for life.

Two honest caveats. First, "one per subscription" means exactly that — create the free-tier account deliberately and keep it, because you cannot have two at once. Second, the free allowance applies to provisioned throughput, and anything you provision above the free slice bills normally, per hour, whether you use it or not. That word provisioned is the single most expensive word in this article, and it reappears in the traps section below. Verify the current allowance on the Cosmos DB free-tier docs before you plan around it.

When would a learner pick Cosmos over free Azure SQL? When the thing you want to learn is NoSQL itself — partition keys, RU-based pricing, the tradeoffs that make document databases different. If you are unsure which side of that line your project sits on, I wrote up the decision in Azure SQL vs Cosmos DB; the short version is that boring relational data wants the boring relational database.

PostgreSQL Flexible Server: cheap, honestly not free

There is no always-free tier for Azure Database for PostgreSQL that I would build a plan around (new-account 12-month promotional credits exist and expire; I do not count those). What you get instead is a genuinely cheap floor: the smallest burstable SKU — a fraction of a vCPU that saves up credit while idle and spends it in bursts — has generally run somewhere in the low tens of dollars a month for compute, plus a few dollars for storage, as of 2026. Region and reserved pricing shift these numbers, so read the pricing page for your region rather than trusting my memory.

The redeeming feature for a learner budget: Flexible Server can be stopped. Stopped means compute billing pauses — but be careful with the fine print, because two things still apply. Storage (and backup storage) keeps billing while the server is stopped, and a stopped server does not stay stopped forever: Azure automatically restarts it after a set number of days (it has been seven in my experience — again, verify current behavior in the Flexible Server docs). If you stop a server before a two-week vacation and assume $0, you will come home to a running server and a compute bill. Stop is a pause button with a timer on it, not an off switch.

Why pay at all when free Azure SQL exists? Because PostgreSQL is what an enormous share of real application stacks run on, and "I deployed an app against a managed Postgres, locked down its firewall, and rotated its credentials" is a stronger portfolio sentence for many jobs than another T-SQL exercise. It is the option you graduate to, not the one you start on.

Table Storage: pennies, if you can live without SQL

The quiet budget option nobody markets. Azure Table Storage is the key-value corner of a plain storage account: no server, no vCores, nothing to pause or stop. You pay for what you store — pennies per gigabyte per month — plus per-transaction amounts so small that a learner project rounds to zero. A side project storing a few megabytes of rows will show up on your bill as cents, as of 2026; the Table Storage pricing page has the current per-GB figures.

The tradeoff is total: no SQL, no joins, no foreign keys, queries limited to partition key and row key unless you enjoy full scans. It suits logs, lookup tables, IoT-ish streams, and app state that is naturally keyed. It does not suit "I am learning databases." If you want the fuller picture of where tables sit next to blobs, files, and queues, that is covered in the storage services guide.

The SQLite paragraph most cloud blogs will not write

Here is a thing a cloud training site is not supposed to say: for a lot of learner projects, the right database is not in the cloud at all. If your portfolio app runs on one small VM or app service and the database exists only to make the app function, SQLite — a single file, embedded in your process, zero configuration, zero cost — is not a toy. It is one of the most deployed pieces of software on Earth, and for a single-box app it beats a remote database because there is no network round-trip at all.

Use a managed cloud database when the database is part of what you are demonstrating: connection strings and secrets handling, firewall rules, backups and restores, scaling tiers, the operational story an employer actually asks about. Use SQLite when the database is plumbing and the app is the point. Plenty of my students do both — build fast on SQLite, then swap in a managed database at the end specifically to practice the wiring. That order costs almost nothing and teaches the same lessons.

The database you chose is almost never what bills you. The thing you forgot about it is.

The bill-shock traps — the section that saves you $40

Every one of these has hit real learners. None are on the pricing page in bold.

• Provisioned throughput you forgot. Cosmos DB provisioned RU/s bills per hour whether a single request arrives or not. Provision 5,000 RU/s for a load test on Friday, forget it, and the weekend bills it faithfully. Serverless-mode Cosmos or autoscale caps this; the real fix is the delete discipline below.
• The serverless database that never pauses. Azure SQL serverless only saves money when it actually pauses — and it will not pause while anything connects. An uptime monitor, a keep-alive in your web app, a dashboard tile that polls, even you leaving a query window open with the wrong settings: any of these turns "pauses when idle" into "runs continuously" and quietly drains the free grant, after which it either goes dark or starts billing depending on your setup choice. If your free database keeps hitting its cap by day ten, something is pinging it.
• The stopped server that woke up. As above: Flexible Server restarts itself after the stop period expires. Stopping is for days, not months.
• Backup storage growing quietly. Managed databases take backups automatically, and backup storage beyond the included amount bills separately. On a tiny learner database this is usually cents — but long retention settings on a database you churn a lot of data through can build a line item you never asked for. Skim your backup retention settings once; default them down for lab work.
• Egress. Data leaving Azure to the internet bills per GB after a free monthly allowance. A learner querying a small database will never notice it; an app serving big public responses, or repeated full exports to your laptop, eventually will.

The two habits that make all of this a non-issue

First: one resource group per experiment, and delete the group when the session ends. Not the database — the group. Deleting the resource group takes the database, its backups, its monitoring, and everything else you forgot down with it, and a deleted resource bills nothing, ever. It is the only cost control that requires no ongoing attention, and rebuilding from a script the next evening is itself the skill employers pay for.

Second: budget alerts before your first resource, not after your first bill. An Azure budget with alerts at a few dollars costs nothing and emails you before a mistake compounds. We have a free hands-on lab that sets up exactly this — the cost guardrails lab — and I would honestly do it before any database on this page. The wider discipline is covered in budgets and alerts if you want the reasoning too.

Which option for which project

Cert-lab work (AZ-104, DP-900 and friends)

The Azure SQL free offer, plus the delete-the-resource-group habit for everything else the exam makes you touch. Your labs are short-lived by nature; nothing should survive the evening. Pair it with the free exam practice bank and the whole study loop costs $0.

A portfolio web app that stays up

Start on SQLite if the app is the point. When you want the managed-database story on your résumé, the free Azure SQL offer with pause behavior works if occasional cold-starts are acceptable, Cosmos free tier works if it is a NoSQL-shaped app that must stay warm, and a burstable PostgreSQL server is the paid-but-cheap option when you want the exact stack a job posting names. Budget alert first, always.

Learning SQL itself

You barely need the cloud: SQLite or a local PostgreSQL in a container costs nothing and removes every trap above. Move to the free Azure SQL offer when you want the Azure-specific layer — firewalls, connection policies, the portal — on top of the language.

Questions people also ask

Is there a truly free database on Azure?

Yes, two, as of 2026. The Azure SQL Database free offer gives you one serverless database per subscription with a monthly compute cap and free storage, and it does not expire after twelve months. The Cosmos DB free tier gives one account per subscription a permanent free allowance of throughput and storage. Both are genuinely $0 if you stay inside the limits, and both have limits that Microsoft can change — read the current terms on the official docs before you build anything you care about.

How much does the cheapest Azure database cost per month?

If free tiers do not fit, the cheapest real database server is usually PostgreSQL Flexible Server on the smallest burstable SKU, which has generally run somewhere in the low tens of dollars per month for compute plus a few dollars for storage, as of 2026 — check the pricing page for your region because these numbers move. Below that, Table Storage costs pennies per gigabyte but is not a relational database. The honest cheapest option for a tiny project is often SQLite, which costs nothing because it is a file.

Does the Azure SQL Database free offer expire after 12 months?

No. The free offer on Azure SQL Database is a different thing from the 12-month free services you get with a new Azure account. It is an always-free arrangement: one serverless database per subscription with a monthly grant of vCore-seconds and free storage, refreshed every month for the life of the subscription, as of 2026. When you use up the month's grant, the database either pauses until next month or starts billing, depending on which behavior you picked when you set it up. Terms can change, so confirm on the official free-offer page.

Can I stop an Azure database to avoid charges?

Partly. PostgreSQL and MySQL Flexible Servers can be stopped, which pauses compute billing, but storage and backup storage keep billing while stopped, and a stopped server restarts itself automatically after a set number of days — so stopping is a pause button, not an off switch. Azure SQL serverless auto-pauses on its own when idle, unless something keeps connecting to it. The only way to guarantee $0 is to delete the resource, ideally by deleting the whole resource group when a lab session ends.

Should I use SQLite instead of an Azure database for my portfolio project?

If your app runs on one small server and the database exists to make the app work, yes — SQLite is a serious production-grade engine, it costs nothing, and it removes a whole class of connection, firewall, and billing problems. Use a cloud database when the database itself is the thing you are demonstrating: managed backups, firewall rules, connection strings from a deployed app, scaling settings. For a cloud engineering portfolio that is often exactly the point, so many learners run both — SQLite to build fast, then a managed database to show they can wire one up properly.