Merge pull request #54057 from staleycyn/patch-1

Content drift for the storage accounts module

Author: v-dirichards

learn-pr/wwl-azure/configure-storage-accounts/includes/2-implement-azure-storage.md

@@ -29,6 +29,13 @@ As you think about your configuration plan for Azure Storage, consider these pro
 
 - **Consider data accessibility**. Data in Azure Storage is accessible from anywhere in the world over HTTP or HTTPS. Microsoft provides SDKs for Azure Storage in various languages. You can use .NET, Java, Node.js, Python, PHP, Ruby, Go, and the REST API. Azure Storage supports scripting in Azure PowerShell or the Azure CLI. The Azure portal and Azure Storage Explorer offer easy visual solutions for working with your data.
 
+- **Consider SFTP support**. Blob Storage can use SFTP (SSH File Transfer Protocol), so you can keep using existing SFTP tools to move files directly to and from blobs. To use SFTP, enable hierarchical namespace (HNS). You can turn it on when you create the storage account (Advanced tab) or later under Settings → Configuration.
+  
+- **Consider NFSv3 protocol support**. Blob Storage can also be accessed using NFSv3, which lets Linux clients mount a container like an NFS share. NFSv3 can simplify migrations from Linux file workloads to Azure.
+
+- **Consider default authorization preferences**. In the Azure portal, you can enable **Default to Microsoft Entra authorization**. This authentication makes role-based access control (RBAC) the default instead of shared access keys, which can improve security.
+
+
 
 
 

learn-pr/wwl-azure/configure-storage-accounts/includes/4-determine-storage-account-kinds.md

@@ -12,12 +12,15 @@ General purpose Azure storage accounts have two basic [types](/azure/storage/com
 > You can't convert a Standard storage account to a Premium storage account or vice versa. You must create a new storage account with the desired type and copy data, if applicable, to a new storage account. All storage account types are encrypted by using Storage Service Encryption (SSE) for data at rest.
 
 
-| Storage account| Supported services| Recommended usage |
-| --- | --- | ---|
-| [**Standard** __general-purpose v2__](/azure/storage/common/storage-account-upgrade)| Blob Storage (including Data Lake Storage), Queue Storage, Table Storage, and Azure Files | Standard storage account for most scenarios, including blobs, file shares, queues, tables, and disks (page blobs). |
-| [**Premium** __block blobs__](/azure/storage/blobs/storage-blob-block-blob-premium)| Blob Storage (including Data Lake Storage) | Premium storage account for block blobs and append blobs. Recommended for applications with high transaction rates. Use Premium block blobs if you work with smaller objects or require consistently low storage latency. This storage is designed to scale with your applications. |
-| [**Premium** __file shares__](/azure/storage/files/storage-how-to-create-file-share)| Azure Files | Premium storage account for file shares only. Recommended for enterprise or high-performance scale applications. Use Premium file shares if you require support for both Server Message Block (SMB) and NFS file shares. |
-| [**Premium** __page blobs__](/azure/storage/blobs/storage-blob-pageblob-overview)| Page blobs only | Premium high-performance storage account for page blobs only. Page blobs are ideal for storing index-based and sparse data structures, such as operating systems, data disks for virtual machines, and databases. |
+| Storage account| Supported services| Redundancy options | Recommended usage |
+| --- | --- | ---| --- |
+| [**Standard** __general-purpose v2__](/azure/storage/common/storage-account-upgrade)| Blob Storage (including Data Lake Storage), Queue Storage, Table Storage, and Azure Files | LRS, GRS, RA-GRS, ZRS, GZRS, RA-GZRS | Standard storage account for most scenarios, including blobs, file shares, queues, tables, and disks (page blobs). |
+| [**Premium** __block blobs__](/azure/storage/blobs/storage-blob-block-blob-premium)| Blob Storage (including Data Lake Storage) | LRS, ZRS | Premium storage account for block blobs and append blobs. Recommended for applications with high transaction rates. Use Premium block blobs if you work with smaller objects or require consistently low storage latency. This storage is designed to scale with your applications. |
+| [**Premium** __file shares__](/azure/storage/files/storage-how-to-create-file-share)| Azure Files | LRS, ZRS | Premium storage account for file shares only. Recommended for enterprise or high-performance scale applications. Use Premium file shares if you require support for both Server Message Block (SMB) and NFS file shares. |
+| [**Premium** __page blobs__](/azure/storage/blobs/storage-blob-pageblob-overview)| Page blobs only | LRS only | Premium high-performance storage account for page blobs only. Page blobs are ideal for storing index-based and sparse data structures, such as operating systems, data disks for virtual machines, and databases. |
+
+> [!NOTE]
+> Administrators managing existing Azure subscriptions may encounter legacy storage account types such as General-purpose v1 (GPv1) and legacy BlobStorage accounts. Microsoft recommends upgrading legacy accounts to General-purpose v2 for access to all current capabilities. Upgrades are supported in-place via the Azure portal, Azure CLI, or PowerShell.
 
 > [!TIP]
 > Before continuing, consider working through the [*Create a storage account*](/training/modules/create-azure-storage-account/) training module. 

learn-pr/wwl-azure/configure-storage-accounts/includes/7-secure-storage-endpoints.md

@@ -22,5 +22,19 @@ Here are some points to consider about configuring service access settings:
 > [!Important]
 > Be sure to test the service endpoint and verify the endpoint limits access as expected.
 
+### Things to know about configuring private endpoints
+
+In addition to service endpoints, Azure Storage supports private endpoints for enhanced security and network isolation. Private endpoints are the recommended approach for production workloads requiring secure access.
+
+A private endpoint uses a private IP address from your virtual network to bring the Azure Storage service into your VNet. All traffic between your VNet and the storage service goes over the Microsoft backbone network, eliminating exposure to the public internet.
+
+**Key differences from service endpoints**
+
+- Private endpoints assign a private IP from your VNet to the storage account, keeping all traffic within the Microsoft backbone. Use private endpoints for production workloads requiring complete network isolation and compliance requirements
+  
+- Service endpoints keep the storage account on its public endpoint but restrict access to specific VNets and subnets. Use service endpoints for development scenarios or when you need simpler configuration with some public internet access
+
+
+
 > [!TIP]
 > Learn more with the [*Secure and isolate access to Azure resources by using network security groups and service endpoints*](/training/modules/secure-and-isolate-with-nsg-and-service-endpoints/) training module. This module has a sandbox where you can restrict access to Azure Storage by using service endpoints.

learn-pr/wwl-azure/configure-storage-accounts/index.yml

@@ -5,7 +5,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Configure Storage Accounts
   description: "Learn how to configure storage accounts, including replication and endpoints."
-  ms.date: 02/23/2026
+  ms.date: 03/23/2026
   author: wwlpublish
   ms.author: cynthist
   ms.topic: module