How Azure billing and licensing work

If you have spent your career buying software by the seat, Azure will feel unfamiliar. There is no per-user number to multiply. The invoice is different every month, it arrives after the money has already been spent, and the line items are written for engineers rather than for the person signing the check.

The underlying model is simpler than the invoice makes it look. Here is how Azure charges you, what levers bring the number down, and what to insist on so the bill stays predictable.

Azure is a utility bill, not a seat count

Microsoft 365 is licensing. You buy a subscription for each person, the price is known in advance, and the bill is stable until your headcount changes.

Azure is consumption. You are renting infrastructure by the second, the gigabyte, and the transaction. Nothing is licensed to a person. The bill reflects what was running, how big it was, and how long it ran. If someone builds a server on Tuesday and forgets it, that server is on the invoice at the end of the month.

For budgeting, three consequences follow:

• Your budget is a forecast, not a purchase order. You are estimating a variable cost, the way you would estimate electricity or freight.
• Cost is an engineering decision. The size and shape of what gets built determines what you pay. That decision usually happens weeks before finance sees the result.
• Small changes compound. A server that is one size too large is not a rounding error. It is a fixed monthly overcharge that repeats until somebody notices.

The Azure pricing page lists current rates for every service, and the Azure pricing calculator turns a proposed design into an estimate. Both are public, and both are worth asking to see before a project starts.

What a meter is

Every Azure service exposes one or more meters. A meter measures one billable thing, at one rate, in one region, and your invoice is the sum of every meter reading for the month. Most business bills are dominated by three families.

Compute is time. A virtual machine is billed for every hour or fraction of an hour it is running, at a rate set by its size and region. Stopping a machine from inside the operating system is not enough. It has to be stopped and deallocated in Azure to stop the compute meter.

Storage is space, plus activity. You pay for the capacity you have provisioned, for the performance tier you chose, and often for the number of read and write operations. A disk keeps billing whether or not the machine attached to it is running, and whether or not it is attached to anything at all.

Network is movement, and it is asymmetric. Data coming into Azure is generally not billed. Data leaving Azure for the internet, or crossing between Azure regions, is billed by the gigabyte. Current rates and the included monthly allowance are on the bandwidth pricing page.

That asymmetry catches people. Moving 10 terabytes into Azure is free. Moving the same 10 terabytes back out, or copying it to another region every night, is not. If a design moves large volumes of data out of Azure on a schedule, that belongs in the estimate from day one.

Three ways to pay for the same virtual machine

Once a workload is steady, you are no longer buying flexibility. You are buying capacity you already know you need, and Microsoft will discount it in exchange for a commitment.

A reservation locks in a discount for a particular resource in a particular place. Because it is specific, it carries the deeper discount. Microsoft allows you to exchange a reservation for another of the same type, and to refund reservations up to a published limit within a rolling 12-month window. A reservation on a Windows or SQL Server machine covers the compute only; the software licensing sits outside it.

A savings plan works differently. You commit to spending a set amount per hour on eligible compute, and the discount is applied automatically each hour to whatever eligible resources are running, starting with the ones that benefit most. You can move workloads between sizes and regions without losing the benefit. Unused commitment in a given hour expires and does not roll over, and savings plan purchases cannot be canceled or refunded. The compute savings plan comes in one-year and three-year terms; the database savings plan is one-year only.

The trade-off is straightforward. Reservations pay better and bind tighter. Savings plans pay less and bend more. Most organizations end up with reservations covering the part of the estate that has not moved in two years, and a savings plan covering the part that keeps changing.

Where to start: the one-year term. Unless a workload is genuinely short-lived, the one-year commitment is the default worth taking. It captures most of the available discount, and a year is a horizon a business can forecast, where three years usually is not. One difference from seat licensing is worth knowing here: with Azure reservations, paying up front and paying monthly come to the same total, so the payment schedule is a cash-flow preference rather than a discount. Pay up front if you would rather have one invoice and be done with it.

Savings plans are available to organizations on an Enterprise Agreement, a Microsoft Customer Agreement, or a Microsoft Partner Agreement, which is the agreement type behind partner-billed Azure. Either way, commitments need a review schedule, because a reservation that no longer matches what you run is a bill for nothing.

Azure Hybrid Benefit

This is the largest routinely missed saving in Azure, and it is a paperwork exercise rather than an engineering one.

If you already own core-based Windows Server or SQL Server licenses with active Software Assurance or subscription licenses, Azure Hybrid Benefit lets you apply those licenses to matching workloads in Azure instead of paying for the software again through the Azure meter. You pay the base compute rate rather than the rate that includes the license.

