Windows Server and SQL Server ESU Deadlines: 2016 Licensing Costs and Azure Changes

The four dates on Microsoft's ESU page​

Microsoft's Windows Server ESU planning page lists four milestones:

• July 14, 2026: SQL Server 2016 Extended Support ends and its ESUs begin.
• October 13, 2026: Windows Server 2012 ESUs end.
• January 12, 2027: Windows Server 2016 Extended Support ends and its ESUs begin.
• July 12, 2027: SQL Server 2014 ESUs end.

Microsoft's lifecycle and Azure Arc documentation confirms these dates and adds the end points the marketing page leaves out:

For SQL Server 2016, Microsoft's SQL Server ESU FAQ gives an end of support date of July 14, 2026, with ESUs available until July 17, 2029. Microsoft's own documentation and independent trackers describe the transition the same way: the lifecycle page expresses the same moment as 7/15/2026 6:59:59 AM Pacific — that is the instant support lapses. That is also when the first ESU term begins. So the one-day differences you see across Microsoft pages come from time zones and labels, not from conflicting dates.

Section summary: Server 2012 is done. SQL Server 2014 has about eight months of ESU left. SQL Server 2016 has the longest runway. Windows Server 2016 is the next big cliff.

Windows Server 2012: the bridge is gone​

Microsoft's Windows Server 2012 release health page says that as of October 13, 2026, ESUs for Windows Server 2012 have ended, and devices on that version will no longer get security updates against the latest threats. The Azure Arc documentation is more specific. The October 13, 2026 security update was the last ESU release, and Arc-enabled ESU licenses were deactivated at midnight UTC on October 14, 2026, at which point they stopped granting update eligibility. Billing for those licenses stopped too. The license resources stay visible in Azure, but they now do nothing.

Two more details from that release health page:

• Microsoft says the page itself retires on November 13, 2026. That is today, so even the status page for Server 2012 is closing.
• The page's last entry is a confirmed known issue. After the October 13, 2026 update (KB5126835) and later updates, SQL Server linked-server queries that use OLE DB providers can leave connections open, and the connections pile up over time. Oracle and PostgreSQL are named as affected targets. Windows Server 2012 and 2012 R2 are on the affected list alongside current releases. Microsoft says an out-of-band fix is coming, and for now offers a mitigation through Microsoft Support for business. The page doesn't say whether that fix will reach the out-of-ESU Server 2012 builds, so don't assume it will.

What should a Server 2012 admin do now? Microsoft's answer is to upgrade, and its release health page points to Windows Server 2025 as the current LTSC release. A free 180-day evaluation is available.

Section summary: Server 2012 and 2012 R2 machines are now unpatched. The only remaining choices are to upgrade, migrate, or isolate them.

Windows Server 2016: the next deadline​

Windows Server 2016 reaches the end of support on January 12, 2027. According to Microsoft's Azure Arc preparation guide:

• ESUs for Windows Server 2016 provide Critical and Important security updates for up to three years, through 2030.
• Standard and Datacenter editions are supported.
• You've been able to configure Windows Server 2016 ESUs in the Azure portal since August 3, 2026. Arc billing begins January 13, 2027.
• Arc enrollment for Server 2016 requires Azure Connected Machine agent version 1.62 or higher. Server 2012 required 1.34.
• Arc-based ESUs for Server 2012 and 2016 are not available in Azure operated by 21Vianet regions.
• Don't use Arc to deliver ESUs to VDI virtual machines. Microsoft says to use Multiple Activation Keys for those instead.

Azure is not free this time​

This is the most important difference from the Server 2012 era. Microsoft's marketing page promises ESUs "for 3 more years in Azure" across VMs, Dedicated Host, Azure VMware Solution and the Azure Stack portfolio. That's true, but it leaves out the price. The Lifecycle FAQ says Server 2012/2012 R2 ESUs were free on those Azure destinations, while Windows Server 2016 ESUs are a paid offering in Azure. Microsoft also says installation and delivery details for Server 2016 ESUs in Azure will be published when the offering is generally available. Anyone who budgeted for the 2016 migration based on 2012's free Azure ESUs needs to redo those numbers.

Microsoft's Arc licensing guidance lists other 2012-era benefits that don't carry over to Server 2016:

• No free disaster-recovery benefit. DR instances need paid ESU coverage, and their cores have to be counted in your Arc license.
• No Visual Studio dev/test benefit for Server 2016 ESUs.

Licensing math, briefly​

According to Microsoft's ESU FAQ and Arc licensing guidance:

