How to Use the Azure Pricing Calculator: An Azure Cost Calculator Guide for Indian Enterprises

The Azure Pricing Calculator, often searched for as the Azure cost calculator, gives you a number. The first invoice gives you a different one. The gap is often large, and it is rarely because the calculator is wrong. It is because the estimate was built with the defaults: the wrong region, pay-as-you-go pricing on servers that never stop, no licence reuse, and nothing for the network, support and security lines that only appear on the bill.

The short answer. Choose an Indian region first, enter the hours each server really runs, move steady servers to a reservation or savings plan, apply Azure Hybrid Benefit where you already own the licences, and add the lines the calculator does not prompt for: network, support, Defender, monitoring and backup. Then keep the estimate and compare every monthly bill with it.

This guide covers how to configure the calculator so the number survives contact with the invoice, which costs it leaves out, how to use it for ongoing cost control rather than a one-time pitch, and what a realistic estimate looks like for a mid-size Indian estate. Prices and discount ceilings were checked against Microsoft's published pricing in October 2026; confirm the current figures on the pricing page before you commit.

• About 45%: lower than the calculator defaults, for the same 35 VMs in the worked example below
• 730 hours: what the calculator assumes every server runs each month; a business-hours dev box runs about 170
• Up to 72%: off compute for a three-year reservation, and 0% if the line is left on pay-as-you-go

What the Azure Pricing Calculator is, and what it is not

The calculator lives at azure.microsoft.com/pricing/calculator. You add services, choose a region, tier and usage pattern, and it returns an estimated monthly cost. It is good at three things: comparing architectures, producing an order-of-magnitude figure, and producing an Azure figure you can set beside an AWS or Google Cloud estimate from their own calculators.

It is not a quotation. Actual charges follow actual usage. It is not complete: several categories are easy to miss or absent by default. And it is not optimised: every compute line starts on pay-as-you-go, which is the most expensive way to buy a server that runs all month.

Read it as a floor. Your bill will be higher than the estimate unless you deliberately configure the savings and add the hidden lines. Both are covered below.

Start with a TCO business case, not the pricing calculator

Most teams skip the total cost of ownership comparison and go straight to pricing. For a migration business case that is backwards. Microsoft's standalone TCO calculator has gone, and its old page now redirects to a blog post; the comparison lives in the Azure Migrate business case, which sets five years of on-premise cost, including hardware refresh, data centre power and cooling, software licensing and the staff time spent keeping it running, against the same period on Azure.

That comparison is what a board signs off. The pricing calculator then tells you what the Azure side of it costs per month. The one-time cost of getting there is a separate number, broken down in what a cloud migration costs in India.

Two adjustments for Indian estates. Replace the default assumptions with your own figures: your actual IT staff, storage and facilities costs, and your real power and cooling costs. Several defaults are US-dollar benchmarks, so they may not reflect Indian prices or tariffs.

Step by step: configuring the pricing calculator accurately

Step 1: choose the region before anything else

Prices differ by region, sometimes by 20–35% for the same virtual machine, even between Indian regions. Set the region on every line: each new line in the calculator defaults to East US. For most Indian enterprises the choice is between Central India (Pune), India South Central (Hyderabad), South India (Chennai) and West India (Mumbai). Compare Central India with India South Central and South India for your VM family: for current D-series sizes, South India is markedly dearer. Keeping data in an Indian region also simplifies residency questions: the DPDP Act 2023 does not by itself require personal data to stay in India, but sector rules such as RBI's payment data localisation can, and many customer contracts ask for it.

A common mistake in inherited estimates is a US or European region left over from a pilot. Change it on every line and the whole estimate moves.

To see figures in rupees, set the calculator's currency to Indian Rupee (INR). The rupee figures are converted from US dollar list prices and exclude GST.

• Central India. City: Pune; What to know: Broad service catalogue, availability zones; paired with South India
• India South Central. City: Hyderabad; What to know: Newer region with availability zones; D-series prices close to Central India; paired with Central India; check service availability
• South India. City: Chennai; What to know: Broad catalogue, no availability zones; for current D-series typically 18–35% dearer than Central India; paired with Central India
• West India. City: Mumbai; What to know: Smaller service catalogue, no availability zones; useful mainly when latency to Mumbai decides

Step 2: add compute with real hours and the right pricing model

For each VM workload:

• Pick the series for the job: D-series for general workloads, E-series for memory-heavy databases, F-series for compute-bound jobs, B-series for small, bursty utility servers.
• Enter the hours it will actually run. The calculator defaults to 730 hours a month. A development server used in business hours runs about 170. Leaving 730 on every line is one of the biggest inflations in many estimates.
• Switch the pricing model from pay-as-you-go to a one-year or three-year reservation for anything that runs continuously. Reservations reach up to 72% off on the compute component for a three-year term; a savings plan for compute reaches up to 65% and is more flexible about VM family. For the first 18 months in Azure, one-year terms are the sensible default, because you do not yet know how the estate settles.
• Apply Azure Hybrid Benefit if you own Windows Server licences with Software Assurance. The VM then bills at the Linux rate, which in Central India removes close to half the pay-as-you-go price of a D-series Windows VM; combined with a reservation, Microsoft puts the saving at up to 80% for Windows Server and up to 85% for SQL Server. The toggle is on the compute line in the calculator and, later, on the VM itself. It is off by default in both places; our guide to Hybrid Benefit and reservations sets out the order to apply the two.

Step 3: add storage as its own lines

Storage is undercounted because it is scattered. Add, separately: a managed disk for every VM in the correct tier (Standard HDD, Standard SSD or Premium SSD; most application disks do not need Premium), blob storage for backups and logs in the right access tier (hot, cool, cold or archive), and snapshot storage. Snapshots accumulate silently and are rarely in the first estimate.

Step 4: add the network

This is a category estimates often miss. Three lines:

• Outbound data transfer. Azure charges per gigabyte for data leaving its network after the first 100 GB a month. Estimate your monthly egress to users and external systems. For a 200-person enterprise running ordinary web applications, ₹15,000–30,000 a month before GST is a reasonable planning figure; a public-facing product can be far more.
• A VPN gateway or ExpressRoute circuit if you keep anything on-premise, which most Indian enterprises do during and after a migration.
• Load balancers and NAT gateways for multi-instance services. Both have an hourly charge and, for NAT, a per-gigabyte charge on top.

Step 5: add platform services separately

Azure SQL Managed Instance, Azure Kubernetes Service, App Service, Azure Functions, Cosmos DB and the rest are not part of a VM estimate. Add each one with its own tier and expected consumption, and give consumption-based services a sensible ceiling rather than the default.

Step 6: add monitoring and backup

Azure Monitor and Log Analytics bill on data ingested and retained, so estimate gigabytes per day, not a flat line. Azure Backup bills per protected instance plus storage; ₹500–2,000 per VM per month before GST is a reasonable planning range depending on data volume and retention. Both lines are routinely absent from first estimates and present on every bill. Our backup and disaster recovery guide covers what the backup line should include.

The hidden costs that turn a good estimate into a surprise

Even a carefully built calculator estimate often leaves out six lines that appear on the invoice.

1. Support plan. The calculator has a support selector, but it sits at the bottom of the estimate and defaults to Basic, which is free. Developer, Standard and Professional Direct support list at USD 29, 100 and 1,000 a month, about ₹2,800 to ₹96,000 before GST. Most production estates need at least Standard.
2. Microsoft Defender for Cloud. Only the free foundational posture checks are on by default. Paid plans start billing as soon as anyone enables them, at subscription or management-group level or while following a recommendation, the 30-day trial converts to paid automatically, and once a plan is on, every resource of that type in its scope is billed. Defender for Servers, for example, charges per server per month. Decide which plans you want; switch off the rest.
3. Idle and oversized resources. The calculator assumes you provision what you use. Twelve months after a migration, a meaningful share of a typical estate is oversized, stopped but still billing, or forgotten. This is a governance cost, not an Azure cost, and it is the reason ongoing cost management matters more than the initial estimate.
4. SQL Server licensing. SQL VM prices depend on whether you bring your own licences. Azure Hybrid Benefit for SQL Server can cut SQL VM cost substantially (Microsoft puts the ceiling at up to 85% when combined with other offers); the calculator only shows that if you tell it. Enterprise edition where Standard would do is the other common waste.
5. Development and test environments at production prices. Enterprise Dev/Test subscriptions remove the Windows licence component and discount several services for non-production use. If dev and test are in the main subscription, they are billed as production.
6. Currency. Azure list prices are in US dollars, Indian invoices convert at the prevailing rate, and GST is added on top of every line. Budget a 5–8% buffer, or negotiate INR commercial terms through a Microsoft partner in India.

Using the calculator for ongoing cost management

Most organisations use the calculator once, at migration time, and then never open it again. The estimate becomes useful precisely when you keep comparing against it.

The monthly routine: the saved calculator estimate beside the Cost Management export. Any line more than 20% over is investigated. Illustrative figures for the 35-VM estate below.