Two things make this worth checking specifically:

• It is not automatic. It is a setting, and a machine deployed without it will quietly bill at the higher rate for as long as it runs.
• It stacks with reservations and savings plans, which cover compute but not software licensing. Applying both is where the meaningful reductions come from.

Azure Hybrid Benefit for SQL Server can also be managed centrally, assigning licenses at the subscription or billing-account level rather than machine by machine. If you have an on-premises estate with Software Assurance and a growing Azure footprint, this is the first question to ask, not the last.

Dev/test pricing and spot capacity

Two more discounts apply to specific circumstances.

Azure Dev/Test pricing offers reduced rates on subscriptions used only for development and testing, subject to Microsoft's use terms. The catch is the terms: these subscriptions are not for production workloads. Used correctly, it takes a real bite out of the cost of environments that exist only so your team can rehearse changes safely.

Spot virtual machines rent Azure's unused capacity at variable, reduced rates. The condition is that Azure can take the capacity back with about 30 seconds of notice, and there is no service level agreement. That makes spot capacity suitable for batch processing, overnight jobs, and test environments, and unsuitable for anything a person is waiting on.

The free tier and the trial credit

New Azure accounts come with a starting credit and a set of free service allowances. The Microsoft documentation on avoiding unexpected charges is blunt about what expires:

• The credit is usable for the first 30 days. When it runs out or expires, the subscription and its services are disabled until you upgrade.
• The free service allowances last 12 months after you upgrade, in limited monthly quantities. Unused quantity does not roll into the next month.
• A smaller set of services is always free within published limits.
• When the 12 months end, everything still running switches to standard rates. Microsoft sends a notice, but the resources do not turn themselves off.

A proof of concept built on a free account and left in place is a common source of a first real invoice that nobody expected.

Buying direct, through a partner, or under an agreement

The same Azure services can be purchased through different channels, and the channel determines who invoices you, who you call, and what management sits around the account. Microsoft's billing account documentation lists all the account types. Most businesses encounter three.

Direct from Microsoft. You sign up on the Azure website, pay by card or invoice, and hold the commercial relationship with Microsoft. You get self-service tooling and Microsoft's own support channels, and nobody is watching the bill on your behalf.

Through a Cloud Solution Provider partner. A Microsoft partner resells Azure to you under a Microsoft Partner Agreement. You get one invoice from the partner, usually alongside your other Microsoft subscriptions, and the partner is your first line of support and can hold delegated access to help directly. Cost governance, tagging discipline, and reservation reviews are typically part of the arrangement rather than something you build yourself. Some Azure programs work slightly differently in this channel, so it is fair to ask how spot capacity, reservations, and dev/test subscriptions are handled under a given partner's agreement.

Under an Enterprise Agreement. A negotiated volume agreement with Microsoft, generally suited to larger organizations. It brings enrollment-level administration, price sheets, and its own set of roles and reporting.

The question worth asking is operational rather than commercial: when a virtual machine will not start on a Sunday morning, who picks up, and does that person already know how your environment is built?

Support is a separate purchase

Azure includes billing and subscription support at no cost. Technical support with committed response times is a separate subscription, and the plans are published on the Azure support plans page. The paid tiers, Developer, Standard, and Professional Direct, differ mainly in how fast Microsoft commits to respond.

Two things about support plans surprise people. It is a recurring charge on the Azure invoice, and it renews automatically until you turn renewal off in Cost Management. And buying it is not the same as having someone who knows your environment: Microsoft's support engineers work on the platform, not on your applications. Most organizations running production workloads end up with both a support plan and a partner relationship, and use each for what it is good at.

The cost controls to insist on

None of these are difficult. All of them are easier to set up on day one than to retrofit after a bad month. Microsoft's cost planning guidance covers the mechanics.

• Budgets and alerts. Set a monthly budget on every subscription and configure alerts so that a spending anomaly reaches a human within days, not at invoice time.
• Tagging. Tags label each resource with an owner, a project, and a cost center. Without them, cost analysis can tell you that spending rose and cannot tell you whose spending rose. Tag inheritance makes it harder for untagged resources to slip through.
• Right-sizing reviews. Azure Advisor flags resources with low utilization. A quarterly pass through those recommendations is usually the highest-return hour anyone spends on the bill.
• Auto-shutdown on non-production machines. Development and test machines rarely need to run overnight or at weekends. Scheduled shutdown removes most of their running hours and needs no ongoing effort.
• Reservation and savings plan review. At least twice a year, check that commitments still match reality, and that anything eligible for Azure Hybrid Benefit has it applied.

