How Much Does Azure Cost?

Updated on October 12, 2026 | Written by Alec Pow
This article was researched using 13 sources. See our methodology and corrections policy.

Microsoft Azure can cost $0 per month for eligible free-tier usage, while a small hosted application may incur tens or hundreds of dollars monthly. A larger production environment can cost thousands of dollars per month. There is no fixed Azure subscription price covering all services, and the frequently quoted $200 to $500 monthly small-business budget is not a verified national average.

Azure bills for the resources an organization deploys and consumes. Virtual machines, managed databases, storage, outbound traffic, and additional security or networking services have separate pricing rules. Region, resource size, uptime, redundancy, and purchasing commitments can substantially change the final invoice. A reliable estimate begins with a defined workload rather than a generic business-size label.

Article Highlights

• New qualifying Azure customers can receive $200 (at $30 per hour, earning that amount would take about 6.7 hours of work, before taxes) in trial credit for 30 days, along with eligible free service allowances.
• Azure App Service offers an $0 Free tier for development and testing, not supported production hosting.
• A published Windows App Service D1 Shared rate is $9.49 per month per site, under the referenced pricing configuration.
• Pay-as-you-go virtual machines are billed according to the selected compute meter and running time, with disks and networking priced separately.
• Azure Reservations can offer eligible resource savings of up to 72%, while compute savings plans can offer up to 65% under Microsoft’s published comparisons.
• Storage, network gateways, monitoring ingestion, and retained disks may continue generating charges even when the application has little traffic.

How Much Does Microsoft Azure Cost?

Microsoft Azure is a collection of cloud services rather than one bundled hosting product. Most spending falls into compute, storage, networking, databases, and operations. Each category uses different billing meters.

Microsoft’s Azure pricing overview provides product-specific prices and access to the pricing calculator. Some prices depend on the selected region and agreement, so a published number from one configuration should not be presented as universal.

Azure service	Primary billing unit	What changes the cost
Virtual Machines	Compute usage, often hourly-equivalent	VM size, OS, region, runtime, discounts
App Service	Selected service plan and instances	Plan tier, worker count, region
Blob Storage	Stored capacity and operations	Access tier, redundancy, retrievals
Managed Disks	Provisioned disk resources	Disk tier, size, performance
Azure SQL Database	Compute and storage allocation	Service tier, vCores or DTUs, backup retention
Azure Functions	Executions and resource consumption	Hosting plan, duration, memory and baseline capacity
Networking	Traffic and provisioned services	Outbound data, gateway hours, IPs, load balancers
Azure Monitor	Monitoring data and selected features	Log ingestion, retention, queries and alerts

A virtual machine price does not necessarily include everything necessary to operate a website. Microsoft explains in its VM cost planning documentation that disks, network bandwidth, monitoring, and other connected services can add separate billable meters.

For comparison, the consumer-focused Google Drive storage service uses subscription-style storage packages. Azure Blob Storage instead charges according to cloud infrastructure usage, so the products should not be compared solely by gigabytes.

Virtual Machine Pricing

Azure Virtual Machines are commonly used for application servers, databases, development environments, and workloads that require control over an operating system. Their principal compute cost depends on the selected VM family, size, image, licensing, region, and purchasing model.

A VM with two virtual CPUs cannot be assigned one reliable nationwide price without specifying the actual SKU. Windows images may also carry license costs that differ from Linux configurations.

Microsoft’s pricing calculator documentation uses 730 hours as a typical full-month VM estimate. An always-running machine can therefore consume substantially more compute than one used only during working hours.

Illustrative monthly VM calculation

Assume a VM has an entirely hypothetical compute price of $0.10 per hour. This is a calculation input, not a verified quotation for a particular Azure instance.

• Continuous operation for 730 hours costs $73 (about 2.4 hours of work at $30 per hour) in modeled compute.
• Operation for 160 hours costs $16 in modeled compute.
• The compute difference is $57 per month, before other resource costs.

The 160-hour option reduces modeled compute usage by approximately 78.1%. It does not guarantee a comparable total-bill reduction because managed disks, retained storage, and other provisioned resources may remain billable.

This distinction matters for development environments. A company running a test VM only during business hours can save substantially on compute, provided the machine is actually deallocated and can tolerate the scheduled downtime.

App Service and Serverless Costs

Azure App Service provides managed hosting for web applications and APIs. It can reduce the system-administration work associated with running a conventional VM, but the charge depends on the hosting plan and allocated workers.

Microsoft’s Windows App Service pricing page lists an $0 F1 plan with limited shared resources. The Free tier is intended for experimentation and learning. It has no production service-level agreement, and Microsoft does not support production workloads on that tier.

