A licence error does not break anything, which is why it survives
Moving Windows Server and SQL Server to a hyperscale cloud changes the licensing math at every step, and the rules differ sharply across Azure, AWS and Google Cloud. What makes these errors durable is that a wrongly licensed machine runs exactly like a correctly licensed one.
Prepared by Redress Compliance · August 11, 2026 · Microsoft advisory. Based on 35 to 45 Microsoft estates benchmarked for hyperscale migration, 2024 and 2025.
Executive summary
Windows Server BYOL was assumed portable to AWS in about 6 of 10 business cases, ignoring the dedicated host requirement that added 15 to 30 percent to the modeled compute bill.
Microsoft defines Amazon, Google, Alibaba and itself as Listed Providers, and the flexible outsourcing rights introduced in October 2022 do not apply to them. That single definition is what most cloud business cases miss.
Azure Hybrid Benefit was switched off on 20 to 40 percent of eligible virtual machines at the point we reviewed the estate. It is the largest single lever available, cutting Windows Server cost by 30 to 45 percent and SQL Server Enterprise by up to 77 percent, and it was simply not enabled.
Nothing signals the omission, because the machine runs identically either way.
SQL Server edition was over specified, with Enterprise running workloads that Standard would carry, inflating cost by 2 to 4 times per core.
Edition choices made years earlier on premises travel into the cloud unexamined, where the per core economics are far less forgiving than they were on hardware you already owned.
License Mobility covers server applications, not the operating system. SQL Server, SharePoint, Exchange, Skype for Business, Project Server and BizTalk qualify through Software Assurance.
Windows Server and Windows desktop do not, and follow the outsourcing rules instead, which is the distinction that decides whether a dedicated host is required.
What moves, and under which rule
| Product | Governing rule | Practical effect on a Listed Provider |
|---|---|---|
| Windows Server | Outsourcing rules in the Product Terms | New licenses without prior rights need a dedicated host |
| SQL Server | License Mobility through Software Assurance | Portable to most clouds including AWS and GCP |
| SharePoint, Exchange, BizTalk | License Mobility through Software Assurance | Portable with active Software Assurance |
| Microsoft 365 and Office 365 | SaaS subscription | Unaffected by where compute runs |
The controlling document is the Microsoft Product Terms, not the account team slide, and the variable that decides your position is licence vintage and Software Assurance status.
Two estates running identical workloads can face completely different rules depending on when the licences were bought and whether Software Assurance is current, which is why a generic answer to the portability question is always wrong.
Establish the vintage and the Software Assurance position first, because everything downstream, including whether a dedicated host is required and therefore whether the business case holds, follows from it. The renewal position sits in the EA renewal playbook.
The checks that pay for themselves
- Audit Azure Hybrid Benefit across every eligible virtual machine, because it was switched off on 20 to 40 percent of them and it is worth 30 to 45 percent on Windows Server and up to 77 percent on SQL Server Enterprise.
- Re examine SQL Server edition per workload, since Enterprise running what Standard would carry inflated cost 2 to 4 times per core and the decision usually predates the migration.
- Confirm the dedicated host requirement before the business case is approved, as it added 15 to 30 percent to modeled compute on AWS in the cases that assumed portability.
- Separate the License Mobility products from the outsourcing products, because server applications travel with Software Assurance while Windows Server does not, and conflating them is what produces the wrong answer.
- Verify licence vintage and Software Assurance status first, since they determine what you can actually do and no general rule survives contact with them.
The Microsoft EA renewal playbook
Microsoft renewal moves, the EA framework, the M365 SKU framework, the Copilot framework, and the buyer side moves across the estate.
Get the playbook →Three errors, one reason they persist
The three findings point in different directions, which is worth noticing before looking for a single cause. Assuming Windows Server BYOL is portable to AWS overstates the savings in the business case.
Leaving Azure Hybrid Benefit switched off forfeits savings that were already available and already paid for. Running SQL Server Enterprise where Standard would serve overspends on the entitlement itself.
One is a modelling error, one is an operational omission, one is a design decision that aged badly. What they share is not their direction but their invisibility, and that is the thing to fix.
A virtual machine with Hybrid Benefit switched off boots, runs, serves traffic and passes every health check exactly like one with it enabled. Nothing in the operational telemetry distinguishes them, and no alert fires, because from the platform's point of view nothing is wrong.
The only place the difference appears is the invoice, and the invoice is read by people who are not looking at virtual machine configuration.
That is why the figure is 20 to 40 percent of eligible machines rather than a handful: there is no feedback loop, so the error accumulates instead of being corrected. The same property explains the other two.
An over specified SQL Server edition works perfectly, it simply costs two to four times more per core, and the business case error is discovered at migration only if someone re reads the Product Terms rather than the slide.
The practical consequence is that licensing on a hyperscale migration cannot be treated as a one time input to a business case, which is exactly how it is usually treated. It has to become a recurring operational check with a named owner, because the estate will not tell you when it is wrong.
Start with the definition that produces the most expensive surprise: Microsoft treats Amazon, Google, Alibaba and Microsoft itself as Listed Providers, so the flexible outsourcing rights from October 2022 do not apply.
And a Windows Server licence without prior rights needs a dedicated host on AWS or Google Cloud.
That requirement removed 15 to 30 percent of the modeled compute saving in the six of ten business cases that assumed otherwise. Confirm it against the Product Terms and your own licence vintage before the number is committed to a board paper.
The optimisation detail sits in the licence optimisation calculator.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across Microsoft cloud migration engagements, 2024 and 2025
Across roughly 35 to 45 Microsoft estates benchmarked for hyperscale migration between 2024 and 2025, the licensing line was understated in the original cloud business case more often than not:
What the dedicated host requirement added on AWS in the business cases that assumed Windows Server BYOL was portable without it.
Share of eligible virtual machines running without Azure Hybrid Benefit enabled, forfeiting savings already paid for.
Three patterns recurred: Windows Server BYOL assumed portable to AWS in about 6 of 10 business cases, Azure Hybrid Benefit switched off on 20 to 40 percent of eligible virtual machines, and SQL Server edition over specified at 2 to 4 times the per core cost Standard would have carried.
The wider library sits in the Microsoft practice.
Your first five moves
- Give the licensing position a named operational owner, because a wrongly licensed machine runs identically to a correct one and no alert will ever tell you it is wrong.
- Sweep every eligible virtual machine for Azure Hybrid Benefit, where it was off on 20 to 40 percent of them and is worth 30 to 45 percent on Windows Server alone.
- Confirm the dedicated host requirement before the board paper, since Listed Provider rules removed 15 to 30 percent of the modeled compute saving in 6 of 10 cases.
- Re specify SQL Server edition per workload, as Enterprise running Standard workloads cost 2 to 4 times more per core and the decision usually predates the cloud entirely.
- Work from the Product Terms and your licence vintage, not a vendor slide, because Software Assurance status decides what you can actually do. The Microsoft practice runs the check with you.
Frequently asked questions
Is Microsoft BYOL portable to any cloud?
Not by default. Microsoft defines Amazon, Google, Alibaba and Microsoft itself as Listed Providers, and the flexible outsourcing rights introduced in October 2022 do not apply to them. A Windows Server licence without prior rights needs a dedicated host on a Listed Provider.
What does License Mobility actually cover?
Server applications, not the operating system. SQL Server, SharePoint Server, Exchange Server, Skype for Business, Project Server and BizTalk Server qualify through Software Assurance. Windows Server and Windows desktop do not qualify and follow the outsourcing rules instead.
How much is Azure Hybrid Benefit worth?
It cuts Windows Server cost by 30 to 45 percent and SQL Server Enterprise by up to 77 percent, which makes it the largest single lever in a Microsoft cloud estate. It was nonetheless switched off on 20 to 40 percent of eligible virtual machines at the point of review.
Why do these errors go unnoticed for so long?
Because nothing breaks. A virtual machine with Hybrid Benefit disabled boots, runs and passes every health check exactly like one with it enabled, and no alert fires because the platform sees nothing wrong.
The difference appears only on the invoice, which is read by people not looking at machine configuration.
Does migrating change Microsoft 365 licensing?
No. Microsoft 365 and Office 365 are SaaS subscriptions and are unaffected by where your compute runs. The licensing questions on a hyperscale migration concern Windows Server, SQL Server and the other server applications, not the productivity suite.
What decides our specific position?
Licence vintage and Software Assurance status, read against the Microsoft Product Terms rather than an account team slide. Two estates running identical workloads can face different rules depending on when licences were bought and whether Software Assurance is current.
Why is SQL Server edition worth revisiting at migration?
Because Enterprise running workloads that Standard would carry inflated cost 2 to 4 times per core, and the edition decision usually predates the cloud. On hardware you already owned the over specification was tolerable, while per core cloud economics are far less forgiving of it.
Microsoft EA: Where the Leverage Really Is, and the Mistakes That Give It Away
Leverage lives in Microsoft's calendar and targets, and in credible movement at the edges of the estate. The three mistakes that hand it back: the copy-paste renewal, everyone-gets-everything licensing, and price-only negotiation under their clock.
