Skip to content

Commit b64e013

Browse files
Merge pull request #18591 from ronhogue/ronh-2025-07-31-network-prereqs-update
update network pre-reqs
2 parents fdea16a + 95c1fd2 commit b64e013

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

azure-managed-lustre/amlfs-prerequisites.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Prerequisites for Azure Managed Lustre file systems
33
description: Learn about network and storage prerequisites to complete before you create an Azure Managed Lustre file system.
44
ms.topic: overview
5-
ms.date: 01/17/2025
5+
ms.date: 07/31/2025
66
author: pauljewellmsft
77
ms.author: pauljewell
88
ms.reviewer: mayabishop
@@ -21,7 +21,7 @@ This article explains prerequisites that you must configure before creating an A
2121

2222
## Network prerequisites
2323

24-
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.
24+
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.
2525

2626
You can't move a file system from one network or subnet to another after you create the file system.
2727

@@ -49,7 +49,7 @@ If you plan to use another resource to host your compute VMs in the same virtual
4949

5050
### Subnet access and permissions
5151

52-
[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.
52+
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:
5353

5454
| Access type | Required network settings |
5555
|-------------|---------------------------|

azure-managed-lustre/auto-export.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.reviewer: brianl
1010
# 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.
1111
# Keyword:
1212
---
13-
# Azure Managed Lustre Auto-Export (Preview)
13+
# Azure Managed Lustre auto-export (preview)
1414

1515
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.
1616

0 commit comments

Comments
 (0)