Merge pull request #311204 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-02 12:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-app-configuration/reference-javascript-provider.md

@@ -317,7 +317,7 @@ import { ConfigurationMapFeatureFlagProvider, FeatureManager } from "@microsoft/
 // Create a feature flag provider which uses the configuration provider as feature flag source
 const ffProvider = new ConfigurationMapFeatureFlagProvider(appConfig);
 // Create a feature manager which will evaluate the feature flag
-const fm = new FeatureManager(ffProvider);
+const featureManager = new FeatureManager(ffProvider);
 
 import express from "express";
 const server = express();
@@ -522,4 +522,4 @@ To learn how to use the JavaScript configuration provider, continue to the follo
 To learn how to use the JavaScript feature management library, continue to the following documentation.
 
 > [!div class="nextstepaction"]
-> [JavaScript Feature Management](./feature-management-javascript-reference.md)
+> [JavaScript Feature Management](./feature-management-javascript-reference.md)

articles/migrate/how-to-upgrade-windows.md

@@ -1,8 +1,8 @@
 ---
 title: Upgrade Windows Operating System
 description: Learn how to upgrade Windows OS during migration.
-author: AnuragMehrotra
-ms.author: anuragm
+author: vijain
+ms.author: vijain 
 ms.manager: vijain
 ms.topic: how-to
 ms.date: 05/08/2025
@@ -19,6 +19,7 @@ This article describes how to upgrade Windows Server OS while migrating to Azure
 > - The upgrade feature only works for Windows Server Standard, Datacenter, and Enterprise editions.
 > - The upgrade feature doesn't work for non en-US language servers. 
 > - This feature doesn't work for a Windows Server with an evaluation license and needs a full license. If you have any server with an evaluation license, upgrade to full edition before starting migration to Azure.
+> - 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.
 
 ## Prerequisites 
 

articles/migrate/prepare-for-migration.md

@@ -54,6 +54,9 @@ Verify supported operating systems for migration:
 - Verify [Windows operating systems](https://support.microsoft.com/help/2721672/microsoft-server-software-support-for-microsoft-azure-virtual-machines) are supported in Azure.
 - Verify [Linux distributions](/azure/virtual-machines/linux/endorsed-distros) supported in Azure.
 
+> [!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.
+
 ## Review URL and port access
 
 Review which URLs and ports are accessed during migration.

articles/migrate/simplified-experience-for-azure-migrate.md

@@ -17,6 +17,9 @@ The simplified experience leverages an enhanced agent-based migration stack tail
 - **Broader OS support**: It enables migration of newer Linux distributions to Azure, expanding compatibility and allowing customers to benefit from the latest innovations in Linux technology.
 - **Modern replication appliance**: It utilizes Windows Server 2022 (WS2022) for the replication appliance, ensuring robust and up-to-date infrastructure.
 - **Unified OS support matrix**: This provides a consistent and streamlined approach to operating system support across migration workflows, simplifying planning and execution.
+
+> [!NOTE]
+> For the latest list of supported operating systems, including EOL or unsupported OSs such as CentOS, see [Azure support matrix](/azure/site-recovery/vmware-physical-azure-support-matrix).
   
 Overall, the upgraded stack equips customers with powerful tools to efficiently migrate newer Linux distributions, leverage modern Windows Server platform for replication, and benefit from a unified OS support framework, enhancing the entire migration journey to Azure.
 

articles/migrate/tutorial-migrate-physical-virtual-machines.md

@@ -47,6 +47,9 @@ Before you begin this tutorial, you should:
 - [Review](./agent-based-migration-architecture.md) the migration architecture.
 - [Review](../site-recovery/migrate-tutorial-windows-server-2008.md#limitations-and-known-issues) the limitations related to migrating Windows Server 2008 servers to Azure.
 
+> [!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.
+
 > [!NOTE]
 > If you're planning to upgrade your Windows operating system, Azure Migrate and Modernize might download the Windows SetupDiag utility for error details in case upgrade fails. Ensure that the VM created in Azure after the migration has access to [SetupDiag](https://go.microsoft.com/fwlink/?linkid=870142). If there's no access to SetupDiag, you might not be able to get detailed OS upgrade failure error codes but the upgrade can still proceed.
 

articles/storage/blobs/blobfuse2-what-is.md

@@ -21,7 +21,7 @@ BlobFuse provides several caching mechanisms, including file, metadata, and attr
 The BlobFuse project is [licensed under the MIT license](https://github.com/Azure/azure-storage-fuse/blob/main/LICENSE).
 
 > [!NOTE]
-> BlobFuse is the latest version of BlobFuse and has many significant improvements over BlobFuse v1. [BlobFuse v1](storage-how-to-mount-container-linux.md) support ends in September 2026. Migrate to BlobFuse v2 by using the provided [instructions](https://github.com/Azure/azure-storage-fuse/blob/main/MIGRATION.md).
+> BlobFuse v2 is the latest version of BlobFuse and has many significant improvements over BlobFuse v1. [BlobFuse v1](storage-how-to-mount-container-linux.md) support ends in September 2026. Migrate to BlobFuse v2 by using the provided [instructions](https://github.com/Azure/azure-storage-fuse/blob/main/MIGRATION.md).
 
 ## Key use cases