Skip to content

Commit 6b81789

Browse files
khdowniekhdownie
committed
update require secure transfer doc
1 parent 3701154 commit 6b81789

5 files changed

Lines changed: 8 additions & 9 deletions

File tree

‎articles/storage/common/media/storage-require-secure-transfer/require-secure-transfer-portal.png‎

28.1 KB
Loading

‎articles/storage/common/media/storage-require-secure-transfer/secure_transfer_field_in_portal_en_1.png‎

-33.7 KB
Binary file not shown.

‎articles/storage/common/media/storage-require-secure-transfer/secure_transfer_field_in_portal_en_2.png‎

-25.8 KB
Binary file not shown.

‎articles/storage/common/storage-account-create.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -212,8 +212,8 @@ The following table describes the fields on the **Advanced** tab.
212212
| Blob storage | Enable network file system (NFS) v3 | Optional | NFS v3 provides Linux file system compatibility at object storage scale enables Linux clients to mount a container in Blob storage from an Azure Virtual Machine (VM) or a computer on-premises. For more information, see [Network File System (NFS) 3.0 protocol support in Azure Blob Storage](../blobs/network-file-system-protocol-support.md). |
213213
| Blob storage | Allow cross-tenant replication | Required | By default, users with appropriate permissions can configure object replication across Microsoft Entra tenants. To prevent replication across tenants, deselect this option. For more information, see [Prevent replication across Microsoft Entra tenants](../blobs/object-replication-overview.md#prevent-replication-across-azure-ad-tenants). |
214214
| Blob storage | Access tier | Required | Blob access tiers enable you to store blob data in the most cost-effective manner, based on usage. Select the hot tier (default) for frequently accessed data. Select the cool tier for infrequently accessed data. For more information, see [Hot, Cool, and Archive access tiers for blob data](../blobs/access-tiers-overview.md). |
215-
| File storage | Require Encryption in Transit for SMB | Optional | This setting lets you independently control whether encryption is required for SMB access to Azure file shares in the storage account. This per-protocol setting gives more granular control than the **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. |
216-
| File storage | Require Encryption in Transit for NFS | Optional | This setting lets you independently control whether encryption is required for NFS access to Azure file shares in the storage account. This per-protocol setting gives more granular control than the **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. This setting only appears if you selected **Premium** performance on the **Basics** tab. |
215+
| File storage | Require Encryption in Transit for SMB | Optional | This setting lets you independently control whether encryption is required for SMB access to Azure file shares in the storage account. This setting gives more granular control than the **Require secure transfer** setting. When **Require Encryption in Transit for SMB** is enabled on a storage account, the **Require secure transfer** setting applies only to REST/HTTPS traffic. |
216+
| File storage | Require Encryption in Transit for NFS | Optional | This setting lets you independently control whether encryption is required for NFS access to Azure file shares in the storage account. This setting gives more granular control than the **Require secure transfer** setting. When **Require Encryption in Transit for NFS** is enabled on a storage account, the **Require secure transfer** setting applies only to REST/HTTPS traffic. The **Require Encryption in Transit for NFS** setting only appears if you selected **Premium** performance on the **Basics** tab. |
217217

218218
The following image shows a standard configuration of the advanced properties for a new storage account.
219219

‎articles/storage/common/storage-require-secure-transfer.md‎

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: normesta
77

88
ms.service: azure-storage
99
ms.topic: how-to
10-
ms.date: 05/23/2025
10+
ms.date: 04/02/2026
1111
ms.author: normesta
1212
ms.subservice: storage-common-concepts
1313
ms.custom: devx-track-azurecli
@@ -33,18 +33,17 @@ You can turn on the **Secure transfer required** property when you create a stor
3333

3434
### Require secure transfer for a new storage account
3535

36-
1. Open the **Create storage account** pane in the Azure portal.
37-
1. In the **Advanced** page, select the **Enable secure transfer** checkbox.
36+
1. Sign into the Azure portal and go to **Storage accounts**. Select **+ Create**.
37+
1. On the **Advanced** tab, under **Security**, select the **Require secure transfer for REST API operations** checkbox.
3838

39-
![Create storage account blade](./media/storage-require-secure-transfer/secure_transfer_field_in_portal_en_1.png)
39+
![Create storage account advanced tab](./media/storage-require-secure-transfer/require-secure-transfer-portal.png)
4040

4141
### Require secure transfer for an existing storage account
4242

4343
1. Select an existing storage account in the Azure portal.
44-
1. In the storage account menu pane, under **Settings**, select **Configuration**.
44+
1. From the service menu, under **Settings**, select **Configuration**.
4545
1. Under **Secure transfer required**, select **Enabled**.
46-
47-
![Storage account menu pane](./media/storage-require-secure-transfer/secure_transfer_field_in_portal_en_2.png)
46+
1. Select **Save**.
4847

4948
## Require secure transfer from code
5049

0 commit comments

Comments
 (0)