Merge pull request #300310 from normesta/network-content-improvement

Network content clean up

Author: prmerger-automator[bot]

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

@@ -7,9 +7,8 @@ author: normesta
 
 ms.service: azure-storage
 ms.topic: how-to
-ms.date: 06/17/2024
+ms.date: 05/23/2025
 ms.author: normesta
-ms.reviewer: fryu
 ms.subservice: storage-common-concepts
 ms.custom: devx-track-azurecli
 ms.devlang: azurecli
@@ -25,11 +24,6 @@ Azure Policy provides a built-in policy to ensure that secure transfer is requir
 
 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 or SMB 3.x without encryption. 
 
-> [!NOTE]
-> Because Azure Storage doesn't support HTTPS for custom domain names, this option isn't applied when you're using a custom domain name.
->
-> This secure transfer setting doesn't apply to TCP. Connections via NFS 3.0 protocol support in Azure Blob Storage using TCP, which isn't secured, will succeed.
-
 ## Require secure transfer in the Azure portal
 
 You can turn on the **Secure transfer required** property when you create a storage account in the [Azure portal](https://portal.azure.com). You can also enable it for existing storage accounts.