Loading...

Generally Available: Transition to WS2012 / R2 ESUs enabled by Azure Arc from Volume Licensing

Generally Available: Transition to WS2012 / R2 ESUs enabled by Azure Arc from Volume Licensing

Customers that have enrolled in WS2012/ R2 ESUs through Volume Licensing for Year 1 can transition to Azure Arc for Year 2 of the program. Extended Security Updates afford customers with critical security patches for end of support Windows Server 2012/R2 machines. ESUs are available at no additional cost to customers running on Azure VMs or Azure Stack HCI. For customers running on-premises or other public clouds, WS2012/R2 ESUs are a paid offer.

 

The WS2012/R2 ESUs enabled by Azure Arc affords key advantages compared to ESUs through Volume Licensing including:

  • Pay as you Go flexibility to scale down WS2012 ESU consumption consumptively as customers migrate workloads to Azure and modernize affording flexibility. 
  • Ability to apply Azure Discounting with the decrement of a Microsoft Azure Consumption Commitment (MACC) affording significant financial benefits. 
  • Azure management capabilities including Azure Update Manager, Azure Change Tracking and Inventory, and Azure Machine Configuration are available at no additional cost.

aurnovcy_0-1721769578494.png

 

For enrollment, customers must specify their Year 1 Volume Licensing entitlement, indicating their Invoice Id (Invoice Number) to reflect their MAK Key entitlement at the time of Azure Arc WS2012 / R2 ESU license provisioning. This is available directly in the Azure portal with the current experience for Create an Extended Security Updates license. Programmatically, customers can use Azure CLI to generate new licenses, specifying the new Volume License Details parameter in az connectedmachine license | Microsoft Learn their Year 1 Volume Licensing entitlements by entering their respective Invoice Numbers. Customers must explicitly specify the Invoice Id (Number) in their license provisioning for Azure Arc.

 

Customers that make this indication in their license creation will not be back billed for Year 1 of Extended Security Updates, with billing to commence from the start of Year 2 of Windows Server 2012/R2 Extended Security Updates. Customers do not need to deactivate existing MAK Keys or unenroll from ESUs through Volume Licensing to enroll in WS2012/R2 ESUs enabled by Azure Arc. See enrollment steps at Deliver Extended Security Updates for Windows Server 2012 - Azure Arc | Microsoft Learn. After reviewing Azure Arc and licensing terms, connect your servers to Azure Arc, provision new WS2012/R2 ESU licenses in Azure portal specifying Volume Licensing entitlements, and link your servers to these licenses for enrollment. With just three months until the end of Year 1, the time is now to transition to WS2012/R2 Extended Security Updates enabled by Azure Arc. 

Published on:

Learn more
Azure Arc Blog articles
Azure Arc Blog articles

Azure Arc Blog articles

Share post:

Related posts

Announcing Azure MCP Server 2.0 Stable Release for Self-Hosted Agentic Cloud Automation

Azure MCP Server 2.0 is now generally available, delivering first-class self-hosting, stronger security hardening, and a faster foundation for...

11 hours ago

Azure Security: Private Vs. Service Endpoints

When connecting securely to a platform service such as a key vault or an Azure storage account, Microsoft recommends using a private endpoint ...

1 day ago

Give your Foundry Agent Custom Tools with MCP Servers on Azure Functions

Learn how to connect your MCP server hosted on Azure Functions to Microsoft Foundry agents. This post covers authentication options and setup ...

2 days ago

Azure Data Factory Tips for Reliable Microsoft Dynamics 365 CE and Dataverse Integrations

Reliable integrations between Microsoft Dynamics 365 Customer Engagement and external systems can become challenging. This is especially true ...

2 days ago

Scalable AI with Azure Cosmos DB: Tredence Intelligent Document Processing (IDP) | March 2026

Azure Cosmos DB enables scalable AI-driven document processing, addressing one of the biggest barriers to operational scale in today’s enterpr...

3 days ago

Announcing the end of support for Node.js 20.x in the Azure SDK for JavaScript

After July 9, 2026, the Azure SDK for JavaScript will no longer support Node.js 20.x. Upgrade to an Active Node.js Long Term Support (LTS) ver...

4 days ago

MCP Apps on Azure Functions: Quickstart with TypeScript

Learn how to build and deploy MCP (Model Context Protocol) apps on Azure Functions using TypeScript. This guide covers MCP tools, resources, l...

4 days ago

Setting up Power BI Version Control with Azure Dev Ops

In this blog post is a way set up version control for Power BI semantic models (and reports) using the PBIP (Power BI Project) format, Azure D...

10 days ago

Azure Developer CLI (azd) – March 2026: Run and Debug AI Agents Locally, GitHub Copilot Integration, & Container App Jobs

Run, invoke, and monitor AI agents locally or in Microsoft Foundry with the new azd AI agent extension commands. Plus GitHub Copilot-powered p...

11 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy