Workload Orchestration in the Azure portal is now available: Deploy in minutes, scale with ease
Edge deployments rarely stay simple for long. What begins as an application running on a single Kubernetes cluster can quickly expand across stores, factories, branches, or other distributed locations, each having different configuration needs. That is exactly where workload orchestration for Azure Arc comes in. Workload orchestration helps teams manage that complexity by providing a centralized approach to consistently define, configure, and deploy applications across distributed cloud, on-premises, and edge environments, all while catering to custom configuration needs of individual sites and deployment targets. See the experience in action Evaluating a new deployment approach often starts slowly: study the documentation, package an application, complete the setup, and only then decide whether it fits. The Azure portal reverses that order with its jumpstart onboarding experience. Bring your Azure Arc-enabled Kubernetes cluster and deploy a pre-packaged application in minutes. Whether you are validating a proof of concept or introducing the product to your broader team, the new portal onboarding experience turns the end-to-end workflow into something you can quickly try on your own cluster. Scale from first deployment to production Once you have validated the first deployment, you can evolve the same approach for production. Onboard your infrastructure into workload orchestration, organize your deployment sites into hierarchies, and define shared configurations for all deployments – all without leaving the portal. This lets you expand from one cluster to a distributed fleet while retaining centralized governance, repeatability, and site-level flexibility. Ready to try it? Try now by deploying your first application with workload orchestration in the Azure portal. Explore the product documentation for the complete set of capabilities.Scaling Industrial AI at the Edge with Helin and Azure IoT
Remote industrial sites generate operational data continuously, but the ability to act on that data in near real time can be challenging. Bandwidth is often limited; connectivity is inconsistent, and the analysis needed to turn raw signals into insight typically depends on cloud connection. When worker safety is on the line, that gap matters even more, since a person entering a hazardous zone has to be detected and flagged on site independent of a cloud connection. Meeting those conditions calls for a secure, repeatable foundation, one that trains models in the cloud, runs inference locally, governs distributed edge devices, and turns the right signals into insight. Helin Data built that foundation: an edge-to-cloud platform that combines local inference, industrial data collection, and fleet observability on Azure. RedZone, Helin's vision AI application for hazardous-zone monitoring, is the first proof point of this platform. It uses the CCTV cameras already installed on a rig to detect when a person enters a defined danger zone around active equipment, triggering a local alert through an on-site interface and status lights, and logging the event for later safety and operational analysis. Because inference runs at the edge, RedZone can detect and alert without waiting on a connection to the cloud, while Azure handles centralized management, analysis, and model lifecycle activities. What sets this solution apart Designed for constrained environments – Inference runs directly on the edge box, so RedZone keeps detecting and alerting even through network outages, with no dependence on the cloud at runtime. Only priority events and metadata detected by RedZone sync to Azure, which keeps bandwidth use low on a constrained connection such as satellite connectivity used at some offshore sites. Secure, scalable fleet governance – Devices onboard automatically through Device Provisioning Service (DPS) with per-device X.509 certificates. Every device is listed in Azure Device Registry (in preview) and projected as native ARM resources, so updates and configuration changes can be targeted, governed, and audited using standard Azure tooling. Helin adds multi-level security, including public key infrastructure (PKI), data encryption, and industry-trusted authentication, protecting data as it moves from the rig to the cloud. Helin's observability layer spans device health, firmware updates, application status, and the data pipeline, so organizations can promptly identify and investigate potential issues across the edge-to-cloud pipeline. A closed edge-to-cloud AI loop – Models are trained and versioned in Azure Machine Learning, then deployed to the edge for local inference. Detections stream back into Microsoft Fabric, where the data can inform model evaluation and future model versions, closing the loop between the field and the cloud. A reusable application foundation – RedZone runs on the same platform and loop that can be adapted for additional customer scenarios. A different hazard, a different zone, or a different operational question can become its own application. Delivering a governed device fleet Azure IoT Hub and DPS provide secure device connectivity, messaging, and automated provisioning. The Azure IoT Hub integration with Azure Device Registry, currently in public preview, represents devices as Azure resources, providing a foundation for Azure-native fleet inventory and governance. Together, these services help Helin onboard, connect, and manage distributed edge deployments. Azure Device Registry (public preview with Azure IoT Hub): Provides the management plane, representing each device as an Azure Resource Manager resource so it can be governed with the same patterns used for other Azure resources including role-based access control, resource groups, tags, and resource-level management, with namespaces acting as the organizational and security boundary. Azure Device Registry integration with Azure IoT Hub and Microsoft-backed X.509 certificate management is in public preview and is not recommended for production workloads. Azure IoT Hub and DPS: Deliver secure onboarding and bidirectional messaging between the devices and the cloud. Helin Data Edge Inference and Data Collector: Runs vision AI inference at the edge and connects into the industrial control systems already on site, so each detection carries operational context. Industrial data is collected, contextualized, buffered, and filtered locally before important signals are sent to Azure. Microsoft Fabric: Ingests telemetry and turns it into an operational model for analysis and reporting, giving organizations clearer insight into their operations. Customer Impact This solution is already proven in a demanding industrial environment. When Helin Data implemented RedZone on Noble’s Maersk Discoverer rig, RedZone detected a person entering a hazardous zone and raised an alert in roughly 150 milliseconds. Processing the detection locally is particularly important offshore, where limited connectivity makes a cloud-dependent response impractical. Helin’s broader edge platform is already supporting Noble across its operations. The offshore drilling contractor, which operates a fleet of more than 40 rigs, uses Helin’s Remote CCTV Manager to provide authorized personnel with live video from more than 20 rigs. Reduced resolution streams sync to Noble’s secure Azure environment for viewing while full resolution recordings stay at the rig to reduce bandwidth use. Together, these examples demonstrate the broader platform pattern: process high-volume data locally, transmit the signals that matter, and centrally manage applications deployed across a distributed industrial fleet. Closing RedZone shows what becomes possible when Azure IoT Hub is used as more than a device-connectivity service. Combined with secure provisioning, Azure-native device governance, edge inference, model lifecycle management, and Microsoft Fabric, it becomes part of a repeatable platform for building and operating industrial AI applications at scale. For customers, the value extends beyond a single safety scenario. The same foundation can support new applications across worker safety, operational visibility, process improvement, and other industrial use cases, without rebuilding the underlying device and data infrastructure each time. Helin brings the industrial application expertise; Azure provides the scalable foundation on which those applications can be deployed, governed, and continuously improved. Take the next step Read the customer case study, Improving safety across a fleet of drilling rigs Learn more about RedZone in Seeing the Human Layer: Helin Brings Edge Vision AI to Industrial Operations on Azure. Explore Helin’s Intelligent Edge Application Platform is now available in Azure Marketplace Resources Deploy Azure IoT Hub with Device Registry integration and certificate management (preview) Azure IoT Hub Documentation Product documentation | Helin DocumentationHow Mesh Systems Builds on Azure IoT Hub and Azure IoT Operations to Accelerate Industrial AI
Manufacturers generate vast amounts of operational data, yet its complexity and fragmentation across historians, Operational Technology (OT) systems, and cloud platforms can slow AI adoption at scale. As organizations invest in AI to enhance productivity, quality, and decision making, the ability to connect and contextualize operational data becomes critical. Azure IoT Hub, Azure IoT Operations, and Mesh address this challenge together, spanning the full path from device connectivity to actionable AI-powered insights. Mesh brings deep Azure IoT platform experience and a practical path to industrial AI, with MeshCloud built on Azure IoT Hub, an open-source .NET Akri framework for Azure IoT Operations, and MeshInsights delivering generative AI-powered operational intelligence. This expertise is backed by a long history with Azure; Mesh launched its first IoT solution on Azure in private preview in 2009 and remained an early adopter of every major Azure IoT service since. Together, Azure IoT Hub, Azure IoT Operations, and Mesh give manufacturers a streamlined way to unify operational data and apply AI where it matters most. Unlocking legacy data with Mesh's Akri Connector Industrial organizations often struggle to modernize operations because critical operational data sits isolated inside historians and legacy Operational Technology (OT) systems. Many manufacturers are also wary of integrations that create new dependencies and limit future flexibility. Azure IoT Operations addresses this through an open architecture built around Akri, connecting industrial data sources while preserving interoperability across hardware and software environments. Mesh built on this foundation with its Akri Historian Connector, bringing historian and legacy operational data into Azure IoT Operations through prebuilt connectivity rather than source-by-source integration work. The result is faster access to operational data ready for analytics, AI, and industrial automation. The key features of this connector include: Restart-safe data continuity: Manufacturers can trust that operational data keeps flowing even through outages or restarts, with no data loss and no time spent recovering or reprocessing data. Secure, flexible authentication: Modern and legacy industrial systems connect under one security model, meeting enterprise-grade authentication standards without restructuring existing infrastructure. A foundation other connectors can be built on: The underlying framework handles the heavy lifting, so teams only need to build what's unique to each new OT data source. This means faster time to value for every new data source. Built in alignment with Azure IoT Operations roadmap: The connector stays up to date automatically, as new Azure IoT Operations features become available. This means manufacturers have access to the latest capabilities as the platform evolves. Together, Mesh and Azure IoT Operations give organizations a production-ready path from the shop floor into Azure IoT Operations and onward to Microsoft Fabric. Delivering Scalable Connected Products with Azure IoT Hub and MeshCloud MeshCloud helps manufacturers move from connected product pilots to fleet scale deployments faster by providing a platform build on Azure IoT Hub and other Azure native services. Azure IoT Hub provides per-device identity, support for MQTT, AMQP, and HTTPS, and built-in capabilities like device twins, direct methods, and rules-based message routing. Azure Device Provisioning Service (DPS) extends this foundation with zero-touch, just-in-time onboarding using X.509, TPM, or symmetric key attestation. Mesh operates as one cohesive engineering practice across the full connected product lifecycle, delivering hardware, firmware, wireless, edge, and cloud integration natively for Azure IoT Hub and Azure IoT Operations. That end-to-end scope is what MeshCloud, their Azure-native connected product platform, brings together. MeshCloud embeds Azure IoT Hub and DPS into an Azure-native connected product platform, giving organizations a faster path to connected product delivery without sacrificing control, scale, or solution ownership. The platform comes together across four layers: Edge to cloud: Connected devices, from MCU controllers to tablets and phones, register and authenticate through DPS and connect securely to IoT Hub, giving organizations a direct, secure line from shop floor to enterprise systems. Messaging and command: Event Hubs and Container Apps move telemetry and commands between devices and the cloud, with asset and ontology data exposed for digital twin management and device control. IT and operations: Azure Monitor, OpenTelemetry, Microsoft Entra, and Application Gateway bring platform observability, identity management, and secure ingress together, equipping IT and operations teams with a unified way to manage and secure the environment. Analytics and visualization: Telemetry flows into Azure Data Explorer and Microsoft Fabric for processing and storage, with Grafana, Power BI, and a Device Health UI giving teams fleet-wide visibility. This architecture enables organizations to move from pilot projects to fleet-scale deployments using Azure-native services, while maintaining interoperability across devices, connectivity protocols, and analytics platforms. For manufacturers, this means less time integrating infrastructure and more time delivering operational insights, connected services, and AI-powered workflows. Advancing Industrial Intelligence with MeshInsights As organizations connect more assets and operational systems, the next challenge becomes turning information into consistent actions and decisions. Microsoft Azure provides the cloud, data, and AI foundation for intelligent operational workflows, while giving organizations control over their data and business processes. Mesh extends this foundation through MeshInsights. MeshInsights is Mesh's AI agent offering for connected-product manufacturers. Mesh works with organizations to define a specific operational decision worth automating, such as classifying an alert or determining the right service response, and builds an evaluation standard from real telemetry, service history, and expert-validated examples. AI agents are then developed and measured against that standard, acting automatically on high-confidence cases and routing the rest to the organization's own experts. This extends connected systems beyond monitoring and reporting into trusted, auditable operational decisions. By combining Azure IoT platform services with MeshInsights, Mesh helps organizations move from connected infrastructure to autonomous, AI-driven action without changing where their data lives or who owns the architecture. Why This Matters Industrial transformation increasingly depends on strong collaboration between hyperscale cloud platforms and ecosystem partners who bring operational expertise, deployment acceleration, and industry-specific engineering capabilities. Mesh Systems demonstrates how partners can build differentiated value on top of Azure IoT platform services while helping organizations accelerate deployment timelines, standardize industrial data architectures, and operationalize AI across connected environments. Organizations are already putting this value to work in everyday operations. BUNN's cloud-connected coffee machines now give technicians a head start before every service call. As Kurt Powell, Executive Vice President at BUNN, put it: "With this solution, we know exactly which component to fix before we get there." WLS Lighting Systems has turned that same visibility into measurable savings at scale. Built on MeshCloud and Azure IoT, WLS's netLiNK gives property owners remote monitoring and control over individual light fixtures. Kevin Fletcher, President National Accounts at WLS, shared that the company has saved customers a little over $50 million in electrical costs since bringing netLiNK to market. Together, Azure IoT Hub, Azure IoT Operations, and Mesh Systems help manufacturers reduce integration complexity and operationalize industrial data, creating a foundation for AI driven operations spanning plant, edge, and cloud. The result: manufacturers spend less time on integration and more time improving productivity, resiliency, and decision making across their operations. Learn More Explore Mesh Systems solutions on Azure Marketplace: https://marketplace.microsoft.com/en-us/product/saas/mesh-systems.cloud?tab=Overview Read customer success stories: https://meshsystems.com/case-study-eaton-1/ Learn more about Azure IoT Operations: https://azure.microsoft.com/products/iot-operations/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 by specifying their Volume Licensing entitlements (Invoice Ids) in provisioning new Azure Arc WS2012/R2 ESU licenses. Extended Security Updates afford customers with critical security patches for end of support Windows Server 2012/R2 machines.
Windows Server 2012/R2 Extended Security Updates Licensing and Billing
While more and more organizations are moving towards cloud they are all using cloud in their own way depending on size and scale. Some have adopted cloud native model using Microsoft Azure, but some decided to use cloud services while still maintaining their on-premises footprint. The latter approach is known as Hybrid model. Hybrid also means having presence in more than one cloud provider. While the Hybrid model comes with some advantages and flexibility it has certain challenges too. One of the biggest challenges is the added management complexity. In a Hybrid model as the workload grows, organizations might struggle to control the growing complex environments which could be extending across data centers, multiple clouds and even the edge. One common struggle which we will be covering in this blog post today is… the ability to protect your end-of-support Windows Servers which are either in multi-cloud environment or on-premises. What options do Customers have for end-of-support Windows Servers 2012/R2? It’s not always easy for clients to upgrade all older Windows Servers to Win2016 or later. As the on-premises or multi-cloud environment servers reach the end of support, it also means end of security updates which can put business applications running on the server at security risk and can cause compliance issues. The Extended Security Updates (ESU) program is an option that can be used by customers to run Windows servers past the end of support for a maximum period but not indefinitely. The updates provided through ESUs are only Security updates as well as critical and important rated bulletins. Below are options for customers to use ESU: Migrate workload to Azure: Migrate existing affected Windows Server workloads as-is to Azure Virtual Machines which will automatically provide ESU for a defined period without being additionally charged for these updates on top of Azure VM's cost. Migrating workloads to Azure VMware Solution (AVS) also makes them eligible for free ESUs. Get ESU through Azure Stack HCI: On-premises Windows Server 2012/ 2012 R2 virtual machines connected to cloud via Azure Stack HCI can get free ESUs through Azure verification of VMs. Purchase ESU license outside of Azure: By purchasing ESU, they can protect them until they decide to upgrade them to a more recent version or migrate them to cloud. Purchase ESU License Options If workload running outside of Azure and not connected to cloud through Azure Stack HCI, customers have below options for licensing ESU. Azure Arc-enabled Servers: Their on-premises servers or in a hosted environment should be connected through Azure Arc service to have Arc-enabled servers. If they are Arc enabled, they can enroll their Windows Server 2012 and 2012 R2 servers for ESU via the Azure portal. They will be billed monthly on their subscription. Non-Arc enabled physical and virtual machines – For these servers they can enable ESU by acquiring ESU licenses through Microsoft Volume Licensing program. These ESU licenses are valid for annual coverage periods and each license is entitled to a specific server or operating system for the duration it has been purchased. They can acquire license for later years only if they have acquired licenses for prior years. Purchase ESU License Eligibility Criteria To be eligible for ESU licenses, their server/operating system must qualify one of the following: Customers should have Software Assurance to purchase ESUs on-premises or in hosted environment. Windows Server 2012/2012 R2 machines are licensed through Services Provider License Agreement (SPLA) and not using their own licenses. Windows Server 2012/2012 R2 machines are licensed with a Server Subscription where Software Assurance is not required. ESU Licensing with Azure Arc enabled Windows Server 2012/2012 R2 To deliver ESU for Windows Server 2012, customers should provision Windows Server Arc ESU licenses and then apply/link those licenses to Azure Arc enabled servers. These can be done via Azure portal. Before we progress to understand how to provision WS2012 ESU license and to link licenses to Arc enabled servers it is good to be aware about below: Standard vs Datacenter Edition: When standard edition of license selected, it will be limited to 2 virtual instances but with Datacenter Edition, it can be applied to unlimited virtual instances. vCore Vs pCore Licensing: vCore (Virtual Core ) Licensing: When this licensing is chosen, they will pay based on the number of virtual cores (vCores) being used by the OS. It requires a minimum of 8 cores per Virtual machine when selected. It uses the standard edition rate for billing. pCore ( Physical Core) Licensing: If they choose to license based on physical cores (pCores), then they pay based on the number of physical cores (pCores) utilized by the host operating system. It requires a minimum of 16 cores per server when selected. Customers have the flexibility to use this licensing with either edition. NOTE: vCore Licensing cannot be used on physical servers. They can select either licensing options or can also select a mix of pCore and vCore licensing for their virtual machines within the remit of their virtualization entitlements. Create a new ESU WS2012 license: Step 1: Sign in to the Azure portal Step 2: On the Azure Arc service page, select Extended Security Updates in the left pane under Management section. Step 3: Under Licenses tab, select Create. Step 4: Provide the information required in Create an Extended Security Updates license page to configure the license. Resource group: The ESU license will be billed to. License name: You can create multiple licenses. It may be helpful following a naming convention for license name. SKU and Core Type: Select the value based on licensing option chosen. Core Packs: Enter the value based on cores count required. You can modify the number of cores associated with a license later after creation. Step 5: Review the information provided and then select Create. License created from above will appear in the list under Licenses tab. Licenses can be linked to Arc-enabled servers following steps in next section. ESU license can be provisioned in a deactivated state during creation to avoid initiation of billing. Link ESU licenses to Arc-enabled servers: Each license can be linked to one or more Arc-enabled servers. Step 1: Sign in to the Azure portal Step 2: On the Azure Arc service page, select Extended Security Updates in the left pane under Management section. Step 3: Select Eligible Resources tab. This will give you the list of all Arc-enabled servers which are running Windows Server 2012/2012 R2 and eligible for ESU updates. ESU Status column tells us whether the machine is ESU enabled. Step 4: Select the machines from the list (with ESU Status = Not enabled) and then select Enable ESUs. Step 5: Next page Enable Extended Security Updates shows the count of machines selected for enabling ESU and lists the available licenses. Select the license that needs to be linked to these machines and then click on Enable at bottom of page. It will take some time but later the status of machine in ESUs Status column changes to Enabled. NOTE: A Windows Server is eligible to receive ESU updates once linked to an activated ESU license. ESU Licensing limits: Customer can include up to 10,000 cores within each WS2012 ESU license and if needed for more cores then can split the cores across multiple licenses. However, there is a limitation of only 800 licenses per resource group. ESU Billing: Billing for ESU is mainly dependent on three factors: Number of cores provisioned Selection of license edition Any eligible discounts While above three factors sound simple, below are few good to know points before we proceed to understand on how to estimate monthly cost: Is the Customer planning to decommission any servers? Do not include the core counts for servers, which need to be decommissioned and do not require extended security updates applied. Back-billing for sign-ups after the end of support dates: For customers who enroll in ESUs enabled by Azure Arc after the end of support date October 10, 2023, for Windows Server 2012/R2, they will be billed a one-time upfront charge for the months they missed after the end of support date, with billing coming in at the end of the first month when they signed-up. Example: XYZ Corp has decided to enroll for ESU for Windows Server 2012/R2 in February 2024. In that case they will receive a one- time back-bill for October (starting from 11th of the month), November, December 2023, and January 2024 at the end of February month. After February, for the later months, XYZ Corp billing will only be based on the current month. Back-billing applies even if a customer intermittently deactivates ESUs. Example: If XYZ Corp, unenrolls in March 2024 and then decides to re-enrolls in June 2024, the re-enrollment will trigger back-billing for April and May 2024. When ESU enabled by Azure Arc, Customers can link their already paid extended security updates to their eligible Disaster Recovery Benefit servers. Billing is monthly. Decrementing, deactivating, or deleting a license will result in charges for up to five more calendar days from the time of decrement, deactivation, or deletion. Reduction in billing isn't immediate. There is no cost for non-production workloads that need ESU updates. Examples of Cost-Effective ESU Licensing: It is recommended to refer to the Azure Pricing calculator for calculating estimated monthly cost. Let us take some examples (based on public pricing) to understand cost effective ESU licensing. Example 1 *: XYZ Corp. has currently got a VMware cluster containing 28 hosts with 736 physical cores on-premises. There are 90 VMs on the cluster and they are running Windows Server 2012 R2 consuming all 736 cores. Based on above information, public pricing for Arc Enabled ESU for both the licensing option would be: pCore (Physical Core) Licensing: 46 x Windows Server 2012 DC – 16 Core (£341) = ~ £15K / month vCore (Virtual Core) Licensing: 92 x Windows Server Standard – 8 Core (£30) = ~ £3K / month They can either license the entire cluster with 736 Windows Server 2012 Datacenter ESU physical cores or license each VM individually with a total of 736 standard edition virtual cores. In the above case, it's cheaper to purchase an Arc ESU Windows Server 2012 Standard edition license associated with 736 virtual cores if all other factors align with the option. NOTE: In the above example it was assumed that ESU vCore/pCore licensing requirements for the machines were achieved. Example 2 *: ABC Corp has currently got 64 cores of Datacenter Edition and 128 cores of standard edition physical hosts running Windows 2012 and eligible for ESU. When buying licenses, they can buy in 2 or 16 core packs with not much difference in cost. 8 packs of 2 cores costs almost the same as 1 pack of 16 core. When buying 16 core packs then pricing calculation will be: 64 cores of Datacenter Edition = 4x Windows Server 2012 DC – 16 core (£341) = ~ £1.3 K /month 128 cores of Standard Edition = 8 x Windows Server Standard – 16 core (£60) = £480/month When calculating with 2 core packs, calculation will look like: 64 cores of Datacenter Edition = 32 x Windows Server 2012 DC – 2 core (£43) = ~ £1.3 K /month 128 cores of Standard Edition = 64 x Windows Server Standard – 2 core (£7.4) = £473.6 /month As seen in the above calculations, buying multiple packs of lesser core, or buying a smaller count of packs with larger core size does not bring much cost difference. However, for situations where they need granular control on activation of licenses, it might help with the flexibility in buying multiple packs of required cores. * This example is only for illustration purposes. Scenario and factors to consider for cost effective ESU licensing option may vary based on Customer requirements. Summary Extended Security Updates for Windows Server includes security updates, critical and important bulletins for a period after end of extended support. ESUs do not include new features, customer-requested non-security updates, or design change requests. After the period of ESU ends, Microsoft will stop providing updates. It is recommended to upgrade your version of Windows Server to the current version or more recent version as soon as possible for the most advanced security, performance and innovation. Where updates are not immediately possible, migrating your on-premises Windows servers Infrastructure (that has past the end of extended support or almost reaching to it) to Azure or connecting them to cloud using Azure Stack HCI is also an option (for a defined period) as they're eligible for free ESUs. ESU Availability and End dates information for Windows Server 2012/2012 R2 are: End of Extended Support/ESU Start Date: October 10, 2023 ESU End Date Year 1: October 8, 2024 ESU End Date Year 2: October 14, 2025 ESU End Date Year 3: October 13, 2026 Type of Security Update: Critical, Important Learn More Search Product and Services Lifecycle Information - Microsoft Lifecycle | Microsoft Learn Overview of Extended Security Updates for Windows Server 2008, 2008 R2, 2012, and 2012 R2 | Microsoft Learn Product Lifecycle FAQ - Extended Security Updates | Microsoft Learn Extended Security Updates (ESU) on Azure Stack HCI - Azure Stack HCI | Microsoft Learn Manage Azure Arc-enabled Servers using Windows Admin Center in Azure preview | Microsoft Learn Overview of Windows Server upgrades | Microsoft Learn Perform an in-place upgrade of Windows Server | Microsoft LearnGenerally Available: Windows Server 2012 and 2012 R2 Extended Security Updates enabled by Azure Arc
Secure your End-of-Life Windows Server infrastructure on your own terms with Azure Arc. Benefit from the flexibility of a monthly Azure billed service and free access to Azure management services by leveraging Extended Security Updates enabled by Azure Arc for your Windows Server 2012 and 2012 R2 machines.The first Windows Server 2012/R2 ESU Patches are out! Are you protected?
Receive critical security patches for your WS2012/R2 machines enrolled in ESUs enabled by Azure Arc. Follow these detailed instructions outlining all of the enrollment and prerequisites, so you are protecting your EOL infrastructure.