The published D1 Shared configuration has been listed at $9.49 per month per site. This is a specific Shared-tier offer, not a recommended production hosting budget. Dedicated Basic and Premium plans are charged according to their configured compute instances, with additional capabilities and scaling options.

Azure Functions

Azure Functions offers event-driven execution without requiring every workload to operate an always-running application server. The billing model depends on the hosting plan.

According to Microsoft’s Azure Functions price schedule, the Consumption plan includes a monthly free grant of one million executions and 400,000 GB-seconds on eligible pay-as-you-go subscriptions.

The Flex Consumption plan uses different free allowances and billing meters. Premium and dedicated hosting plans also differ, especially where baseline provisioned capacity is required.

Free executions do not make an entire application free. Associated storage accounts and networking services can generate charges outside the Functions execution allowance.

Azure Storage Pricing

Azure offers several storage products intended for different workloads. Blob Storage handles objects, Azure Files provides managed file shares, and Managed Disks provide persistent storage for virtual machines.

Blob Storage is divided into access tiers, including Hot, Cool, Cold, and Archive, where available. The official Blob Storage pricing documentation shows that cheaper storage tiers can carry higher access and retrieval costs.

For frequently downloaded application assets, a low storage price can be misleading. Requests, data retrievals, and outbound network traffic may collectively make the cheapest capacity tier more expensive for that usage pattern.

Archive is intended for infrequently accessed data. Rehydration takes time and can involve additional charges, making it unsuitable for objects that an application must retrieve immediately.

Disk pricing operates differently. A VM may retain chargeable disks when the compute resource is stopped. Deleting the VM without reviewing its attached and detached resources can leave ongoing storage expenses.

The storage decision should therefore consider four costs together: capacity, operations, retrieval, and data transfer. A storage-only comparison ignores potentially important expenses.

Database and AI Service Costs

Managed databases charge for the resources or consumption model selected, not simply for the number of records stored. Azure SQL Database offers DTU-based and vCore-based configurations, including provisioned and serverless options.

Microsoft’s Azure SQL pricing schedule explains that serverless configurations can scale compute with demand and may automatically pause when eligible conditions are met. Provisioned compute is usually more appropriate for steady workloads, while serverless can benefit intermittently used databases.

Storage and backup charges require separate attention. A database configured for regional redundancy or longer backup retention may have a materially different total from a small development database.

Azure Cosmos DB uses its own throughput and storage pricing structures. Azure Database for PostgreSQL and other managed database products have different allocation models. Their prices should not be combined into one generalized database rate.

AI workloads introduce another layer. Azure-hosted model inference can be metered by tokens, requests, or provisioned throughput, depending on the product and deployment. GPU virtual machines are a separate compute category. Neither approach has a useful fixed monthly average without model selection, traffic volume, and capacity requirements.

The Hidden Cost of Networking

Networking is one of the easiest parts of an Azure estimate to underestimate. A working application may require public IP addresses, load balancing, private connectivity, or outbound network access in addition to its compute resources.

Azure’s bandwidth pricing schedule distinguishes inbound traffic from chargeable outbound traffic. Internet egress and transfers between regions can follow different rules. Not every network transfer uses the same rate.

An application sending 1,000 GB of chargeable data outward in a month is not equivalent to one receiving 1,000 GB. The direction, destination, and eligible free allowances affect the final amount.

Other potential expenses include NAT gateways, load balancers, private endpoints, cross-region replication, and monitoring services. Some have hourly provisioned charges even during periods of low traffic.

The hidden-price finding is that reducing compute utilization does not necessarily eliminate the surrounding infrastructure bill. An organization may successfully shut down its application VM yet continue paying for disks, retained data, gateways, and other deployed resources.

Azure Discounts

Azure supports pay-as-you-go pricing, reservations, savings plans, and Spot VMs. These options solve different problems and should not be treated as interchangeable discounts.

Microsoft’s free account offer provides qualifying new customers with $200 (about 6.7 hours of work at $30 per hour) in credit for 30 days, selected free monthly quantities for 12 months, and always-free allowances for certain services.

Free allowances have eligibility and usage limits. Once the credit period ends, continuing a workload on a paid subscription can generate regular charges.

Reservations and savings plans

Microsoft describes potential reservation discounts of up to 72% and compute savings plan discounts of up to 65% in its Azure cost savings guidance. Those are maximum advertised comparisons for eligible usage, not reductions that every customer receives.

A reservation generally works best for stable, predictable resource requirements. A savings plan involves a monetary hourly commitment with broader eligibility across participating compute services.

