Windows Server Licensing Cost in India: A 2026 Buyer's Guide

The quote that made my client switch back to on-prem AD
Last October a 90-person logistics firm in Peenya sent me a quote they'd received from a large reseller. Windows Server 2022 Datacenter, 16 cores, Open NL, plus 90 user CALs, plus SA. Total: ₹11,42,000 before GST. They wanted a second opinion because the number felt wrong.
It was wrong. Not illegally — just badly scoped. They were running two Hyper-V hosts with a combined six VMs: a domain controller, a file server, a Tally ERP application server, an antivirus management box, a print server, and a backup proxy. A Datacenter licence was never required. Two Standard licences — one per host — covered all six VMs legally, because Standard permits two OSEs (Operating System Environments) per host when the host is only running Hyper-V. The correct stack came to ₹3,86,000 plus GST. They saved ₹7.5 lakh on hardware they didn't need.
I see this constantly. Windows Server licensing cost in India is not a number you look up — it's a calculation that depends on cores, VMs, edition, CAL type, and whether you buy SA. Get one variable wrong and you either overpay by lakhs or fail a Microsoft audit. This guide walks through the actual 2026 pricing, the break-even math, and where the traps are.
All figures below are Open No Level (Open NL) and CSP list pricing as of Q1 2026, exclusive of GST. The 18% GST applies on top for Indian buyers. Open NL is what most SMEs under 250 PCs qualify for; larger firms go Open Value or an Enterprise Agreement (EA), both of which can be 15-30% cheaper at volume but with a three-year commitment.
The unit you're actually buying: two cores, not a server
Microsoft stopped selling per-processor licences in 2016. Since then every Windows Server licence is sold as a pack that covers two physical cores. To licence a single server you multiply the core count by half, round up, and that's the number of packs.
A Dell PowerEdge R760 with a single Xeon Gold 6438Y+ has 32 cores. To fully licence it you need 16 two-core packs. If it has dual that same CPU — 64 cores total — you need 32 packs. That is the entire maths. There is no per-server price anymore.
The 16-core minimum nobody remembers
When you buy a Standard or Datacenter licence, Microsoft charges you for at least 16 cores per physical processor. If your server has a 12-core Xeon, you still pay for 16. This matters constantly in India because a lot of budget servers come with 8-core or 12-core processors and buyers assume they'll pay less. They don't. A 12-core Silver 4410Y and a 16-core Silver 4416+ cost the same in licensing terms.
If you're buying new hardware specifically, aim for exactly 16 cores per socket at the low end. Going to 20 or 24 cores only makes sense if you genuinely need the compute. Every additional core is an additional licensing cost that compounds across VMs and SA renewals.
Core factors and how they're counted
- Physical cores on the motherboard. Hyper-threading is not counted — 16 cores / 32 threads is licensed as 16 cores.
- All cores on the processor must be licensed, even if Hyper-V is configured to use fewer.
- Fault tolerance counts. If you have a passive failover host, it still needs licences unless you have SA and the standby is genuinely cold (see the SA section below).
Standard vs Datacenter: the only break-even that matters
Here's the comparison everyone searches for.
| Edition | 2-core pack list price (2026, Open NL, ex-GST) | 16-core server licence | Included Windows Server OSEs |
|---|---|---|---|
| Windows Server 2022 Standard | ₹9,400 | ₹75,200 | 2 (1 physical + 1 virtual, or 2 virtual on a Hyper-V-only host) |
| Windows Server 2022 Datacenter | ₹54,000 | ₹4,32,000 | Unlimited OSEs on the licensed host |
The gap is roughly 5.7x. To break even in favour of Datacenter, you need to be running more than 13 Windows Server VMs on a single host (because 14 Standard VMs on one host needs 7 Standard licences stacking to about ₹5,26,400 — pass Datacenter).
That's the theoretical break-even. In the real world, most Indian SMEs run 5-12 VMs per host and Standard is almost always correct. Datacenter only wins when:
- You're running a private cloud with 15+ Windows Server VMs per host
- You're doing HCI with Storage Spaces Direct (which requires Datacenter)
- You need Software-Defined Networking (SDN)
- You're a hosting provider selling Windows VM capacity commercially (Datacenter is mandatory for SPLA-style scenarios)
Datacenter is also the right answer if you're planning to ignore per-VM counting and just not think about it for three years. That's a legitimate reason. It costs more but it removes an audit risk. I'll be honest — for a client running 8 VMs on a single host who expects to grow to 20 in two years, I sometimes recommend Datacenter just to stop the counting exercise. It's a borderline call.
Where Datacenter is genuinely, dangerously mis-sold
Every quarter I come across a Datacenter licence on a server running three VMs. The reseller sold it because it makes them more commission, and the buyer didn't know to ask. If you're being quoted Datacenter and your VM count is under 10, demand the Standard equivalent in writing before you sign anything. There is no feature in Datacenter besides the OSE count and the HCI/SDN features listed above. You get the same Windows Server experience. Same support path. Same updates.
CALs — the part where people get fined
A Common Access Licence (CAL) is required for every user or device that accesses Windows Server services. CALs are separate from the server licence. They are not optional, they are not included, and Microsoft audits them.
There are two types.
User CALs vs Device CALs
| CAL type | When it's right | 2026 Open NL list price (ex-GST) |
|---|---|---|
| User CAL (2022) | One person, multiple devices — desks, laptops, mobiles | ₹2,860 each |
| Device CAL (2022) | One device, multiple people — shift terminals, factory floor PCs | ₹2,480 each |
| RDS User CAL (2022) | Remote Desktop Services — per user accessing an RDS session host | ₹8,920 each |
| RDS Device CAL (2022) | Per device accessing RDS | ₹7,180 each |
The rule of thumb: count humans if users outnumber devices 1:1 or better; count devices if a machine is shared by shifts. A 50-person firm with laptops generally buys 50 User CALs. A hospital with 200 nursing staff and 30 shared ward terminals buys 30 Device CALs. The Device CAL route saves ₹4,97,600 in that scenario — 200 User CALs at ₹2,860 is ₹5,72,000 against 30 Device CALs at ₹2,480 for ₹74,400. This is why the type matters more than the count.
The CAL trap: not only AD login counts
Here's the bit nobody explains properly. A CAL is required for any access to Windows Server services, including:
- Authentication against Active Directory
- Access to a file share on a Windows Server
- DNS resolution against a Windows DNS server
- DHCP assignment from a Windows DHCP server
- Printing through a Windows print server
- Access to line-of-business apps (Tally, Busy, ERP) hosted on Windows Server
- Access via third-party applications that authenticate against AD (including some NAS devices)
The exclusions are narrow: unauthenticated access to published web services, and anonymous access to a Windows Server acting as an internet-facing web server. That's basically it.
Where the audit lands
The named failure story: a Bengaluru SaaS company with 210 staff got hit with a Microsoft true-up in early 2025. They had 210 User CALs — correct — but they had forgotten RDS CALs entirely. Every one of their 40 support staff logged into a Remote Desktop session host running Tally. That's 40 RDS User CALs missing at ₹8,920 each. Microsoft's audit tool found them in a day. True-up cost: ₹3,56,800 plus 18% GST, plus a penalty settlement of ₹1,15,000. Total ₹5,36,024.
What fixed it going forward? They bought 40 RDS User CALs with SA (which gives them the right to future version upgrades), documented the entitlement in their IT asset register, and set a calendar reminder for the three-year SA renewal. The lesson isn't "buy more CALs." It's "track what you have and match it to what actually accesses the servers."
I'll say the blunt thing here: Microsoft audits in India have become more common in the last 24 months, and the profit motive is real. If your CAL count doesn't match your AD user count, fix it before someone else finds out.
Software Assurance: worth it, or rent disguised as insurance?
Software Assurance is an annual fee — roughly 25% of the licence list price per year — that gives you:
- Rights to the next version of the product when it releases
- Licence Mobility (move the licence to new hardware or a different cloud)
- Cold Disaster Recovery rights (a standby DR host doesn't need its own licence)
- Windows Server Hybrid Benefit eligibility for Azure (this is the big one)
- Extended support beyond the standard lifecycle
- Access to Microsoft's Virtual Academy and planning services
The break-even on SA: if you plan to upgrade Windows Server within three years, and the next version would cost you the full licence again (₹75,200 for 16-core Standard), then SA at ₹18,800/year over three years = ₹56,400 is cheaper than a fresh buy. That's the maths. And that next version is coming — Windows Server 2025 shipped in late 2024, and the next release is on Microsoft's roadmap for 2027-2028.
Where SA does not pay off:
- You're running an old ERP app that only works on Server 2016 and you have no upgrade plans. Then SA is annual money for zero benefit. Skip it.
- You're replacing hardware entirely and moving to cloud. If you're going to Azure anyway, SA is often replaced by Azure Hybrid Benefit calculations.
- Small environment where the next upgrade is more than three years out. Buy outright, no SA.
Windows Server Hybrid Benefit = real money in Azure
If you're considering Azure VMs, Software Assurance and the Hybrid Benefit let you apply your on-prem Windows Server licence to an Azure VM, saving roughly 40% of the Windows VM cost. For a 16-core VM running 24/7 (an E16s_v5, roughly ₹78,000/month pay-as-you-go for the Windows portion), Hybrid Benefit cuts the Windows line item significantly. That alone frequently justifies SA on the on-prem licence. If you have any Azure footprint, run this calculation.
What the total actually looks like — three worked scenarios
Scenario 1: 20-user startup, single physical server
- HP ProLiant DL360 Gen11, single 8-core Xeon — but licences minimum 16 cores
- Windows Server 2022 Standard, 16-core: ₹75,200
- 20 User CALs: ₹57,200
- No SA
- Subtotal: ₹1,32,400 + GST ₹23,832 = ₹1,56,232
Don't buy Datacenter here. Don't buy SA unless you have an upgrade planned. This is the cheapest correct configuration.
Scenario 2: 75-user SME, two Hyper-V hosts, 8 VMs total
Each host runs 4 VMs, both hosts are active (no DR standby).
- 2x Windows Server 2022 Standard, 16-core: ₹1,50,400
- 75 User CALs: ₹2,14,500
- SA on both Standard licences at 25%: ₹37,600/year
- Year-1 subtotal: ₹4,02,500 + GST ₹72,450 = ₹4,74,950
- Year-2 onwards: ₹37,600 + GST = ₹44,368/year (SA renewal only)
If they were quoted Datacenter for this, someone was padding the quote. Total Datacenter cost would be ₹8,64,000 before GST just for the two host licences.
Scenario 3: 150-user, virtualisation-heavy, 22 Windows Server VMs
Three Hyper-V hosts with 12, 8, and 4 VMs respectively. Host A's 12 VMs would need Standard x6, Host B's 8 VMs need Standard x4, Host C's 4 VMs need Standard x2. Twelve Standard licences = ₹9,02,400. Datacenter x3 hosts = ₹12,96,000. They're within range. What tips it: the client planned to grow Host A to 18 VMs within two years. Datacenter wins on the growth projection.
- 3x Windows Server 2022 Datacenter, 16-core: ₹12,96,000
- 150 User CALs: ₹4,29,000
- SA on Datacenter: ₹3,24,000/year
- Year-1 subtotal: ₹20,49,000 + GST ₹3,68,820 = ₹24,17,820
Big number, but note the SA renewal: ₹3,82,320/year including GST, which is what they pay annually thereafter. Datacenter gets expensive at the SA line fast.
Where resellers pad the quote (and how to spot it)
A quick checklist before you sign any Windows Server quote in India:
- Too many cores licensed. Re-count the physical cores in the server spec sheet. If the quote says "licence for 64 cores" and the CPU has 16 cores, you're being over-quoted.
- Datacenter for low VM count. Under 10 VMs per host, Standard. Full stop.
- Duplicate CALs. Sometimes buyers pay for both User and Device CALs against the same population. You only need one type.
- SA on hardware that's being retired. If the server is going to be replaced in 12 months, SA renewal is money down the drain.
- "Microsoft Certified Partner" surcharges. These are made up. Microsoft license pricing is published. Any competent reseller quotes from the same list.
- Wrong Open programme. A 500-PC company can't buy at Open NL rates, and a 10-PC company shouldn't be pushed into Open Value with a three-year commitment.
We regularly do licence reviews for clients as part of our software licensing services — 9 times out of 10 there is 20-40% that can be cut from an existing or proposed agreement.
GST, TDS, and the boring details that matter
GST: Windows Server licences are taxed at 18% IGST or CGST+SGST depending on inter-state or intra-state supply. If your reseller is in Karnataka and you're in Karnataka, expect CGST 9% + SGST 9%. If you're buying from a Delhi distributor, IGST 18%. There is no GST exemption for these licences. Input tax credit is available to GST-registered businesses.
TDS: If you're buying a licence as a one-time purchase from an Indian entity, TDS under Section 194J (professional services) or 194C may apply depending on how the invoice is structured. Most licence sales are treated as goods supply and do not attract TDS. If your finance team is confident, structure as goods. If unsure, ask your CA — this is not a place for guesses.
Documentation: Microsoft's audit defence is documentation. Keep every invoice, the licence agreement, and a register of every server, its core count, and every CAL allocated. If you have SA, keep the renewal proof. Paperwork is what saves you, not eloquence.
The DPDP and CERT-In angle (briefly)
None of this changes your Windows Server licensing cost directly. But two regulatory realities do sit alongside the licensing decision in India:
- DPDP Act 2023: if you're processing personal data on a Windows Server (which is almost always true if you have customer records, HR files, or employee emails), your server needs logging, access control, and retention mechanisms. Most of this is achievable with Windows Server's built-in tooling plus a compliance add-on like ManageEngine or Lepide — budget ₹2-8 lakh one-time depending on user count.
- CERT-In 2022 directions: six-hour incident reporting, 180-day log retention. This affects your storage sizing and your backup design, which indirectly affects the server config you're licensing. Don't buy a minimum-spec server that can't hold 180 days of logs.
If DPDP or CERT-In compliance is on your roadmap, that's a conversation worth having before you fix the server configuration, not after. Our team handles this routinely — see our contact page to start that scoping.
A note on the Synology / TrueNAS question
Half the readers searching this topic are also wondering whether they should just buy a Synology DS1621+ or a TrueNAS box and skip Windows Server entirely. Fair question. For light file sharing, print serving, and NAS-style workloads, a ₹1.2-1.8 lakh Synology is genuinely cheaper than a Windows Server stack. We install them regularly.
But it doesn't replace Windows Server if you're running:
- Active Directory with Group Policy
- Tally/Busy on a client-server deployment that expects Windows printing and permissions
- Line-of-business apps that require Windows Server APIs
- Any environment where users expect drive-letter mapping and AD-based permissions
We are not going to pretend Synology is a Windows Server replacement in those cases. It isn't. If you're at a size where AD still matters, Windows Server is the answer, and the licensing cost is a real cost.
FAQ: Windows Server licensing questions we get every week
Q: Can I buy a Windows Server licence once and use it forever? Yes. The licence is perpetual for the version you bought. You can keep running Windows Server 2022 forever. What you lose without SA is the right to upgrade to 2025 or later versions, and the licence mobility rights if you replace the hardware later. Perpetual licences remain valid but frozen at that version.
Q: What happens if I install Windows Server on more cores than I've licensed? You are out of compliance. The server will run — Windows doesn't enforce core counts at runtime — but if Microsoft audits you, you owe a true-up for the shortfall plus potential penalties. The honest answer: nobody's technical infrastructure prevents this, only your process does. Audit yourself before someone else does.
Q: Do I need CALs for users who only access via a web browser? If it's a public unauthenticated web service, no. If it's an authenticated web app that touches Windows Server services (AD, SQL, file shares), yes. The distinction is authentication, not browser vs thick client.
Q: Is Windows Server 2019 cheaper than 2022? No. Current pricing is version-agnostic. Microsoft sets Standard and Datacenter at the same price points across the 2019, 2022, and 2025 releases. What changes is availability — you generally can't buy 2019 new anymore from authorised channels. You can buy 2022, or 2025 with downgrade rights to 2022.
Q: Can I move my Windows Server licence to a new server when I upgrade the hardware? Only if you have Software Assurance (Licence Mobility) or the older Software Assurance-equivalent rights. A bare perpetual licence is tied to the hardware it was first assigned to. This catches people out when they replace a server at year three: they assume the licence follows the workload. It doesn't, unless you paid for SA.
Q: Is there a cheaper way to run Windows workloads — containers or Azure? Yes for some workloads. Windows containers on an Azure Container Apps plan or AKS don't require the same per-OSE licensing. Azure VMs with Hybrid Benefit can be cheaper than on-prem at moderate scale. For a domain controller and a file server, no — on-prem Windows Server is still the right call.
Q: How do I prove my CAL count to Microsoft in an audit? User CALs are documented by number of unique authenticated identities, not concurrent sessions. Your AD user list with an entitlement mapping is the standard proof. Device CALs are documented by the number of distinct devices that access server services. Keep an updated asset register — that is what auditors want to see.
The next action
If you're within 90 days of a server refresh or a licence renewal, do one thing this week: pull your current Windows Server invoice, list every server you run, its physical core count, and the VM count on each host. Match it against the editions and CAL counts you're paying for. In our experience, about one in three Indian SMEs is either under-licensed (audit risk) or over-licensed (wasted money) by 20% or more.
If you'd rather have someone confirm the math before you sign, send us the spec sheet and the quote — we'll turn it around in two working days. No charge for a licence review.
