Loading...

Coming Soon: Transition to WS2012/R2 ESUs enabled by Azure Arc for Year 2 and beyond

Coming Soon: Transition to WS2012/R2 ESUs enabled by Azure Arc for Year 2 and beyond

Announced during last week’s Windows Server Summit 2024, customers will be able to transition to Azure Arc for WS2012 Extended Security Updates enabled by Azure Arc for Year 2 if they had purchased Year 1 of Extended Security Updates for Volume Licensing. This experience will ask customers to supply their Invoice Id, corresponding to WS2012 ESU purchases from Volume Licensing.

 

With its pay as you go flexibility as an Azure billed service and inclusion of Azure management services like Azure Update Manager and Machine Configuration at no additional cost, WS2012 ESUs enabled by Azure Arc offer financial and experience benefits to customers. This is especially critical to support customers in their journey of migrating and modernizing End of Life infrastructure to Azure.

 

This transition experience is coming soon! To prepare, your organization can begin to review the connectivity requirements for Azure Arc, whitelisting the necessary endpoints, and deploying the Connected Machine agent to eligible Windows Server 2012/R2 Standard and Datacenter machines using at-scale options like Configuration Manager and Group Policy.

 

aurnovcy_0-1712143268900.png

 

Beyond the announcement, we had three sessions covering Azure Arc capabilities during last week’s Windows Server Summit:

 

Empowering Windows Server customers to modernize to Azure management, Azure Arc is the bridge bringing cloud capabilities to Windows Servers across hybrid, multicloud, and edge environments. To sign up for feedback and notification when the experience becomes available, register at https://aka.ms/WS2012ArcESUTransition/.

Published on:

Learn more
Azure Arc Blog articles
Azure Arc Blog articles

Azure Arc Blog articles

Share post:

Related posts

Storage migration: Combine Azure Storage Mover and Azure Data Box

Migrating storage from on-premises can be challenging. That’s why we are on a mission to make your migrations as simple as possible. We've dev...

1 hour ago

Loop DDoS Attacks: Understanding the Threat and Azure's Defense

In the realm of cybersecurity, Distributed Denial-of-Service (DDoS) attacks are a significant concern. The recent holiday season has unveiled ...

9 hours ago

Azure Communication Services at Microsoft Build 2024

Join us in-person in Seattle or virtually for Microsoft Build 2024 from May 21 to 24. We're excited to share the latest updates from Azure Com...

10 hours ago

Azure Developer CLI (azd) – May 2024 Release

This post announces the May release of the Azure Developer CLI (`azd`), which includes a new demo mode, various .NET Aspire enhancements, and ...

10 hours ago

Join us at Build 2024: Get the latest on Azure Cosmos DB in Seattle or online!

Are you ready to dive into the future of AI and data innovation? Microsoft Build 2024 is just around the corner, taking place May 21–23 in Sea...

12 hours ago

Announcing Data API builder General Availability for Azure Cosmos DB

Great news for developers out there! The Data API Builder for Azure Cosmos DB is now officially available, eliminating the need for writing co...

1 day ago

Organizing rule collections and rule collection groups in Azure Firewall Policy

Firewall Policy is the recommended method to manage Azure Firewall security and operational configurations. When using Firewall Policy, any ru...

1 day ago

Get Started with Azure AI Services | Open AI and Deployment Models

Table of Contents   Overview - Azure AI Services Kind of Azure AI Services Responsible AI Services Limited Access Features Cognitive Acc...

1 day ago

Using Sempy to Authenticate to Fabric/Power BI APIs using Service Principal and Azure Key Vault

In this blog post, the author demonstrates how to use Azure Key Vault and Azure identity to authenticate securely when working with Fabric Not...

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