Skip to content

Commit 1aaa47d

Browse files
committed
add to storage account creation page
1 parent 046b6f4 commit 1aaa47d

3 files changed

Lines changed: 11 additions & 2 deletions

File tree

articles/storage/files/create-classic-file-share.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: How to create an Azure storage account and Azure classic file share
55
author: khdownie
66
ms.service: azure-file-storage
77
ms.topic: how-to
8-
ms.date: 01/30/2026
8+
ms.date: 04/02/2026
99
ms.author: kendownie
1010
ms.custom: devx-track-azurecli, references_regions, devx-track-azurepowershell
1111
# Customer intent: "As a cloud administrator, I want to create and manage Azure classic file shares using the Azure portal, PowerShell, or CLI, so that I can efficiently store and access data with configurable performance and redundancy options."
@@ -108,6 +108,15 @@ The **Blob storage** section applies only to Azure Blob storage use, even in Fil
108108
| Allow cross-tenant replication | Checkbox | Checked/unchecked | No | This is an Azure Blob storage only setting. This setting is always available, even for FileStorage storage accounts which can't contain Azure Blob storage. Checking this checkbox has no impact on Azure Files. |
109109
| Access tier | Radio button group | _Blob storage access tiers_ | No | This is an Azure Blob storage only setting. This setting is always available, even for FileStorage storage accounts which can't contain Azure Blob storage. Selecting an option has no impact on Azure Files. |
110110

111+
The **Azure Files** section allows you to choose whether to require encryption in transit for SMB and NFS file shares in the storage account, respectively. This per-protocol setting gives more granular control than the storage account-level **Secure transfer required** setting. When **Require Encryption in Transit** is enabled on a storage account, the **Secure transfer required** setting applies only to REST/HTTPS traffic.
112+
113+
:::image type="content" source="media/storage-how-to-create-file-share/require-encryption-in-transit.png" alt-text="A screenshot showing how to enable or disable the Require Encryption in Transit settings for SMB and NFS.":::
114+
115+
| Field name | Input type | Values | Applicable to Azure Files | Meaning |
116+
|-|-|-|-|-|
117+
| Require Encryption in Transit for SMB | Checkbox | Checked/unchecked | Yes | This setting lets you independently control whether encryption is required for SMB access to Azure file shares. |
118+
| Require Encryption in Transit for NFS | Checkbox | Checked/unchecked | Yes | This setting lets you independently control whether encryption is required for NFS access to Azure file shares. |
119+
111120
### Networking
112121

113122
The networking section allows you to configure networking options. These settings are optional for the creation of the storage account and can be configured later if desired. For more information on these options, see [Azure Files networking considerations](storage-files-networking-overview.md).

articles/storage/files/encryption-in-transit-for-nfs-shares.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ You can configure **Require Encryption in Transit for NFS** for a storage accoun
6868

6969
You can configure **Require Encryption in Transit for NFS** for a storage account in the following locations:
7070

71-
- On the **Security** tab when creating a new storage account in the Azure portal.
71+
- On the **Advanced** tab when creating a new storage account.
7272
- Under the **File service** section on the storage account overview blade.
7373
- Under **File share settings > Security** for an existing storage account.
7474

14.3 KB
Loading

0 commit comments

Comments
 (0)