Added note about WS 2008 EOL

Jeronika-MS · Jeronika-MS · commit 4214d60736fa · 2026-02-27T14:35:34.000+05:30
diff --git a/articles/site-recovery/avs-tutorial-reprotect.md b/articles/site-recovery/avs-tutorial-reprotect.md
@@ -4,7 +4,7 @@ description: Learn how to reprotect Azure VMware Solution VMs after failover to
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 02/12/2026
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 ms.custom: MVC
 # Customer intent: As an IT administrator managing virtual machines, I want to reprotect Azure VMware Solution VMs after failover, so that I can ensure data consistency and maintain disaster recovery capabilities in my cloud environment.
@@ -16,6 +16,8 @@ After [failover](avs-tutorial-failover.md) of Azure VMware Solution VMs to Azure
 
 ## Before you begin
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 1. Follow the steps in [this article](vmware-azure-prepare-failback.md) to prepare for reprotection and failback, including setting up a process server in Azure, and an Azure VMware Solution private cloud master target server, and configuring a site-to-site VPN, or ExpressRoute private peering, for failback.
 2. Make sure that the Azure VMware Solution private cloud configuration server is running and connected to Azure. During failback, the VM must exist in the configuration server database. Otherwise, failback is unsuccessful.
 3. Delete any snapshots on the Azure VMware Solution private cloud master target server. Reprotection won't work if there are snapshots.  The snapshots on the VM are automatically merged during a reprotect job.
diff --git a/articles/site-recovery/azure-stack-site-recovery.md b/articles/site-recovery/azure-stack-site-recovery.md
@@ -2,7 +2,7 @@
 title: Replicate Azure Stack Hub to Azure using Azure Site Recovery
 description: Learn how to set up disaster recovery to Azure for Azure Stack Hub with the Azure Site Recovery service.
 ms.topic: how-to
-ms.date: 08/29/2025
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 ms.service: azure-site-recovery
 ms.custom:
@@ -79,6 +79,7 @@ Here's what you need to set up this scenario.
 
 Make sure that the VMs are running one of the operating systems summarized in the table.
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
 
 **Operating system** | **Details**
 --- | ---
diff --git a/articles/site-recovery/azure-to-azure-support-matrix.md b/articles/site-recovery/azure-to-azure-support-matrix.md
@@ -2,7 +2,7 @@
 title: Support Matrix for Azure VM Disaster Recovery with Azure Site Recovery
 description: Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery.
 ms.topic: concept-article
-ms.date: 02/12/2026
+ms.date: 02/27/2026
 ms.service: azure-site-recovery
 author: Jeronika-MS
 ms.author: v-gajeronika
@@ -97,6 +97,8 @@ Site Recovery supports replication of Azure VMs running the operating systems li
 
 ### Windows
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 Operating system | Details
 --- | ---
 Windows Server 2025 | Supported.
diff --git a/articles/site-recovery/hydration-process.md b/articles/site-recovery/hydration-process.md
@@ -5,7 +5,7 @@ author: Jeronika-MS
 ms.author: v-gajeronika
 ms.topic: concept-article
 ms.service: azure-site-recovery
-ms.date: 09/18/2025
+ms.date: 02/27/2026
 ---
 
 # Configure on-premise disks for Azure through Hydration
@@ -99,6 +99,8 @@ The preparation script executes the following changes based on the OS type of th
 
 1. **Install the Windows Azure Guest Agent**.
 
