India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
Azure Virtual Machines, Scale Sets & Compute Cost Optimization
Azure compute is Microsoft's infrastructure-as-a-service layer: Virtual Machines, Virtual Machine Scale Sets and Azure Virtual Desktop running Windows or Linux in Azure regions such as Central India (Pune). NTSPL migrates Windows Server and SQL Server estates for Indian mid-market firms, sizes VM families against measured load, and stacks Azure Hybrid Benefit, Savings Plans and Spot VMs to bring the monthly compute bill down.
Microsoft Azure services in scope
The Problem Azure Virtual Machines and Azure Virtual Machine Scale Sets (Flexible orchestration) Solve
Most Indian mid-market server estates are Windows-heavy: Windows Server 2012 R2 to 2019 hosts running Tally, SQL Server-backed line-of-business apps, dispatch consoles and file servers, bought on a five-year refresh cycle and sized for the worst month of the year. Moving them to Azure as-is reproduces that oversizing at pay-as-you-go rates, and the bill shocks finance in month two. The real compute problem is threefold: matching VM families to measured CPU, memory and IOPS profiles, deciding which tiers can scale horizontally in a Scale Set, and getting the Windows and SQL Server licences already paid for counted against Azure.
NTSPL starts with Azure Migrate dependency mapping and at least 30 days of performance data per server, then classifies every workload as baseline, burst or interruptible. Baseline VMs get a 1- or 3-year commitment, burst tiers move into Flexible-orchestration Scale Sets with metric-based autoscale, and batch or render jobs go to Spot. Licences with active Software Assurance are applied through Azure Hybrid Benefit from day one, and remaining Windows Server 2012 hosts, whose Extended Security Updates ended on 13 October 2026, are prioritized for OS upgrade or replacement before or during migration.
When Azure VMs and Scale Sets Are the Right Compute (and When App Service or AKS Is Better)
Signals that point to compute & scale on Microsoft Azure
- A hardware refresh quote for on-premises Hyper-V or VMware hosts has arrived and exceeds what 36 months of right-sized Azure compute would cost.
- Windows Server 2012 or 2012 R2 hosts are still in production and the business has not completed application upgrades even though Extended Security Updates for them ended in October 2026.
- Peak CPU on web or application servers exceeds 80 percent for a few days a month (filing deadlines, month-end, sale events) and sits under 15 percent otherwise.
- Staff use RDP over a public IP or a consumer VPN to reach a Windows desktop application from home or client sites.
- The organization owns SQL Server or Windows Server licences with Software Assurance that are not being used against any cloud workload today.
When a different approach is better
- Web apps written in .NET, Java, Node.js or PHP that the team controls and can redeploy: Azure App Service removes OS patching and gives deployment slots, so a VM adds operational load without benefit.
- Microservices already packaged as containers with more than 10 services: Azure Kubernetes Service or Azure Container Apps bin-packs them more efficiently than one VM per service.
- Event-driven jobs that run for seconds and sit idle most of the day: Azure Functions on the Flex Consumption plan bills only for execution and avoids an always-on VM.
Azure Compute Building Blocks: VM Series, Flexible Scale Sets, Spot and Virtual Desktop
| Service | Role in the architecture | Choose it when |
|---|---|---|
| Azure Virtual Machines | Runs Windows Server and Linux guests on general-purpose (D-series), memory-optimized (E-series), compute-optimized (F-series) and burstable (B-series) sizes with Premium SSD or Premium SSD v2 disks. | An application is stateful, single-instance or licensed per host and cannot be rebuilt from an image without vendor involvement. |
| Azure Virtual Machine Scale Sets (Flexible orchestration) | Manages a pool of identical or mixed-size VMs spread across availability zones and fault domains, with autoscale rules on host metrics or a schedule. | A web, API or worker tier is stateless or keeps state externally and its load varies by more than 2x between quiet and peak hours. |
| Azure Hybrid Benefit | Applies existing Windows Server and SQL Server core licences with Software Assurance (or qualifying subscriptions) to Azure VMs so only the base compute rate is billed. | The organization holds Windows Server Datacenter or Standard, or SQL Server Enterprise or Standard, licences with active Software Assurance. |
| Azure Reservations and Azure Savings Plan for compute | Commit to a specific VM size and region (Reserved VM Instances) or to an hourly spend across families and regions (Savings Plan) for 1 or 3 years in exchange for a lower rate. | A VM has run above roughly 70 percent of the month for three consecutive months and its size is not expected to change. |
| Azure Spot Virtual Machines | Uses spare Azure capacity at a deep discount, with eviction on 30 seconds' notice when Azure needs the capacity back or the price exceeds the set maximum. | The job is checkpointed or restartable: report generation, rendering, CI build agents, simulation or test environments. |
| Azure Virtual Desktop | Delivers Windows 11 Enterprise multi-session desktops or published RemoteApps from host pools in an Azure region, with FSLogix profile containers on Azure Files. | Users need a Windows-only desktop application from home, client sites or branch offices without data leaving the firm's tenant. |
Zone-spread Windows application estate in Central India
Zone-spread Windows application estate in Central India
Users reach published apps through Azure Virtual Desktop or an Application Gateway, which forwards to a Flexible-orchestration Scale Set spread across three availability zones in Central India. The application tier writes to a SQL Server VM pair on Premium SSD v2, while Azure Backup and Azure Site Recovery replicate the estate to South India.
Select any component
Zone-spread Windows application estate in Central India: click any of its 8 components to see its role and the design choice NTSPL makes for it, or trace the 5-step primary path.
Azure VM Engineering Decisions: Sizing, Zones, Commitments and Hybrid Benefit
VM family and generation selection
Start from measured P95 CPU and memory, not the on-premises spec sheet. A host with 16 vCPU and 64 GB that peaks at 30 percent CPU and 40 GB is usually a D8s v5 or D8as v5, not a D16. Use E-series only when memory-to-core demand exceeds 6 GB per vCPU, typical for SQL Server. Keep B-series for domain controllers, jump hosts and utilities, never for SQL or IIS tiers where CPU credits run out at month-end. Prefer current generations; older series cost more per unit of work.
Single VM, availability set or Scale Set
A single VM with Premium SSD disks carries a 99.9 percent SLA; two or more instances across availability zones carry 99.99 percent. Legacy apps that hold session state in memory go into a two-node zone-spread pair behind a load balancer with session affinity. Anything stateless goes into a Flexible-orchestration Scale Set, which allows mixed sizes and manual VM additions, unlike Uniform mode. Availability sets are now reserved for regions or SKUs without zone support.
Commitment mix: Reservations, Savings Plan and pay-as-you-go
Commit only after 60-90 days of run data. Reserve the SQL Server and domain controller VMs whose size and region will not change for three years; use a Savings Plan for compute to cover the application tier, which may change family during upgrades. Leave Scale Set burst capacity and anything under 50 percent monthly uptime on pay-as-you-go. NTSPL typically targets 70-85 percent of steady-state compute hours under some commitment, reviewed every quarter.
Licence position and Hybrid Benefit
Inventory Windows Server and SQL Server licences, edition and Software Assurance status before sizing. Windows Server Datacenter with SA can cover more cores in Azure than Standard; SQL Server Enterprise with SA maps to more vCores than Standard. SQL Server workloads that run only in a passive DR replica may qualify for free passive failover rights under SA. Where licences lack SA, compare the pay-as-you-go licence rate with buying new subscriptions through CSP before deciding.
Region and zone placement within India
Central India (Pune) supports availability zones and is NTSPL's default primary for production. South India (Chennai) is its paired region and the usual DR target; West India (Mumbai) is used when an application needs proximity to Mumbai-based exchanges or partner data centres. Check SKU availability per region before finalizing, because newer VM series and GPU sizes do not always land in every Indian region (Central, South, West and the newer India South Central in Hyderabad) at the same time.
How NTSPL Migrates a Windows Server Estate onto Azure VMs and Scale Sets
Azure Migrate performance capture
Deploy the Azure Migrate appliance against Hyper-V or VMware for at least 30 days to collect P95 CPU, memory, disk IOPS and dependency maps per server.
Licence and commitment baseline
Reconcile Windows Server and SQL Server cores with Software Assurance, then model each VM at pay-as-you-go, Hybrid Benefit and Reservation rates in INR.
Golden image and Compute Gallery
Build hardened Windows Server 2022/2025 and Linux images with Azure Image Builder, version them in Azure Compute Gallery and replicate to Central and South India.
Zone-spread Scale Set and stateful VM build
Deploy stateless tiers into Flexible-orchestration Scale Sets across zones with autoscale profiles, and stateful SQL or licence-bound servers as zone-separated pairs on Premium SSD v2.
Replication and wave cutover
Replicate servers with Azure Migrate in dependency-grouped waves, run test migrations into an isolated VNet, then cut over each wave in a weekend window.
Site Recovery, patching and commitment purchase
Enable Azure Site Recovery to South India, attach Azure Update Manager maintenance configurations, and buy Reservations or a Savings Plan after 60-90 days of run data.
What you receive
Hardening Azure VMs: Trusted Launch, Encryption at Host, Bastion and Just-in-Time Access
On Azure VMs the customer owns the guest OS, so the main risks are exposed RDP and SSH ports, unpatched Windows images and disks readable outside the VM. NTSPL removes all public IPs from workload VMs, brokers admin access through Azure Bastion and just-in-time access, enforces encryption at host, and uses Trusted Launch so the boot chain is measured before the guest runs.
- Trusted Launch with Secure Boot and vTPM on Generation 2 VMs, to block bootkits and rootkits
- Encryption at host for OS, data and temp disks, so cached data on the host is also encrypted
- Just-in-time VM access in Defender for Servers, so RDP and SSH open only for an approved window and source IP
- Azure Bastion as the only path for interactive admin sessions, removing public RDP exposure
- Azure Policy guest configuration to audit local administrators, password policy and TLS settings inside Windows guests
Azure Compute Pricing Levers: Hybrid Benefit, Reservations, Savings Plan and Spot
Azure compute is billed per second of VM runtime by size, plus separately billed managed disks, outbound data and, where not covered by Hybrid Benefit, the Windows or SQL Server licence. A deallocated VM stops compute charges but disks continue to bill. For a typical Windows estate, licence charges can be a large share of the VM rate, so licence position often matters as much as size.
- Azure Hybrid Benefit on every eligible Windows Server and SQL Server VM, verified monthly in Cost Management
- 3-year Reserved VM Instances for SQL and infrastructure VMs; Savings Plan for compute for the application tier
- Auto-shutdown and Azure Virtual Desktop scaling plans to deallocate non-production and desktop hosts outside working hours
- Spot VMs for overnight batch, render and CI agents with a capped maximum price
- Premium SSD v2 with IOPS and throughput provisioned separately, instead of oversizing Premium SSD capacity to buy performance
Azure Reserved VM Instances vs Azure Savings Plan for compute: which should I buy?
Decide on four criteria. Flexibility: a Savings Plan applies an hourly spend commitment across VM families, sizes and regions, while a Reservation is tied to a size family and region, with instance size flexibility within that family. Discount depth: Reservations generally give a deeper discount for the same term on a VM that never changes. Change horizon: if you expect to move from D-series v4 to v5, consolidate servers or shift some load to App Service or AKS, the Savings Plan absorbs that; a Reservation has to be exchanged. Coverage of other services: a Savings Plan also applies to eligible App Service Premium plans and Container Apps dedicated compute. NTSPL's rule: Reservations for fixed SQL and infrastructure VMs, Savings Plan for everything else that runs steadily, pay-as-you-go for burst.
Key facts about compute & scale on Microsoft Azure
Compute & Scale on Microsoft Azure in Practice
3 compute & scale scenarios from Chartered accountancy & audit, Healthcare diagnostics, Mining: the starting position, the services chosen, the architecture, the rollout and the measured outcome.
Audit firm moves 22 Windows servers to Azure and serves 180 staff via Virtual Desktop
Diagnostics chain runs its Windows LIS on zone-spread Azure VMs with sub-second lookups
Mining operator cuts dispatch-server spend 41% with Savings Plan and Spot simulation runs
Pharma manufacturer connects 4 GxP plants to Azure with validated network-as-code
Compute & Scale on Microsoft Azure: Frequently Asked Questions
How much can Azure Hybrid Benefit save on a Windows Server VM?
For Windows Server VMs, Hybrid Benefit removes the Windows licence component, so you pay roughly the Linux rate for the same size. For SQL Server VMs the saving is larger because the SQL Server licence is also removed. The exact percentage depends on VM size and region. NTSPL produces a per-VM comparison in INR from the Azure pricing calculator before migration so finance sees the effect line by line.
Can we move our on-premises Hyper-V or VMware servers to Azure without rebuilding them?
Yes. Azure Migrate discovers Hyper-V and VMware VMs, assesses them against Azure sizes using performance data, and replicates them to Azure with agentless or agent-based replication. Cutover is a short outage while the final delta syncs. NTSPL groups servers into waves by dependency map, so the database and the application servers that call it move together over one weekend.
Which Azure region in India should host our VMs?
For most production workloads NTSPL uses Central India in Pune because it supports availability zones, with South India in Chennai as the paired disaster-recovery region. West India in Mumbai suits workloads that need proximity to Mumbai-based partners. Keeping both primary and DR copies in Indian regions also simplifies data-residency commitments to customers, auditors and regulators.
What happens to our Windows Server 2012 R2 servers in Azure?
They no longer receive security updates: Extended Security Updates for Windows Server 2012 and 2012 R2, which Azure provided at no extra charge, ended on 13 October 2026, on Azure and on-premises alike. NTSPL therefore treats every 2012 workload as an upgrade-first item: each gets an upgrade or replacement date in the migration plan, it is isolated by network rules until then, and in-place OS upgrade is tested on a cloned VM first.
Are Spot VMs safe to use for production work?
Only for work that tolerates interruption. Azure can evict a Spot VM with 30 seconds' notice, so it suits batch reports, rendering, CI agents and test environments, not a database or an interactive app server. NTSPL designs jobs to checkpoint progress to storage and spreads Spot requests across several VM sizes inside a Scale Set to reduce eviction impact.
Is Azure Virtual Desktop cheaper than giving every user a laptop with the app installed?
It often is when the application is heavy, data-sensitive or needs a nearby SQL Server. Windows 11 Enterprise multi-session lets several users share one host, and eligible Microsoft 365 licences include the AVD access rights, so you pay mainly for host VMs and storage. Scaling plans that shut hosts down after hours typically decide whether the business case works.