Where the money leaks

The overspend patterns are consistent.

• Machines left running. A test environment built for a project that finished in March, still billing in November.
• Oversized machines. Sized for a worst case that never arrived, or sized by copying the specification of the physical server it replaced.
• Orphaned disks and public addresses. Delete a virtual machine and its disks can remain, billing for capacity attached to nothing. Reserved public addresses behave similarly.
• Premium storage where standard would do. High-performance storage on a file share that gets touched twice a week.
• Unnecessary data movement. Backups, log shipping, or reporting extracts crossing regions or leaving Azure on a schedule that nobody chose deliberately.

Every one of these is visible in cost analysis and in Advisor. They persist because nobody has been made responsible for looking.

Licensing that still applies inside Azure

Consumption billing does not mean licensing disappears. Three categories remain.

Windows Server. A Windows virtual machine bills at a higher compute rate than the equivalent Linux machine, because the Windows license is included in the meter. Azure Hybrid Benefit is how you avoid paying twice if you already own the license.

SQL Server. The same pattern, with more variation across the managed database services. Reservations cover the compute, the software license is handled separately, and Azure Hybrid Benefit applies.

Third-party software. Software bought through the Azure Marketplace is billed on your Azure invoice but sold by the software publisher, not Microsoft. Those charges appear as separate line items and are generally not covered by reservations or savings plans. When a bill jumps and the compute has not changed, check these early.

Hosted desktops: two shapes, two licensing models

If the reason you are looking at Azure is to give people a desktop they can reach from anywhere, there are two products, and they are licensed on opposite principles.

Azure Virtual Desktop is consumption. You build and pay for the underlying virtual machines, storage, and networking exactly as you would for any other Azure workload, and the service that brokers connections is included. On top of that, every user needs a qualifying Windows license. Microsoft 365 E3, E5, F3, and Business Premium all qualify, as do Windows Enterprise E3 and E5 and Windows VDA per user. If your session hosts run Windows Server instead of a Windows client operating system, the entitlement comes from Remote Desktop Services client access licenses with Software Assurance, or from Remote Desktop Services user subscription licenses. There is also a per-user access pricing model, but it exists only for serving external customers commercially, not for your own staff or contractors.

Windows 365 is a subscription. Each person gets a Cloud PC of a fixed size for a fixed monthly price per user, which is far easier to budget. The requirements go beyond the Windows 365 license itself: users also need Windows Enterprise E3 or equivalent, Microsoft Intune, and Microsoft Entra ID P1. Those are typically already present if you hold Microsoft 365 E3 or above, and they are an additional purchase if you do not.

The choice is mostly about variability. Azure Virtual Desktop suits uneven usage, because machines can be scaled and shut down. Windows 365 suits organizations that want a predictable per-person number and less infrastructure to run.

Gotchas that catch non-technical buyers

• Stopping a machine inside Windows does not stop the bill. It has to be deallocated in Azure. Half-stopped machines bill at full rate.
• Deleting a machine does not always delete its disks. Storage keeps billing until someone removes it explicitly.
• Azure Hybrid Benefit is a checkbox that nobody checks. It is applied per resource, and a machine built without it never applies it retroactively.
• Reservations do not cover software. A reservation on a Windows or SQL Server machine discounts the compute only.
• Savings plans cannot be undone. Reservations can be exchanged or refunded within Microsoft's published limits. Savings plans cannot be canceled or refunded, so the commitment amount deserves real scrutiny.
• The free tier ends on a date, not on a warning. Free allowances expire 12 months after upgrade, and everything still running moves to standard rates.
• Support plans renew automatically. They are a recurring charge on the Azure invoice, and turning renewal off is a deliberate action in Cost Management.
• Nobody owns the bill by default. Azure will happily run whatever it is asked to run. Budgets, tags, and a named owner are the difference between a variable cost and an unexplained one.

Where to start

If the invoice has been climbing, put three consecutive months of detailed usage next to the resources that produced it. That comparison usually answers the question in an afternoon: what is running, what is oversized, what is orphaned, and what is eligible for a discount nobody applied.

If you are planning a move to Azure and want a number for the budget, do the reverse. Start from the workloads, size them honestly, apply the licenses you already own, and see what the estimate says before anything is built.

Wired CIO works as a fully managed or co-managed IT partner in both situations. If you would like a second read on an Azure estimate, or on an invoice that stopped making sense, bring us the numbers and we will walk through them with you.