ITWeb has highlighted a familiar enterprise headache: Microsoft licensing is becoming tightly bound to modernization plans, especially for organizations running older Windows Server and SQL Server estates alongside Azure services.
The useful part of that argument is not that a new licensing model automatically lowers costs. It is that licensing now needs to be assessed as part of workload design. Perpetual licenses, Software Assurance, subscriptions, Azure consumption, virtualization rights and hybrid-use benefits can produce sharply different results depending on how servers are deployed and used.
Microsoft’s pay-as-you-go option for Windows Server 2025 is a clear example. The model licenses Arc-enabled physical servers and virtual machines through an Azure subscription rather than conventional perpetual licenses. Billing is per core and per hour, with the same rate for Standard and Datacenter editions.
That can suit short-lived, seasonal or rapidly changing workloads, and it removes the upfront purchase decision for new servers. But it is not a blanket replacement for traditional licensing. Each machine, including each VM, needs its own pay-as-you-go license; the model does not confer the virtualization rights that can make Datacenter licensing economical in dense VM environments. Remote Desktop Services CALs also remain separate.
Microsoft’s documentation adds an operational catch that is easy to miss: switching off or deprovisioning a server does not itself stop the Arc pay-as-you-go charge. Administrators must explicitly disable the service or remove the machine from Azure Arc.
For SQL Server estates, the central question remains deployment density. Organizations licensing Enterprise Edition physical cores can use unlimited virtualization rights where eligible, while individual VM licensing can be more appropriate for smaller or less consolidated workloads. The wrong choice can turn a “cloud flexibility” exercise into a higher recurring bill.
SQL Server 2025 also introduces edition changes worth checking during an upgrade review, including higher Standard Edition capacity limits and the discontinuation of the Web Edition after SQL Server 2022. Microsoft’s release notes also flag compatibility changes around linked servers and encryption defaults, so licensing and technical migration work should not be treated as separate projects.
The useful part of that argument is not that a new licensing model automatically lowers costs. It is that licensing now needs to be assessed as part of workload design. Perpetual licenses, Software Assurance, subscriptions, Azure consumption, virtualization rights and hybrid-use benefits can produce sharply different results depending on how servers are deployed and used.
Azure Arc changes the calculation
Microsoft’s pay-as-you-go option for Windows Server 2025 is a clear example. The model licenses Arc-enabled physical servers and virtual machines through an Azure subscription rather than conventional perpetual licenses. Billing is per core and per hour, with the same rate for Standard and Datacenter editions.That can suit short-lived, seasonal or rapidly changing workloads, and it removes the upfront purchase decision for new servers. But it is not a blanket replacement for traditional licensing. Each machine, including each VM, needs its own pay-as-you-go license; the model does not confer the virtualization rights that can make Datacenter licensing economical in dense VM environments. Remote Desktop Services CALs also remain separate.
Microsoft’s documentation adds an operational catch that is easy to miss: switching off or deprovisioning a server does not itself stop the Arc pay-as-you-go charge. Administrators must explicitly disable the service or remove the machine from Azure Arc.
SQL Server is no longer just a product-key decision
SQL Server 2025, which reached general availability on November 18, 2025, expands Microsoft’s hybrid and AI-oriented database pitch. It also offers more ways to license SQL Server through Azure Arc, including pay-as-you-go billing, existing licenses with Software Assurance or a SQL Server subscription, and license-only reporting for perpetual-license customers.For SQL Server estates, the central question remains deployment density. Organizations licensing Enterprise Edition physical cores can use unlimited virtualization rights where eligible, while individual VM licensing can be more appropriate for smaller or less consolidated workloads. The wrong choice can turn a “cloud flexibility” exercise into a higher recurring bill.
SQL Server 2025 also introduces edition changes worth checking during an upgrade review, including higher Standard Edition capacity limits and the discontinuation of the Web Edition after SQL Server 2022. Microsoft’s release notes also flag compatibility changes around linked servers and encryption defaults, so licensing and technical migration work should not be treated as separate projects.
What organizations should do
As reported by ITWeb, the practical response is an inventory and architecture review before renewing agreements or moving workloads. That review should identify:- Actual core counts, VM density and rights already owned.
- Which servers are stable enough for perpetual licensing versus candidates for consumption billing.
- Whether Software Assurance or subscriptions unlock benefits already being paid for.
- Azure Arc connectivity, governance and billing controls required for pay-as-you-go use.
- Application and integration risks before a SQL Server 2025 upgrade.
References
- Primary source: ITWeb
Published: 2026-04-08T09:46:00+00:00
The licensing problem: How can organisations reduce licensing complexity and costs? | ITWeb
Licensing models and costs have undergone changes over the past year, leaving companies at an expensive crossroads if they don’t modernise and manage their licensing effectively, says Chris Badenhorst, head of Azure core services at Braintree.
www.itweb.co.za