+    [!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
     Azure Site Recovery will attempt to install the Microsoft Azure Virtual Machine Agent (VM Agent), a secure, lightweight process that manages virtual machine (VM) interaction with the Azure Fabric Controller. The VM Agent has a primary role in enabling and executing Azure virtual machine extensions that enable post-deployment configuration of VM, such as installing and configuring software. Azure Site Recovery automatically installs the Windows VM agent on Windows Server 2008 R2 and higher versions.
 
     The Windows VM agent can be manually installed with a Windows installer package. To manually install the Windows VM Agent, [download the VM Agent installer](https://go.microsoft.com/fwlink/?LinkID=394789). You can also search for a specific version in the [GitHub Windows IaaS VM Agent releases](https://github.com/Azure/WindowsVMAgent/releases). The VM Agent is supported on Windows Server 2008 (64 bit) and later.
diff --git a/articles/site-recovery/hyper-v-azure-architecture.md b/articles/site-recovery/hyper-v-azure-architecture.md
@@ -3,7 +3,7 @@ title: Hyper-V disaster recovery architecture in Azure Site Recovery
 description: This article provides an overview of components and architecture used when deploying disaster recovery for on-premises Hyper-V VMs (without VMM) to Azure with the Azure Site Recovery service.
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 11/14/2019
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 author: Jeronika-MS
 # Customer intent: As a system administrator, I want to deploy disaster recovery for on-premises Hyper-V virtual machines to Azure, so that I can ensure business continuity and minimize downtime in case of failures.
@@ -86,9 +86,10 @@ If you're using a URL-based firewall proxy to control outbound connectivity, all
         ![Screenshot of the jobs list in the Jobs tab.](media/hyper-v-azure-architecture/image1.png)
         ![Screenshot of the Enable protection screen with more details.](media/hyper-v-azure-architecture/image2.png)
 
-
 ### Initial data replication
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 1. When initial replication is triggered, a [Hyper-V virtual machine snapshot](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd560637(v=ws.10)) snapshot is taken.
 2. Virtual hard disks on the virtual machine are replicated one by one, until they're all copied to Azure. This might take a while, depending on the virtual machine size, and network bandwidth. [Learn how](https://support.microsoft.com/kb/3056159) to increase network bandwidth.
 3. If disk changes occur while initial replication is in progress, the Hyper-V Replica Replication Tracker tracks the changes as Hyper-V replication logs (.hrl). These log files are located in the same folder as the disks. Each disk has an associated .hrl file that's sent to secondary storage. The snapshot and log files consume disk resources while initial replication is in progress.
diff --git a/articles/site-recovery/hyper-v-azure-common-questions.md b/articles/site-recovery/hyper-v-azure-common-questions.md
@@ -1,7 +1,7 @@
 ---
 title: Common questions for Hyper-V disaster recovery with Azure Site Recovery 
 description: This article summarizes common questions about setting up disaster recovery for on-premises Hyper-V VMs to Azure using the Azure Site Recovery site.
-ms.date: 04/26/2025
+ms.date: 02/27/2026
 ms.service: azure-site-recovery
 ms.topic: overview
 ms.author: v-gajeronika
@@ -33,6 +33,8 @@ Yes, you can purchase [reserved Azure virtual machines](https://azure.microsoft.
 
 ### What do I need in Hyper-V to orchestrate replication with Site Recovery?
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 For the Hyper-V host server what you need depends on the deployment scenario. Check out the Hyper-V prerequisites in:
 
 * [Replicating Hyper-V VMs (without VMM) to Azure](./hyper-v-azure-tutorial.md)
diff --git a/articles/site-recovery/hyper-v-azure-support-matrix.md b/articles/site-recovery/hyper-v-azure-support-matrix.md
@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
 description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 08/19/2025
+ms.date: 02/27/2026
 author: Jeronika-MS
 ms.author: v-gajeronika
 # Customer intent: As a IT admin managing on-premises Hyper-V VMs, I want to implement disaster recovery to Azure, so that I can ensure business continuity and data protection in case of on-premises failures.
@@ -39,6 +39,7 @@ Hyper-V (running with Virtual Machine Manager) | Virtual Machine Manager 2022  (
 
 ## Replicated VMs
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
 
 The following table summarizes VM support. Site Recovery supports any workloads running on a supported operating system.
 
diff --git a/articles/site-recovery/includes/end-of-life-notes-windows-server-2008.md b/articles/site-recovery/includes/end-of-life-notes-windows-server-2008.md
@@ -0,0 +1,13 @@
+---
+ms.assetid: 
+title: include file
+description: include file with notes on end of life information for Windows Server 2008 and 2008 R2.
+author: Jeronika-MS
+ms.author: v-gajeronika
+ms.date: 02/27/2026
+ms.topic:  include
+ms.service: azure-site-recovery
+
+---
+> [!NOTE]
+> Windows Server 2008 and Windows Server 2008 R2 have reached End of Life (EOL). For more information, see, [End of support for Windows Server 2008 and Windows Server 2008 R2](/troubleshoot/windows-server/windows-server-eos-faq/end-of-support-windows-server-2008-2008r2) and [Perform in-place upgrade to Windows Server 2016, 2019, 2022, or 2025](/azure/virtual-machines/windows-in-place-upgrade#perform-in-place-upgrade-to-windows-server-2016-2019-2022-or-2025). Review your usage and plan OS upgrades and migrations accordingly.
diff --git a/articles/site-recovery/migrate-tutorial-windows-server-2008.md b/articles/site-recovery/migrate-tutorial-windows-server-2008.md
@@ -3,7 +3,7 @@ title: Migrate Windows Server 2008 servers to Azure with Azure Migrate/Site Reco
 description: This article describes how to migrate on-premises Windows Server 2008 machines to Azure, and recommends Azure Migrate.
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 12/30/2022
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 author: Jeronika-MS
 ms.custom:
@@ -16,6 +16,8 @@ ms.custom:
 
 # Migrate servers running Windows Server 2008 to Azure
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 This tutorial shows you how to migrate on-premises servers running Windows Server 2008 or 2008 R2 to Azure, using Azure Site Recovery. 
 
 In this tutorial, you learn how to:
diff --git a/articles/site-recovery/physical-manage-configuration-server.md b/articles/site-recovery/physical-manage-configuration-server.md
@@ -5,7 +5,7 @@ services: site-recovery
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 07/27/2022
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 ms.custom:
   - sfi-image-nochange
@@ -21,6 +21,8 @@ You set up an on-premises configuration server when you use the [Azure Site Reco
 
 ## Prerequisites
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 The table summarizes the prerequisites for deploying the on-premises configuration server machine.
 
 | **Component** | **Requirement** |
diff --git a/articles/site-recovery/physical-to-azure-failover-failback.md b/articles/site-recovery/physical-to-azure-failover-failback.md
@@ -5,7 +5,7 @@ description: Learn how to fail over physical servers to Azure, and fail back to
 services: site-recovery
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 02/12/2026
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 author: Jeronika-MS
 # Customer intent: As a system administrator, I want to set up failover and failback for physical servers using cloud replication, so that I can ensure business continuity and disaster recovery in the event of an on-premises outage.
@@ -72,6 +72,8 @@ After failover you need to [configure Azure settings](site-recovery-failover.md#
 
 ## Prepare for reprotection and failback
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 After failing over to Azure, you reprotect Azure VMs by replicating them to the on-premises site. Then after they're replicating, you can fail them back to on-premises, by running a failover from Azure to your on-premises site.
 
 1. Physical servers replicated to Azure using Site Recovery can only fail back as VMware VMs. You need a VMware infrastructure in order to fail back. Follow the steps in [this article](vmware-azure-prepare-failback.md) to prepare for reprotection and failback, including setting up a process server in Azure, and an on-premises master target server, and configuring a site-to-site VPN, or ExpressRoute private peering, for failback.
diff --git a/articles/site-recovery/replication-appliance-support-matrix.md b/articles/site-recovery/replication-appliance-support-matrix.md
@@ -3,7 +3,7 @@ title: Support Requirements for Azure Site Recovery Replication Appliance
 description: This article describes support and requirements when you deploy the replication appliance for VMware disaster recovery to Azure with Azure Site Recovery with modernized architecture.
 ms.service: azure-site-recovery
 ms.topic: faq
-ms.date: 04/29/2025
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 author: Jeronika-MS
 # Customer intent: "As a VMware administrator, I want to deploy the Azure Site Recovery replication appliance so that I can ensure effective disaster recovery of my virtual machines to Azure."
@@ -35,6 +35,8 @@ Number of disks | 2, including the OS disk (80 GB) and a data disk (620 GB)
 
 ### Software requirements
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 Component | Requirement
 --- | ---
 Operating system | Windows Server 2022. <br><br> - Windows Server 2019 appliances continue to receive software updates. <br> - Upgrading OS on existing Windows Server 2019 appliances to Windows Server 2022 isn't supported.
diff --git a/articles/site-recovery/site-recovery-active-directory.md b/articles/site-recovery/site-recovery-active-directory.md
@@ -5,7 +5,7 @@ description: This article describes how to implement a disaster recovery solutio
 author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 12/08/2025
+ms.date: 02/27/2026
 ms.author: v-gajeronika
 ms.custom: sfi-image-nochange
 # Customer intent: "As an IT administrator, I want to implement a disaster recovery solution for Active Directory and DNS using cloud services, so that I can ensure business continuity and minimize downtime during disruptions."
@@ -50,6 +50,8 @@ For the virtual machine that hosts the domain controller or DNS, in Site Recover
 
 ### Site-to-site protection
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 Create a domain controller on the secondary site. When you promote the server to a domain controller role, specify the name of the same domain that's being used on the primary site. You can use the **Active Directory Sites and Services** snap-in to configure settings on the site link object to which the sites are added. By configuring settings on a site link, you can control when replication occurs between two or more sites, and how often it occurs. For more information, see [Scheduling replication between sites](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731862(v=ws.11)).
 
 ### Site-to-Azure protection
diff --git a/articles/site-recovery/site-recovery-whats-new-archive.md b/articles/site-recovery/site-recovery-whats-new-archive.md
@@ -4,7 +4,7 @@ description: An archive for features and updates in the Azure Site Recovery serv
 ms.topic: overview
 ms.author: v-gajeronika
 ms.service: azure-site-recovery
-ms.date: 09/22/2025
+ms.date: 02/27/2026
 author: Jeronika-MS
 
 # Customer intent: "As a system administrator, I want to review the latest updates and feature enhancements for the disaster recovery service, so that I can optimize our organization's backup strategy and ensure compatibility with our systems."
@@ -370,6 +370,8 @@ For disaster recovery of Azure VMs to a secondary region, or on-premises VMware
 - Install the update and SHA-2 in accordance with the linked KB. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected.
 - Learn more about [SHA-2 upgrade and requirements](https://aka.ms/SHA-2KB).
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 **Operating system** | **Azure VM** | **VMware VM/physical machine**
 --- | --- | ---
 **Windows 2008 R2 SP1** | [Servicing stack update](https://support.microsoft.com/help/4490628)<br/> [SHA-2](https://support.microsoft.com/help/4474419)| [Servicing stack update](https://support.microsoft.com/help/4490628)<br/> [SHA-2](https://support.microsoft.com/help/4474419)
diff --git a/articles/site-recovery/transport-layer-security.md b/articles/site-recovery/transport-layer-security.md
@@ -17,6 +17,8 @@ Transport Layer Security (TLS) is an encryption protocol that keeps data secure
 
 If the machine is running earlier versions of Windows, ensure to install the corresponding updates as detailed below and make the registry changes as documented in the respective KB articles.
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 |Operating system  |KB article |
 |---------|---------|
 |Windows Server 2008 SP2 | <https://support.microsoft.com/help/4019276> |
diff --git a/articles/site-recovery/vmware-azure-reprotect.md b/articles/site-recovery/vmware-azure-reprotect.md
@@ -5,7 +5,7 @@ author: Jeronika-MS
 ms.service: azure-site-recovery
 ms.topic: how-to
 ms.author: v-gajeronika
-ms.date: 02/12/2026
+ms.date: 02/27/2026
 # Customer intent: As a system administrator, I want to reprotect VMware VMs after failover to Azure so that I can ensure data consistency and facilitate a seamless failback to the on-premises site.
 ---
 
@@ -15,6 +15,8 @@ After [failover](site-recovery-failover.md) of on-premises VMware VMs or physica
 
 ## Before you begin
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 1. Follow the steps in [this article](vmware-azure-prepare-failback.md) to prepare for reprotection and failback, including setting up a process server in Azure, and an on-premises master target server, and configuring a site-to-site VPN, or ExpressRoute private peering, for failback.
 2. Make sure that the the on-premises configuration server is running and connected to Azure. During failover to Azure, the on-premises site might not be accessible, and the configuration server might be unavailable or shut down. During failback, the VM must exist in the configuration server database. Otherwise, failback is unsuccessful.
 3. Delete any snapshots on the on-premises master target server. Reprotection won't work if there are snapshots.  The snapshots on the VM are automatically merged during a reprotect job.
diff --git a/articles/site-recovery/vmware-azure-troubleshoot-failback-reprotect.md b/articles/site-recovery/vmware-azure-troubleshoot-failback-reprotect.md
@@ -3,7 +3,7 @@ title: Troubleshoot failback in VMware VM disaster recovery with Azure Site Reco
 description: This article describes ways to troubleshoot failback and reprotection issues during VMware VM disaster recovery to Azure with Azure Site Recovery.
 ms.service: azure-site-recovery
 ms.topic: troubleshooting
-ms.date: 12/09/2025
+ms.date: 02/27/2026
 author: Jeronika-MS
 ms.author: v-gajeronika 
 
@@ -18,6 +18,8 @@ Failback essentially involves two main steps. For the first step, after failover
 
 ## Common issues
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 - If you perform a read-only user vCenter discovery and protect virtual machines, protection succeeds, and failover works. During reprotection, failover fails because the datastores can't be discovered. A symptom is that the datastores aren't listed during reprotection. To resolve this problem, you can update the vCenter credentials with an appropriate account that has permissions and then retry the job.
 - When you fail back a Linux virtual machine and run it on-premises, you can see that the Network Manager package has been uninstalled from the machine. This uninstallation occurs because the Network Manager package is removed when the virtual machine is recovered in Azure.
 - When a Linux virtual machine is configured with a static IP address and is failed over to Azure, the IP address is acquired from DHCP. When you fail over to on-premises, the virtual machine continues to use DHCP to acquire the IP address. Manually sign in to the machine, and then set the IP address back to a static address if necessary. A Windows virtual machine can acquire its static IP address again.
diff --git a/articles/site-recovery/vmware-azure-troubleshoot-push-install.md b/articles/site-recovery/vmware-azure-troubleshoot-push-install.md
@@ -3,7 +3,7 @@ title: Troubleshoot Mobility Service push installation with Azure Site Recovery
 description: Troubleshoot Mobility Services installation errors when enabling replication for disaster recovery with Azure Site Recovery.
 ms.service: azure-site-recovery
 ms.topic: troubleshooting
-ms.date: 12/09/2025
+ms.date: 02/27/2026
 author: Jeronika-MS
 ms.author: v-gajeronika 
 ms.custom: sfi-image-nochange
@@ -181,6 +181,8 @@ If connection is unsuccessful, please check whether all pre-requisites are met.
 
 After a connectivity check, verify if the File and Printer sharing service is enabled on your virtual machine. These settings are required to copy the Mobility agent to the source machine.
 
+[!INCLUDE [end-of-life-notes-windows-server-2008.md](./includes/end-of-life-notes-windows-server-2008.md)]
+
 For **Windows 2008 R2 and prior versions**:
 
 * To enable file and print sharing through Windows Firewall,
diff --git a/articles/site-recovery/vmware-physical-azure-support-matrix.md b/articles/site-recovery/vmware-physical-azure-support-matrix.md
diff --git a/articles/site-recovery/vmware-physical-azure-troubleshoot-process-server.md b/articles/site-recovery/vmware-physical-azure-troubleshoot-process-server.md
diff --git a/articles/site-recovery/vmware-physical-mobility-service-overview.md b/articles/site-recovery/vmware-physical-mobility-service-overview.md
