298 servers. A hardware refresh due in 18 months. A cloud business case nobody trusted.
The Azure Migrate output looked professional. The problem was not the tool. The problem was the assumptions.
Azure Migrate can discover servers, collect performance data, estimate Azure sizing, and model TCO. But it cannot read your colocation contract, SAN support renewal, VMware quote, Microsoft EA, or fully burdened FTE cost.
That gap is where many migration business cases fail.
This article shows how platform leaders turn Azure Migrate from a directional estimate into a CFO-ready business case.
Executive Impact Summary
The $0 Assumption Problem
The CFO asked one question.
"Where did these on-premises numbers come from?"
The silence lasted four seconds. The meeting ended in four minutes.
Here is the reality that shapes every migration business case: Azure Migrate estimates your on-premises costs using discovery data, performance signals, pricing logic, and default assumptions. When the platform generates its initial business case, it fills the On-Premises Cost section with Microsoft's researched industry benchmarks — averages derived from thousands of enterprise environments.
The tool is working exactly as designed. Azure Migrate cannot automatically know your colocation contract, hardware refresh timeline, VMware renewal quote, SAN or NAS support cost, Microsoft EA or MCA terms, Software Assurance status, SQL licensing ownership, internal FTE cost, or managed service spend. That information lives in procurement systems, vendor invoices, and HR records — not in the hypervisor metadata the appliance can read.
The gap between benchmark and reality is not a flaw in the tool. The flaw is presenting those unvalidated averages to a financial decision-maker as if they are your client's actual numbers. A CFO or procurement lead will identify a generic benchmark in thirty seconds. When they do, the entire migration programme loses credibility — not just the spreadsheet.
The fix is a structured discovery process that replaces every Microsoft assumption with a real contract figure, a real utility bill, or a real headcount number. Platform leaders make those estimates defensible. This article gives you the exact framework to do it.
The Generic Estimate
Microsoft assumes your PUE is 1.80, your storage costs $2/GB, and your admins earn $100k. Directionally correct for a market average. Fatally wrong when presented as your business's reality to a CFO who knows the lease rate on your colo facility.
The Customized PoE
Your actual rack lease at ₹4.2L/month. Your real SAN support contract at $180k/year. Your seven infrastructure FTEs fully burdened at $95k each. These numbers are auditable. A CFO can sign off on auditable numbers.
The CapEx Cliff: Why "Stay On-Premises" Is Never Free
Before you walk into a CFO meeting, make sure the financial framing is right.
On-premises infrastructure does not sit still. Physical servers run on a 3-to-5-year hardware refresh cycle. Once a server exits that window, three cost events trigger simultaneously:
- Support Escalation: OEM warranties expire. Post-warranty maintenance contracts spike — often 2x to 4x the original support cost.
- Operational Risk: Mechanical failure rates climb the reliability bathtub curve. Unexpected downtime carries real revenue impact: a one-hour outage for a mid-size bank is routinely modelled at $250k–$1M in lost transactions.
- Performance Degradation: 5-year-old silicon cannot run modern containerized workloads or GPU-accelerated analytics at acceptable cost-per-compute ratios.
Staying on-premises is not the zero-cost option. It is a deferred CapEx bomb.
[ Year 1–3: Hardware Stable ] ──► [ Year 4–5: Warranty Expires / Risk Spikes ]
──► 💥 [ CapEx Cliff: Massive Hardware Refresh Invoice ]
Azure flips the model. You trade an unpredictable, spike-heavy capital outlay for a predictable monthly OpEx utility. That framing — CapEx elimination — is often worth more to a CFO than the raw TCO reduction percentage.
End-of-Life Workloads: The Hidden Migration Accelerator
Organisations running Windows Server 2012/2012 R2 or SQL Server 2012 — both past Microsoft end-of-support — face compounding cost exposure. Windows Server 2012 / 2012 R2 ESUs may be available at no additional charge for eligible servers hosted in Azure during the applicable ESU period, while non-Azure servers usually require purchased ESU coverage that escalates annually. Validate eligibility, current dates, and terms against current Microsoft guidance before using this as a business case input. For in-scope estates, this single line item frequently closes a business case that was otherwise borderline.
2024–2026: The VMware/Broadcom Licensing Catalyst
Since Broadcom's VMware licensing changes, many enterprises have faced renewal pressure due to subscription packaging, bundling, and changed commercial terms. Do not assume the current VMware run cost reflects the upcoming renewal. Ask procurement for the latest renewal quote and use that actual figure in the business case. If the VMware renewal cost is significant, this single line item — captured in Q9 of the discovery checklist — may exceed the entire Azure cost reduction, making the migration self-funding before Azure Hybrid Benefit or Reserved Instances are even applied. If your client runs VMware, quantify the Broadcom renewal cost first.
Safe, Low-Impact Discovery: How Azure Migrate Collects Data
The first objection from IT infrastructure teams is always the same: "Will this assessment touch our production systems?"
Azure Migrate discovery is designed to be low-impact and agentless. The appliance does not install software inside discovered servers. However, credentials, firewall rules, dependency discovery, and security approval still need to be planned carefully before deployment. Here is how the data collection works:
Lightweight Agentless Appliance
A single VM deployed inside your VMware vSphere or Hyper-V environment. No software installed inside production guest OS instances.
Read-Only Management Privileges
The appliance operates strictly read-only. It cannot modify configuration, deploy agents, or alter network state. CISO-safe by design.
Continuous Performance Sampling and 10-Minute Aggregation
For VMware and Hyper-V assessments, Azure Migrate collects performance samples, aggregates them into 10-minute data points, and uses the selected performance history, percentile, comfort factor, and pricing assumptions to recommend Azure sizing. This eliminates spike-day distortion from the right-sizing model.
Right-Sizing from Real Utilisation
Actual utilisation data — not provisioned capacity — drives the Azure SKU recommendation. Most enterprises discover 20–40% of workloads can run safely on smaller, cheaper cloud instances.
The 11-Question Discovery Checklist
These are the questions you need answered before you touch the Azure Migrate cost configuration panel. Assign each to the right internal stakeholder. Missing even one pillar will leave a hole that the CFO's team will find.
Pillar 1: Compute & Facilities
Target: Infrastructure & Facilities Leads. Microsoft defaults: PUE 1.80, standard linear depreciation on x86 hardware. At PUE 1.80, 44% of total facility power is consumed by cooling overhead — not computing.
Hardware Age & Refresh Timeline
What is the average age of servers hosting target workloads, and when is the next major hardware refresh expected?
Maps to: Compute CapEx & Depreciation Timeline
CapEx vs. Colocation Model
Are servers owned outright (CapEx) or leased/collocated (OpEx)?
Maps to: Compute Acquisition Model Type
Colo Contract Terms
If using colocation, what is the remaining contract duration and annual cost per rack or per square foot?
Maps to: Facilities Real Estate & Rack Rental
Power & Cooling Cost
What is the monthly utility cost (power + HVAC) allocated specifically to the data centre or server rooms?
Maps to: Facilities Power Consumption & PUE
Pillar 2: Storage & Data Management
Target: Storage & Backup Admins. Microsoft defaults: $2.00/GB acquisition, 10% annual maintenance of raw hardware value.
SAN/NAS Capacity & Age
What is the total raw capacity (GB/TB) and age of the current SAN or NAS infrastructure?
Maps to: Storage CapEx
Storage Vendor Support Contracts
What is the annual maintenance and support contract cost paid to storage vendors (Dell EMC, NetApp, Pure Storage, etc.)?
Maps to: Storage Maintenance & Support OpEx
Backup & DR Infrastructure
What are the hardware, licensing, and secondary-site costs for your current backup and disaster recovery footprint?
Maps to: Storage Backup & DR Infrastructure
Pillar 3: Software Licensing & Agreements
Target: Procurement & ITAM Teams. Microsoft defaults: standard retail PAYG pricing for Windows Server and SQL Server.
Enterprise Agreement & Software Assurance
Do you hold an active Microsoft EA with Software Assurance that qualifies for Azure Hybrid Benefit?
Maps to: Licensing OS & DB Optimisation (AHB)
Virtualisation Layer Licensing
What are the annual licensing and support costs for VMware vSphere, vCloud Foundation, or Red Hat Enterprise Linux?
Maps to: Licensing Hypervisor / Virtualisation Software
Pillar 4: IT Labour & Operations
Target: IT Director & HR Finance. Microsoft defaults: $100,000/year administrator salary (geography-adjusted) with a fixed server-to-admin ratio.
Fully Burdened IT Labour Cost
What is the fully burdened cost (salary + benefits + overhead) per IT administrator, and how many FTEs are dedicated to physical infrastructure maintenance (racking, patching, hardware troubleshooting)?
Maps to: Labour IT Administrator Salary & Resource Density
MSP & External Consultant Spend
What is the average annual spend on third-party managed service providers or external consultants supporting on-premises infrastructure?
Maps to: Labour Outsourced Operational Expenses
Take this checklist to your team
Assign each question to the right stakeholder before your first Azure Migrate session.
Once all 11 answers are in hand, you override the Azure Migrate cost properties panel with real figures. The tool will recalculate the entire financial model.
How to Override Cost Properties in the Azure Migrate Portal
- In the Azure Portal, navigate to Azure Migrate → Servers, databases and web apps
- Select your project, then click Business case in the left menu (this is a separate tab from the Assessment view)
- Open your business case and locate the assumptions or cost settings panel — typically accessible from the top action bar (labelled Edit assumptions or Assumptions depending on your portal version)
- Under On-premises infrastructure: update the facility cost (power + cooling per kWh), storage cost per GB, and the IT labour rate and server-to-admin ratio using your discovery data
- Under Azure settings: toggle on Azure Hybrid Benefit and confirm coverage scope (Windows Server, SQL Server, or both)
- Set your Reserved Instance term preference — 1-year or 3-year — for the compute right-sizing model
- Click Save & recalculate — the TCO comparison updates immediately across all five cost pillars
Note: If you only see right-sizing recommendations, you are in the Assessment view. Navigate back to the project overview and select Business Case — it is a distinct workflow within Azure Migrate.
Note: Azure Migrate Business Case capabilities and portal labels may evolve. Always validate the current export, assumptions, and pricing model before using the output for formal investment approval.
The Three Financial Superchargers
Replacing the defaults gets you an honest baseline. These three mechanisms dramatically improve the Azure side of the equation — and they stack.
Azure Hybrid Benefit (AHB)
Reuse existing EA licences in Azure — Windows and SQL licence fee drops to zero.
- ✓EA + Software Assurance licence brought to Azure as a pre-paid coupon
- ✓Covers both Windows Server and SQL Server licences
- ✓Datacenter edition: run on-prem and Azure simultaneously — zero OS cost during migration
Who qualifies
Any enterprise with an active Microsoft EA and Software Assurance on Windows Server or SQL Server. Windows Server Datacenter edition achieves the full 49% saving. Standard edition saves up to 40%.
SQL Server 1:4 Enterprise Multiplier
One on-premises SQL Enterprise core buys four Azure SQL vCores.
- ✓Applies to SQL Server Enterprise Edition (core-based licensing only)
- ✓Targets Azure SQL Managed Instance or General Purpose tier
- ✓Potentially reduce SQL licence renewal scope, subject to licence ownership, Software Assurance terms, retained on-premises usage, and procurement approval
Real example
Need 40 vCores in Azure SQL? Bring 10 SQL Enterprise cores from on-prem. Potentially reduce the remaining 30 cores from future SA renewal scope, subject to actual licence ownership, SA terms, and procurement approval.
⚠ This ratio applies to Azure SQL Managed Instance or SQL Database (General Purpose tier) only. SQL Server on Azure VMs uses standard AHB core-for-core — not this multiplier. Business Critical tiers, SQL Standard edition, and retained on-premises usage follow different rules.
Azure Reserved Instances (RIs)
Commit to 1- or 3-year terms on predictable workloads — stacks directly on top of AHUB.
- ✓1-year RI: up to 37% saving vs PAYG compute rate (Microsoft published)
- ✓3-year RI: up to 57% saving vs PAYG compute rate (Microsoft published)
- ✓AHUB + RI apply simultaneously on the same VM — effects fully stack
The boardroom number
AHB removes the licence cost (up to 49% for Datacenter edition with active SA). A 3-year RI then cuts the remaining compute rate by up to 57%. On Windows Server Datacenter estates, this combination can reach 75–80% total saving versus PAYG — validate eligibility before presenting this figure.
[ 1 On-Premises SQL Enterprise Core ] ──► Unlocks ──► [ 4 Azure SQL vCores ]
The CFO Presentation Blueprint
Once the data is in and the superchargers are applied, synthesise the output into this comparison framework. Do not present Azure Migrate's raw output. Translate it.
Numbers below are representative of a 300-server enterprise estate. Your discovery replaces these with client-specific inputs — the structure stays identical.
| Cost Pillar | On-Premises (As-Is) | Azure (To-Be) | How We Win |
|---|---|---|---|
| Compute / Virtualisation | $1.90M | $1.05M | AHB — up to 49% off (Datacenter edition, SA required) |
| Database Licensing | $720K | $215K | SQL 1:4 multiplier — retire 75% of licence estate |
| Storage & Backup | $540K | $160K | Azure Archive — ~70% below on-prem tape cost |
| Facilities & Power | $440K | $0 | Physical footprint gone — no lease, no power bill, no refresh CapEx |
| IT Labour & Operations | $620K | $310K | FTE hours — redirected from patching to product |
| Total Annual Cost | $4.22M | $1.74M | Net Saving: $2.48M (59%) |
This is the slide that closes the CFO meeting — not reopens it.
Assumptions CFOs Will Ask For
The Azure Migrate Business Case covers five cost pillars. A CFO-grade investment case typically interrogates seventeen. Have a defensible figure — or a documented assumption — for each of these before the presentation.
- Migration timeline and wave plan — what migrates when, and what the transition overlap cost looks like
- Year-over-year infrastructure growth rate — flat, growing at 5%, or shrinking post-migration
- WACC / discount rate — required for NPV and 3-year payback modelling
- Hardware refresh avoidance — the CapEx that disappears if you migrate before the next refresh cycle
- Network cost — ExpressRoute, VPN, data transfer, and egress charges to and from Azure
- Storage and backup cost — Azure Blob, Archive, and backup vault at projected retention volumes
- Security and management cost — Defender for Cloud, Microsoft Sentinel, Azure Monitor, and patch management overhead
- Azure support plan, CSP margin, or managed service cost — frequently omitted from the To-Be column entirely
- Log Analytics ingestion and retention cost — underestimated in most first-pass models
- Landing zone shared services cost — hub networking, DNS, monitoring, firewall, and governance at scale
- Reserved Instances or Savings Plan assumptions — which workloads are committed, which remain PAYG, and the commitment risk if scope changes post-migration
- Azure Hybrid Benefit eligibility — Software Assurance status and licence scope confirmed by ITAM, not assumed
- SQL licensing and Software Assurance status — Enterprise or Standard edition, core count, SA expiry dates, and retained on-premises usage
- VMware / hypervisor renewal cost — the actual procurement renewal quote, not the current run rate
- On-premises facilities, power, cooling, rack, and datacentre cost — full contract values, not PUE benchmark estimates
- People cost and operational support model — who runs the Azure environment post-migration and at what fully burdened cost
Missing even one of these in the CFO meeting signals that the model was built by the technology team, not by someone who has delivered a migration programme before.
Ready to build your business case?
I help platform leaders structure Azure business cases that pass CFO review first time.
The Bottom Line
A regional bank with 298 servers and a hardware refresh due in 18 months walked into their first CFO presentation with Azure Migrate's default output. The CFO's team identified three assumptions inside four minutes — a PUE of 1.80 that didn't reflect their actual data centre efficiency, a $100k admin salary that bore no relation to their London FTE costs, and a $2/GB storage figure that was a fraction of their NetApp support contract. The meeting ended before slide three. The programme was placed on hold.
Two weeks later, the discovery sprint was complete. Their City data centre rack contract came in at $235k per year. Seven infrastructure FTEs were fully burdened at $112k each — $784k in annual labour, not the $700k Microsoft had assumed. Their NetApp support renewal was $220k per year — nearly four times the default $2/GB estimate. The Azure Migrate cost properties were overwritten with these real figures. AHB was applied across the Windows Server Datacenter estate. The SQL 1:4 multiplier reduced the on-premises SQL Enterprise renewal scope by 30 cores, subject to licence confirmation with procurement.
The resubmitted business case cleared the CFO review in 40 minutes. A $2.3M migration programme was signed the following month. Not because the technology changed — because the numbers were real and every figure in the comparison table could be traced back to an invoice.
Azure Migrate is not producing inaccurate output because it is poorly engineered. It is estimating from benchmarks because it has no way to read your client's contracts. Your job as the platform leader driving the business case is to close that information gap before the presentation — not during it.
Run the 11-question discovery sprint. Replace the defaults. Apply AHB and the SQL multiplier where eligibility is confirmed. Present real, validated numbers in the CFO comparison table.
That is how a generic assessment becomes a signed migration programme.
Upendra Kumar
Cloud Solution Architect · Azure Migration · FinOps · Pre-Sales
I design and deliver Azure migration business cases for enterprise programmes across banking, insurance, healthcare, and regulated public sector. My focus is turning Azure Migrate assessments into CFO-approved investment decisions — using real discovery data, structured financial models, and the cost optimisation mechanisms that reduce on-premises TCO by 40–80%.
Ready to turn your assessment into a signed migration programme?
Whether you are building your first business case or validating an existing one, the framework above applies across regulated industries — banking, insurance, healthcare, and public sector alike.