Skip to content

Commit 1018eee

Browse files
authored
Merge pull request #112252 from tamram/patch-86
Update storage-require-secure-transfer.md
2 parents 80817a5 + d545ccc commit 1018eee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

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

88
ms.service: storage
99
ms.topic: how-to
10-
ms.date: 12/12/2019
10+
ms.date: 04/21/2020
1111
ms.author: tamram
1212
ms.reviewer: fryu
1313
ms.subservice: common
@@ -21,7 +21,7 @@ When secure transfer is required, a call to an Azure Storage REST API operation
2121

2222
Connecting to an Azure File share over SMB without encryption fails when secure transfer is required for the storage account. Examples of insecure connections include those made over SMB 2.1, SMB 3.0 without encryption, or some versions of the Linux SMB client.
2323

24-
By default, the **Secure transfer required** property is enabled when you create a storage account in Azure portal. However, it is disabled when you create a storage account with SDK.
24+
By default, the **Secure transfer required** property is enabled when you create a storage account.
2525

2626
> [!NOTE]
2727
> Because Azure Storage doesn't support HTTPS for custom domain names, this option is not applied when you're using a custom domain name. And classic storage accounts are not supported.

0 commit comments

Comments
 (0)