Azure migration licensing is where the cost case for an Azure move silently degrades. The Azure Migrate tooling tells you what to move and at what Azure SKU it will land. It does not tell you which on-premises licences come with you, which ones expire on migration, which third-party stacks lose their licensing model entirely, or how the Software Assurance (SA) clock interacts with Azure Hybrid Benefit (AHB) capture. Done wrong, a "cost-saving" migration ends up paying twice: once for the original on-prem licences (still under SA) and once for full Azure list pricing because AHB was not claimed. The five decisions that protect the cost case: AHB eligibility audit before lift-and-shift, dual-use rights timing across the cutover window, SQL Server Edition step-up decisions, third-party ISV licensing reassessment, and EA-to-Azure consumption accounting through the True-Up cycle.
Why azure migration licensing decides the cost case
Microsoft's standard migration cost model assumes you bring no on-prem licences with you and pay Azure rack rate. That is the worst-case number. In reality, most enterprises hold Windows Server and SQL Server entitlements under EA + Software Assurance (SA), which qualify for Azure Hybrid Benefit: bring your existing core licences to Azure VMs and pay the base compute rate only, saving 40–75% on Windows VM hours and up to 85% on SQL Server VMs. The number whether you save 25% or 65% on Azure consumption hinges on whether the AHB application is filed correctly per VM, per subscription, before the meter ticks.
The Microsoft account team will mention AHB once. The Azure portal default does not apply AHB; you must mark each VM as "Yes" for hybrid benefit at provisioning, or run a remediation script after the fact. We routinely find tenants where 30–60% of eligible VMs are paying the non-AHB rate because the migration runbook never included the AHB checklist.
Azure Hybrid Benefit eligibility audit
AHB applies to Windows Server Standard / Datacenter and SQL Server Standard / Enterprise core licences with active Software Assurance (or qualifying subscription licences). Before any migration, do the audit:
- Inventory every Windows Server and SQL Server core licence on the SCE / EA contract. Confirm SA active and end-date.
- Map each on-prem workload to its Azure target VM family and core count.
- Reconcile total Azure cores needed vs. on-prem cores held with SA. Each on-prem Standard core = 1 Azure core under AHB; each Datacenter core = up to 2 Azure cores under AHB on the same VM (one for on-prem, one for Azure, during dual-use period).
- Dual-use rights: SA holders get 180 days of dual use during migration — on-prem and Azure running simultaneously on the same licence. Plan the cutover inside that window or you lose half the benefit.
Microsoft has no incentive to remind you that AHB applies retroactively only with documentation and only within 180 days of dual-use. Each VM that runs in Azure at the non-AHB rate is a margin win. The "pay-as-you-go with AHB toggle" UI defaults are biased against the customer. Always run the post-migration AHB compliance scan within 30 days of cutover; the recoverable savings on a 500-VM migration are typically $150K–$400K of annual run rate.
SQL Server — the highest-value licensing decision
SQL Server is where migration licensing math gets dense. Three paths into Azure:
- SQL Server on Azure VM (IaaS) with AHB: bring core licences via AHB; pay only Windows VM + storage. Best for lift-and-shift, complex schemas, instances you do not want to rewrite.
- Azure SQL Database / Managed Instance with AHB: bring SQL Server Enterprise core licences and pay only the vCore base rate (no licence-included pricing). 55–65% savings vs. licence-included.
- Pass-through Edition Step-up: SQL Standard with SA can step up to Enterprise inside the SA window if the workload genuinely needs Enterprise features (Always On AG with synchronous secondaries, TDE, advanced compression). Often a cheaper path than buying new Enterprise cores at Azure list.
The single biggest SQL migration mistake we see: choosing Azure SQL Database licence-included pricing because the Azure portal defaults that way, then never converting to AHB after the fact. On an Azure SQL Managed Instance footprint of 200 vCores, the AHB conversion alone saves $280K–$420K annually.
Third-party ISV licensing — the surface Microsoft ignores
Azure Migrate scopes the Microsoft licensing layer. It says nothing about the third-party stack riding on those VMs: Oracle Database, IBM WebSphere, SAP, Red Hat Enterprise Linux, VMware vSphere licences embedded in Azure VMware Solution, Quest / Veeam / Commvault backup ISVs, and on-prem-only OEM subscriptions that do not have a cloud SKU. Each requires its own assessment:
- Oracle Database on Azure VMs: licence-mobility eligibility, two-licence-per-Azure-core ratio rule, and the Authorised Cloud Environment policy.
- SAP on Azure: HANA licensing for certified Azure instance types; ECC vs S/4 path decisions.
- RHEL: Red Hat Cloud Access for SA holders vs. PAYG Azure marketplace.
- VMware: AVS bundle vs. unbundled host vs. ELA conversion.
Build a third-party licensing register before migration. The number of enterprises we have seen pay both Oracle on-prem and Oracle Azure marketplace simultaneously because the ULA conversion was missed is non-trivial.
EA True-Up accounting and Azure consumption
If you are migrating mid-EA term, the True-Up matters. Net new Azure consumption flows through your MACC if you have one, and against the EA's Azure commit if not. Plan the migration cutover so Azure consumption hits inside a single billing period that is already on the True-Up cycle, not bridging months. Otherwise you can end up double-counted on the anniversary True-Up.
If the migration drives Azure spend above the MACC, you may negotiate an in-term MACC uplift in exchange for an additional discount. This is one of the few mid-term EA renegotiations Microsoft will entertain because it grows their wallet share. Use the moment.
Anonymised case study: $920K AHB recovery
A financial services client migrated 420 Windows Server and SQL Server workloads to Azure over six months. Their Azure consumption ramped from $0 to $410K/month. We were brought in three months post-cutover. The AHB audit found 64% of eligible VMs were not flagged for AHB (the migration partner used the default Azure portal settings), 18 SQL Managed Instances were on licence-included pricing despite having Enterprise SA, and 90 days of the 180-day dual-use window had been unused (so on-prem cores remained billed alongside Azure cores with no AHB benefit on the Azure side). Remediation: bulk AHB application across all eligible VMs and Managed Instances, true-back of dual-use timing on the on-prem side, $920K of annual run-rate recovered.
The Microsoft Licensing Briefing — 3 minutes, every Friday
Independent analysis of Microsoft commercial moves, with implications for your EA and Azure commit. No vendor spin.
No spam. Unsubscribe any time.
Where to take this from here
Migration licensing is the difference between a profitable Azure programme and a wash. Sequence the work: AHB eligibility audit before lift-and-shift, dual-use timing plan inside the cutover window, SQL Edition decisions per workload, third-party ISV register, EA True-Up accounting through migration. For the broader Azure cost picture, see the complete Azure cost optimisation guide. For commitment design after migration, the Savings Plans vs RIs guide covers post-migration steady-state commit. For EA renewal leverage when your migration changes the MACC math, the EA tier collapse playbook shows the negotiation moves. For end-to-end migration licensing review and ongoing FinOps governance, our Azure & MACC Advisory covers it as a single engagement. To benchmark your migration licensing position, request a no-cost discovery call.