Merge pull request #18594 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-01 17:00 UTC

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

azure-local/includes/azure-local-end-of-support-banner-23h2.md

@@ -3,9 +3,9 @@ author: alkohli
 ms.author: alkohli
 ms.service: azure-local
 ms.topic: include
-ms.date: 07/22/2025
+ms.date: 07/31/2025
 ms.reviewer: alkohli
 ---
 
 > [!IMPORTANT]
-> Azure Stack HCI, version 23H2 OS (releases 2311.2 to 2509, OS version 25398.xxxx) will reach end of support on October 31, 2025. After this date, you won't receive monthly security and quality updates. Support requests will only be available for patching to a supported release.
+> Azure Stack HCI, version 23H2 OS (OS version 25398.xxxx) will reach end of support on October 31, 2025. After this date, you won't receive monthly security and quality updates. Support requests will only be available for patching to a supported release.

azure-local/manage/use-environment-checker.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 12/27/2024
+ms.date: 07/31/2025
 ---
 
 # Evaluate the deployment readiness of your environment for Azure Local
@@ -413,17 +413,15 @@ Network validator also checks storage connection, adapter driver readiness, and
 You provide the answer file JSON as the input for network validator cmdlet call. Or you can manually provide the individual parameters when running the validator cmdlet.
 
 > [!NOTE]
-> There is currently a limitation where the network validator can only be executed after the portal wizard has continued to the last step, just before the actual deployment starts.
-
-> [!NOTE]
-> You must run the network validator on the final hardware that you want to use for the Azure local instance deployment.
+> - There is currently a limitation where the network validator can only be executed after the portal wizard has continued to the last step, just before the actual deployment starts.
+>- You must run the network validator on the final hardware that you want to use for the Azure local instance deployment.
 
 ### Run the network validator
 
 To run the network validator locally on the Azure Local node with the answer file, use the following commands:
 
 ```powershell
-$allServers = "<ARRAY OF SERVERS' IP>" # you need to use IP for the connection 
+$allServers = @("<ServerIP1>", "<ServerIP2>")  # Replace with actual IP addresses 
 $userName = "<LOCALADMIN>" 
 $secPassWord = ConvertTo-SecureString "<LOCALADMINPASSWORD>" -AsPlainText -Force 
 $hostCred = New-Object System.Management.Automation.PSCredential($userName, $secPassWord) 

azure-managed-lustre/amlfs-prerequisites.md

@@ -2,7 +2,7 @@
 title: Prerequisites for Azure Managed Lustre file systems
 description: Learn about network and storage prerequisites to complete before you create an Azure Managed Lustre file system.
 ms.topic: overview
-ms.date: 01/17/2025
+ms.date: 07/31/2025
 author: pauljewellmsft
 ms.author: pauljewell
 ms.reviewer: mayabishop
@@ -21,7 +21,7 @@ This article explains prerequisites that you must configure before creating an A
 
 ## Network prerequisites
 
-Azure Managed Lustre file systems exist in a virtual network subnet. The subnet contains the Lustre Management Service (MGS) and handles all client interactions with the virtual Lustre cluster.
+Supply the virtual network and subnet for Azure Managed Lustre networking. You have full control of which network security measures you wish to apply, including which compute and other services can access Azure Managed Lustre. Ensure you follow the networking and security guidelines provided for Azure Managed Lustre. Include allowing required connections for essential services such as the Lustre protocol, engineering and diagnostic support, Azure Blob storage, and security monitoring. If your network settings disable one of the essential services, it leads to a degraded product experience or it reduces Microsoft’s support abilities.
 
 You can't move a file system from one network or subnet to another after you create the file system.
 
@@ -49,7 +49,7 @@ If you plan to use another resource to host your compute VMs in the same virtual
 
 ### Subnet access and permissions
 
-[Default outbound access for VMs](https://azure.microsoft.com/updates?id=default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access) will retire on September 30, 2025. After September 30, 2025, the following network settings must be in place to enable Azure Managed Lustre.
+By default, no specific changes need to be made to enable Azure Managed Lustre. If your environment includes restricted network or security policies, the following guidance should be considered:
 
 | Access type | Required network settings |
 |-------------|---------------------------|

azure-managed-lustre/auto-export.md

@@ -10,7 +10,7 @@ ms.reviewer: brianl
 # Intent: As an IT Pro, I need to be able to auto-export files from my Azure Managed Lustre file system to long-term Azure Blob Storage.
 # Keyword: 
 ---
-# Azure Managed Lustre Auto-Export (Preview)
+# Azure Managed Lustre auto-export (preview)
 
 The Auto-Export feature for Azure Managed Lustre is a capability that automatically synchronizes changes in your Azure Managed Lustre file system with a linked Azure Blob Storage Container. This feature ensures that new and modified files in the file system are reflected in the associated Blob Storage Container without manual intervention. This streamlines data management and improves synchronization for long-term storage.