Under Microsoft’s savings plan rules, unused hourly commitment expires. Storage, networking, and software charges may also fall outside the relevant discount.

A business can therefore lose money by making a commitment larger than its actual eligible usage. Right-sizing resources before purchasing a discount is often more valuable than discounting unnecessary capacity.

Spot virtual machines

Spot VMs use available Azure compute capacity at variable discounted prices. Microsoft’s Spot VM guidance describes potential savings of up to 90% compared with standard pay-as-you-go VMs.

The tradeoff is eviction risk. Azure can reclaim the capacity, and the workload may receive only brief notice. Spot is better suited to interruptible batch processing, testing, and fault-tolerant jobs than to a single critical production server.

An Azure Bill

A complete budget should combine the resource quantities that an application actually needs. Consider a small business running one always-on web application and a modest database, with routine backups and public internet traffic.

The following is an illustrative planning model, not an Azure quote or a representative customer invoice. The assumed dollar figures are used to demonstrate cost arithmetic because the actual resource SKUs and region have not been selected.

Component	Illustrative monthly allowance
Application compute	$100
Managed database	$80
Storage and backups	$20
Networking	$25
Monitoring	$15
Modeled monthly total	$240

The modeled annual budget is $240 × 12 = $2,880, before taxes, support upgrades, unexpected usage, and migration expenses.

Compute represents $100 ÷ $240 = 41.7% of this illustrative budget. The remaining 58.3% lies outside the application compute allowance. A company concentrating only on its server’s hourly rate would therefore overlook most of the modeled spending.

Reducing the modeled compute line by 30% saves $30 monthly, bringing the whole estimate to $210. The total-bill reduction is only 12.5%, assuming the other components stay unchanged. That is why a percentage discount on one Azure resource should not be advertised as an equivalent reduction in the entire cloud bill.

For a direct competitor comparison, the separate guide to AWS server costs covers comparable infrastructure concepts. A valid AWS-versus-Azure comparison must use matching compute, storage, region, traffic, uptime, and availability assumptions.

How to Control Azure Spending

The starting point is Microsoft’s Cost Management service. It can show spending by subscription, resource group, service, and other dimensions, helping identify the products driving the actual invoice.

Microsoft’s cost planning guidance recommends estimating workloads before deployment and reviewing usage after resources are running. Budgets and alerts improve oversight, although a budget alert alone should not be assumed to stop every billable service.

Makes sense if

• Use pay-as-you-go during early development or uncertain demand.
• Choose reservations for stable, well-understood eligible workloads.
• Choose savings plans when eligible compute changes across services or regions.
• Use Spot only when interruptions are acceptable.

Does not make sense if

• Buying a long commitment before measuring normal utilization.
• Using an App Service free development plan for critical production hosting.
• Keeping oversized databases and VMs running without a business need.
• Assuming deleting application code also removes every billed cloud resource.

Cost control also requires checking idle disks, orphaned IP addresses, monitoring retention, backup duplication, and resources deployed in unused regions. Review the complete monthly invoice, not only the largest VM or database line.

What We Verified

• Microsoft’s free-account offer and the distinction between promotional credit and continuing free allowances.
• App Service’s Free-tier production restrictions and published Shared-plan price.
• The separate billing treatment of VM compute, managed disks, bandwidth, and monitoring.
• Consumption-plan allowances for Azure Functions and the distinction between compute and associated storage.
• The eligibility differences and commitment risks of reservations, savings plans, and Spot instances.
• The worked budget and VM-hours examples are explicitly modeled calculations, not observed Azure invoices.

Answers to Common Questions

Does Microsoft Azure have a monthly subscription fee?

Azure generally charges for the services and resources consumed rather than requiring one universal infrastructure subscription fee. Specific products, support plans, and purchasing agreements can create recurring commitments.

Can Azure cost nothing?

Yes. Qualifying free services can cost $0 when their eligibility conditions and usage limits are met. Additional services or usage beyond those allowances may be billed.

Is Azure cheaper than AWS?

Neither platform is always cheaper. The answer depends on equivalent configurations, workload patterns, regional rates, software licenses, discounts, and associated data-transfer charges.

Does stopping an Azure VM stop all charges?

No. Deallocating a VM can stop its compute charges, but retained disks, storage, networking resources, and other deployed services may remain billable.

How do I estimate my Azure costs?

Use Microsoft’s Azure Pricing Calculator with the intended region, service tier, resource size, runtime, storage, traffic, redundancy, and purchasing options. Compare the estimate with Cost Management data after deployment.