• pCore licensing has a 16-core minimum per server. A Standard host covers up to two guest VMs. A Datacenter host covers all of them.
• vCore licensing has an 8-core minimum per VM, is billed at the Standard rate, and works only for virtualized operating systems.
• You can't use Datacenter edition on a vCore basis. Once a license is created, you can't change its edition or type, but you can raise or lower its core count.

Microsoft's own example: a 16-node VMware cluster with 1,024 physical cores, where 44 VMs run Server 2016 and use 506 vCores. Licensing those 506 vCores at the Standard rate costs less than licensing the whole cluster as Datacenter. If your legacy VMs are spread thinly across large modern hosts, count vCores before you count pCores.

On eligibility, Microsoft's Arc documentation says you need Software Assurance through EA, EAS, EES, SCE or Open Value programs. Machines licensed through SPLA or a Server Subscription don't need Software Assurance. That's broader than the ESU page's shorthand of "Software Assurance under an Enterprise Agreement," so check your actual agreements before you assume you're excluded.

Section summary: Server 2016 ESUs exist, but they cost money everywhere, including in Azure. Arc enrollment is open now, and the licensing model you choose can change the bill a lot.

SQL Server 2014 and 2016: Critical fixes only​

SQL Server ESUs are narrower than the Windows Server ones. Microsoft's SQL Server ESU FAQ says they include only Critical security updates. Because releases depend on MSRC ratings, Microsoft says there is no regular release cadence. Months can pass with nothing, and that's normal.

What you need to know:

• Editions: Only Enterprise and Standard qualify. Express, Developer and Web editions can't be subscribed. If those editions sit on the same machine as a covered Standard or Enterprise instance of the same version, though, the installed updates apply to all instances.
• Patch baseline: SQL Server 2014 and 2016 ESUs include the latest Cumulative Update. If you've only been applying GDR updates, Microsoft recommends installing and validating the latest CU when you subscribe, not when the first ESU arrives.
• Azure pricing changed: SQL Server 2014 workloads moved as-is to Azure VMs get free ESUs through Windows Update. SQL Server 2016 doesn't. Moving it to an Azure VM no longer includes free ESUs.
• Billing models: vCore subscriptions have a 4-core minimum per VM. pCore subscriptions have a 16-core minimum and are billed at the Enterprise rate.
• Back-billing: Signing up late doesn't save money. Microsoft's example: a SQL Server 2016 customer who enrolls in January 2027 gets a one-time charge for July through December 2026. If an Arc agent is disconnected or inactive for more than 30 days, the subscription may be canceled, and reconnecting can trigger charges back to the start of the current year.
• Dev/test: If you have an ESU plan for production servers, you can manually apply those updates to servers licensed under Visual Studio (MSDN) subscriptions at no extra cost.

Once subscribed, patches arrive through the usual channels: Microsoft Update, Windows Update, Configuration Manager or Azure Update Manager. You can also download them from the Azure portal. Instances that can't connect to Arc may still qualify through volume licensing and can be registered as disconnected in the portal.

Section summary: SQL Server 2014 coverage ends July 12, 2027. SQL Server 2016 runs to 2029 but costs more than earlier versions, including on Azure VMs.

A practical checklist for the next 60 days​

1. Inventory by version and edition. Separate Server 2012/2012 R2 (no coverage), Server 2016 (deadline January 12, 2027), SQL Server 2014 (final ESU year) and SQL Server 2016 (paid ESU through 2029).
2. Isolate or retire Server 2012 boxes. Nothing is patching them anymore.
3. Check licensing for Server 2016 now. Confirm Software Assurance, Server Subscription or SPLA status, and model pCore versus vCore costs per host.
4. Prepare Arc onboarding. Install Connected Machine agent 1.62+, confirm the network endpoints and certificate authorities Microsoft lists, and plan around the 21Vianet and VDI exclusions.
5. Validate SQL Server CUs before ESU enrollment, and check that the Arc agents on SQL hosts are healthy so they don't trigger the 30-day cancellation.
6. Write down an exit date. Microsoft itself calls ESU a last-resort, temporary bridge. It doesn't extend the product lifecycle and doesn't include general technical support, bug fixes or new features.

The bottom line​

Microsoft's ESU page is mostly a pitch for Azure, with suggestions to modernize on Azure App Service and Azure SQL Managed Instance, use Azure Migrate, Azure Hybrid Benefit and Defender for Cloud. That bias is understandable, and some of those options really do cut costs. None of them is required to qualify for ESUs, though, and the free-in-Azure deal that made Server 2012 migrations easier doesn't apply to Server 2016 or SQL Server 2016.

ESUs are worth buying if you need time to migrate. Just don't let them become the plan.