An Azure migration cost estimate may cover servers but omit storage, networking, backup, logging, licensing and support charges on the monthly Azure bill. Copying oversized on-premises machines into Azure preserves spare capacity and turns it into recurring expenditure.
The first bill can also include temporary replication and parallel-running costs. Separate these transition charges from the monthly run cost before deciding whether the migration exceeded its budget.
Separate project cost from monthly run cost
What belongs in the migration project?
Project cost covers one-off discovery, design, compatibility work, migration engineering, testing, cutover and handover. It also includes temporary infrastructure and the period when on-premises and Azure systems run in parallel.
A free migration tool doesn’t remove the project cost of this work. Our cloud migration planning approach considers the business requirements around the move, rather than treating data transfer as the whole project.
What remains after cutover?
Run cost covers the resources and services needed to operate the migrated workload. Allow separately for compute, disks, backup, connectivity, monitoring, licences and administration.
Compare that figure with the full on-premises operating cost, including hardware replacement and support. Comparing Azure consumption with an already purchased server understates the existing environment’s cost.
What does Azure Migrate cost?
The tool and replication have different charging rules
Microsoft’s Azure Migrate pricing lists assessment and migration tools for servers, databases and web applications at no additional charge. This covers the tools, not the Azure resources used during assessment or migration. Server migration licensing is free for the first 180 days per machine, then costs US$25 monthly per replicated instance.
Storage, transactions and data transfer used during replication can still incur charges within that period. Third-party migration tools may have separate licence charges.
Azure Migrate is non-regional, so the service isn’t tied to a particular Azure region. Target resources and associated services still have regional pricing and data residency considerations.
Dependency mapping can add monitoring charges
Dependency analysis identifies communication between servers, helping prevent an application being separated from a required database or service.
Agent-based analysis incurs standard Log Analytics charges. Microsoft’s dependency analysis guidance recommends agentless analysis to avoid those workspace charges. Agent-based analysis is confined to the classic experience, which no longer accepts new server onboarding.
Agentless analysis still requires an appliance, access permissions and review. Removing agents doesn’t remove the assessment work.
Why Azure costs after migration exceed the estimate
Oversized machines become recurring expenditure
Right-sizing is normally the largest initial run-cost lever for a lift-and-shift estate. An assessment should use observed CPU, memory, disk and network demand, not simply reproduce existing allocations. Copying those allocations into a virtual machine can turn unused capacity into recurring spend.
Capture month-end processing and relevant seasonal peaks. A quiet week’s utilisation can suggest a smaller machine that fails during payroll or financial reporting.
Low CPU alone doesn’t prove that a server is unnecessary. File services, authentication and recovery systems may remain essential despite limited processing activity.
Supporting services were missing from the quote
A landing zone establishes subscriptions, virtual networks, identity, policies, connectivity, backup vaults, logging and cost alerts. Organising resources doesn’t automatically incur a charge, but deployed VPN gateways, Azure Firewall, backup storage and monitoring can.
VPN or ExpressRoute connectivity may therefore cost money before production servers move. ExpressRoute can also involve separate connectivity-provider charges.
Disks, snapshots and retained backups can remain billable after a test VM disappears. Our guidance on removing unused Azure resources distinguishes discovery candidates from resources that are safe to retire.
Turn assessment findings into a complete estimate
Azure Migrate assessments produce readiness findings, recommended configurations and estimated costs. Transfer the Azure assessment’s sizing recommendations to the Azure Pricing Calculator, then add dependencies that server assessments don’t fully price.
Set the region, GBP currency, agreement, operating hours and licence position consistently. Record whether sizing assumes peak or average demand, and whether resources run continuously. For a UK South deployment, don’t reuse an East US estimate unchanged.
These configurations provide a useful database comparison.
| Cost component | Azure SQL Database | SQL Server on an Azure VM |
|---|---|---|
| Compute | General Purpose, provisioned Gen5, 4 vCores | D4s v3, with Windows and SQL edition specified |
| Storage | 32 GB provisioned database storage | 128 GB Premium SSD, plus required data disks |
| Backup | RA-GRS backup configuration and retention | Backup service, protected capacity and retention |
| Administration | Managed database platform | Guest OS, SQL maintenance and VM management |
This is an IaaS vs PaaS choice: Azure SQL Database is PaaS, while SQL Server on a VM is IaaS. Equal core counts don’t establish equal performance or application compatibility.
Add shared storage, such as 1 TB of Hot block blob storage with locally redundant storage (LRS). Choose storage tiers to match access frequency and retrieval needs. Include transactions and chargeable outbound or cross-region data transfer, particularly for large restores.
The cost estimate must include shared infrastructure and operational support, not merely the database’s compute subtotal. Our IT migration services can help define that wider scope.
Reduce runtime before buying commitments
Scheduling changes usage, not every charge
For 14 development VMs needed for 55 of 168 weekly hours, scheduled deallocation cuts theoretical compute runtime by about 67. Applied to a US$6,000 monthly compute baseline, that equals approximately US$4,036 in theoretical gross compute savings.
This is schedule arithmetic, not a UK tariff or guaranteed saving. Dependencies, exceptions and existing commitments change the result.
Stopping Windows inside a VM can leave compute allocated and billed. The required state is Stopped (Deallocated). Disks, snapshots and backups remain chargeable.
Reservations and savings plans need stable demand
Microsoft advertises Reserved VM Instance savings of 36% to 72% against pay-as-you-go over 1-year or 3-year terms. A savings plan for compute advertises 11% to 65% savings based on an hourly spending commitment.
The highest examples use large Linux VMs over 3 years in East US. They are not forecasts for smaller Windows servers.
Right-size and remove unnecessary runtime first. Purchasing a commitment against an oversized estate can preserve avoidable expenditure.
Review licences and end-of-support costs separately
Existing licences can reduce the run cost
Azure Hybrid Benefit allows eligible Windows Server and SQL Server core licences with active Software Assurance to reduce Azure licensing charges. Qualifying subscription licences can also be eligible.
Microsoft provides a 180-day migration allowance for parallel on-premises and Azure use. This allowance concerns licensing rights, not free Azure compute.
Document editions, eligible core quantities and ongoing on-premises use before applying the benefit. Moving a workload does not automatically establish licence eligibility.
Moving an unsupported server does not upgrade it
Migration does not change a product’s end of support date or upgrade an unsupported server. Windows Server 2016 extended support ends on 12 January 2027. SQL Server 2016 extended support ended on 14 July 2026, and Windows Server 2012 and 2012 R2 Extended Security Updates ended on 13 October 2026.
SQL Server 2016 on Azure VMs no longer receives free Extended Security Updates (ESUs). Microsoft’s SQL Server ESU guidance describes paid coverage; Azure subscription usage is reported hourly.
Include that charge when comparing continued VM operation with upgrading or moving to a compatible managed database. ESUs provide defined security updates, not a replacement for an upgrade plan.
Review the first full bill against the design
Open Cost Analysis in Azure Cost Management and select the billing period and scope. Group or filter charges by service and resource, then compare actual spend with the approved estimate.
Separate temporary migration resources from the steady-state environment. Investigate price differences and unexpected consumption. For charges that need further investigation, check cost exports or the underlying billing data. Azure Copilot can help where available, but verify its output against Cost Analysis or billing data.
Use These Cost-Driver Checks:
- Identify oversized compute, continuously running development systems and resources without an accountable owner.
- Review disks, snapshots, backup retention, log ingestion and retained Azure Migrate infrastructure.
- Compare data-transfer charges with application traffic, cross-region replication and recovery requirements.
- Assign budget alerts to named owners and document the action expected when thresholds are exceeded.
Budget alerts notify owners, but they don’t normally stop expenditure. A dashboard without an owner doesn’t retire resources.
Support is another recurring line. Microsoft’s Azure support plans list Developer at US$29 monthly, Standard at US$100 and Professional Direct at US$1,000. Basic excludes technical support; Developer is intended for non-production use.
These are published USD prices, not GBP quotations. Microsoft platform support doesn’t replace day-to-day administration, application troubleshooting or recovery management.
Key takeaways
Azure costs after migration become easier to explain when the estimate separates temporary transition work, steady-state consumption and ongoing management. A technically successful cutover does not establish that the environment is commercially proportionate.
Prioritise observed sizing, operating hours, eligible licences and retained resources before committing to discounts. Include backup, connectivity, monitoring and support in the same financial baseline.
Frequently asked questions
Is an Azure assessment free?
Microsoft’s Azure Migrate assessment tools have no additional service charge. Discovery appliances, associated services and professional assessment work can still cost money. The output supports readiness and sizing decisions; it does not replace a complete project or operating budget.
How much does a small business Azure migration cost?
There is no defensible fixed price based only on employee or server count. Application compatibility, data volume, downtime limits, networking, security and recovery requirements determine the project scope. Request separate project and monthly operating totals, with assumptions recorded.
Is Azure SQL Database cheaper than SQL Server on a VM?
Either can cost less, depending on workload size, licensing, runtime and operational requirements. Compare the complete service, including backup and administration. A lower VM compute subtotal does not establish a lower database operating cost.
Establish a run-cost baseline with clear ownership
A useful Azure budget connects each material charge to a required workload, an accountable owner and a documented operating assumption. Review exceptions after cutover rather than accepting the first invoice as the permanent baseline.
Speak to our team about Azure consultancy and support to review sizing, licensing, retained resources and ongoing management together. We can help identify what to resize, what to retire and what needs continued support.