• Monthly review. Export the cost breakdown from Cost Management and compare it, line by line, with the saved calculator estimate. Any line more than 20% over is an investigation, not a trend to accept.
• Right-sizing. Azure Advisor flags underused VMs continuously. Dropping one size in the same family roughly halves that VM's compute cost. Resizing a D4s v5 that idles at 8% CPU to a D2s v5 saves about ₹7,000 (Linux) to ₹13,500 (Windows) a month at Central India pay-as-you-go list prices; multiply by the number of such machines in your estate.
• Reservation coverage. Aim for 70–80% coverage of steady production workloads. Anything that has run three months without change belongs on a one-year reservation. Model the saving in the calculator before buying; it is the same tool.
• Commitment length. Three-year terms save more and lock you in. One-year terms are right for most Indian enterprises in the first 18 months; by the second renewal you understand the estate well enough to go longer.

If you want a broader checklist than Azure alone, the same discipline across Azure, AWS and Google Cloud is in our Cloud Cost Audit Checklist for Indian enterprises, with where to look on each platform for the key checks.

What a realistic estimate looks like for a mid-size Indian enterprise

For illustration, take a 300-person manufacturer near Pune with 40 servers on-premise. The migration scope is 35 VMs to Azure Central India and 5 retained on-premise for compliance. Built with the steps above (one-year reservations, Hybrid Benefit on Windows and SQL, business-hours schedules on non-production, storage tiered), the monthly estimate looks like this. Figures are illustrative and rounded; your estate will differ.

Configured estimate, rupees per month (total about ₹4,31,000)

• Compute: 35 D-series VMs, 1-year reservation, Hybrid Benefit: ₹2,80,000
• Storage: managed disks and blob backup: ₹45,000
• Networking: egress and a VPN gateway: ₹35,000
• Azure Backup: ₹22,000
• Currency and contingency, 5%: ₹21,000
• Azure Monitor and Log Analytics: ₹18,000
• Standard support: ₹10,000

The same architecture on calculator defaults, pay-as-you-go with no licence reuse and no schedules, comes to roughly ₹7,80,000 a month. Both figures are before GST and assume a mix of Linux and smaller Windows VMs, most with less than 50 GB of protected data; an estate of larger Windows VMs will be higher on both sides, and the gap between them wider.

Same 35 VMs, two ways of filling in the calculator

• Calculator defaults: pay-as-you-go, 730 hours, no Hybrid Benefit: ₹7,80,000
• Configured: reservations, Hybrid Benefit, schedules, tiered storage: ₹4,31,000

• ₹3,49,000: a month, the value of the configuration choices alone
• About ₹42 lakh: a year, before anyone touches the architecture

That is why the way you fill in the calculator matters more than which VM series you pick.

Where the estimate meets the engagement

The calculator is a good tool that many teams use badly: wrong region, pay-as-you-go everywhere, nothing for the network, no Hybrid Benefit, 730 hours on servers that run 170. Each mistake is small. Together they explain most of the gap between the estimate and the invoice.

What a managed Azure engagement adds in the pre-migration phase is not a slide deck. It is a cost model built from your actual estate and licences, a 12-month run-rate forecast, a reservation coverage plan, and the monitoring and cost governance that keeps the number true after go-live. Backup and disaster recovery are priced in from the start rather than discovered on the second invoice.

If you would rather have that model than a rough number from a self-serve tool, talk to us. We can build it with you, so you know what Azure is likely to cost before you commit.

Frequently asked questions

Is the Azure Pricing Calculator free to use?

Yes. It requires no account and no commitment. Estimates can be saved if you sign in with a Microsoft account, and shared by link or exported to Excel, which is useful for keeping the baseline you will compare bills against later.

Which Azure region is cheapest for Indian enterprises?

It depends on the service. For current D-series VMs, Central India and India South Central are usually cheaper than South India and West India, but prices differ by VM family and change over time. Compare them in the calculator for your main VM series, and let latency and resilience needs decide if the difference is small.

Should I use a reservation or a savings plan?

A reservation gives the deeper discount but is tied to a VM family and region. A savings plan commits to an hourly spend across eligible compute and lets the family change. For a stable estate, reservations; for one that is still moving, a savings plan; many Indian enterprises end up with both.

How accurate is the calculator?

For the lines you enter correctly, it uses Microsoft's list prices, so those lines will be close. The gap comes from what is missing: network, support, Defender, backup, monitoring, idle resources and currency. Add those and compare monthly, and the calculator becomes an accurate planning tool rather than a sales figure.

Does Azure Hybrid Benefit apply to Linux?

Yes, for Red Hat Enterprise Linux and SUSE subscriptions, in addition to Windows Server and SQL Server. The eligibility rules differ by product; the Windows and SQL benefits require active Software Assurance or an eligible subscription.