Merge pull request #227367 from normesta/normesta-reg-updates-11

Updating a note as per CSS recommendation

Author: prmerger-automator[bot]

articles/storage/blobs/network-file-system-protocol-support-how-to.md

@@ -7,7 +7,7 @@ author: normesta
 ms.subservice: blobs
 ms.service: storage
 ms.topic: conceptual
-ms.date: 06/21/2021
+ms.date: 02/14/2023
 ms.author: normesta
 ms.reviewer: yzheng
 ms.custom: devx-track-azurepowershell
@@ -30,6 +30,9 @@ Currently, the only way to secure the data in your storage account is by using a
 
 To secure the data in your account, see these recommendations: [Network security recommendations for Blob storage](security-recommendations.md#networking).
 
+> [!IMPORTANT]
+> The NFS 3.0 protocol uses ports 111 and 2048. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through those ports. If you have granted access to specific VNets, make sure that any network security groups associated with those VNets don't contain security rules that block incoming communication through those ports.
+
 ## Step 3: Create and configure a storage account
 
 To mount a container by using NFS 3.0, you must create a storage account. You can't enable existing accounts.

articles/storage/blobs/network-file-system-protocol-support.md

@@ -7,7 +7,7 @@ author: normesta
 ms.subservice: blobs
 ms.service: storage
 ms.topic: conceptual
-ms.date: 01/24/2023
+ms.date: 02/14/2023
 ms.author: normesta
 ms.reviewer: yzheng
 ---
@@ -80,7 +80,7 @@ A client can connect over a public or a [private endpoint](../common/storage-pri
   This can be done by using [VPN Gateway](../../vpn-gateway/vpn-gateway-about-vpngateways.md) or an [ExpressRoute gateway](../../expressroute/expressroute-howto-add-gateway-portal-resource-manager.md) along with [Gateway transit](/azure/architecture/reference-architectures/hybrid-networking/vnet-peering#gateway-transit).
 
 > [!IMPORTANT]
-> If you're connecting from an on-premises network, make sure that your client allows outgoing communication through ports 111 and 2048. The NFS 3.0 protocol uses these ports.
+> The NFS 3.0 protocol uses ports 111 and 2048. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through those ports. If you have granted access to specific VNets, make sure that any network security groups associated with those VNets don't contain security rules that block incoming communication through those ports. 
 
 <a id="azure-storage-features-not-yet-supported"></a>
 

articles/storage/blobs/soft-delete-blob-overview.md

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: conceptual
-ms.date: 02/06/2023
+ms.date: 02/14/2023
 ms.author: normesta
 ms.subservice: blobs
 ---
@@ -53,7 +53,7 @@ Version 2017-07-29 and higher of the Azure Storage REST API support blob soft de
 
 ### How deletions are handled when soft delete is enabled
 
-When blob soft delete is enabled, deleting a blob marks that blob as soft-deleted. No snapshot is created. When the retention period expires, the soft-deleted blob is permanently deleted.
+When blob soft delete is enabled, deleting a blob marks that blob as soft-deleted. No snapshot is created. When the retention period expires, the soft-deleted blob is permanently deleted. In accounts that have a hierarchical namespace, the access control list of a blob is unaffected and will remain in tact if the blob is restored.
 
 If a blob has snapshots, the blob can't be deleted unless the snapshots are also deleted. When you delete a blob and its snapshots, both the blob and snapshots are marked as soft-deleted. No new snapshots are created.
 
@@ -82,7 +82,7 @@ For premium storage accounts, soft-deleted snapshots don't count toward the per-
 
 ### Restoring soft-deleted objects
 
-You can restore soft-deleted blobs or directories (in a hierarchical namespace) by calling the [Undelete Blob](/rest/api/storageservices/undelete-blob) operation within the retention period. The **Undelete Blob** operation restores a blob and any soft-deleted snapshots associated with it. Any snapshots that were deleted during the retention period are restored.
+You can restore soft-deleted blobs or directories (in a hierarchical namespace) by calling the [Undelete Blob](/rest/api/storageservices/undelete-blob) operation within the retention period. The **Undelete Blob** operation restores a blob and any soft-deleted snapshots associated with it. Any snapshots that were deleted during the retention period are restored. In accounts that have a hierarchical namespace, the access control list of a blob is restored along with the blob.
 
 In accounts that have a hierarchical namespace, the **Undelete Blob** operation can also be used to restore a soft-deleted directory and all its contents. If you rename a directory that contains soft deleted blobs, those soft deleted blobs become disconnected from the directory. If you want to restore those blobs, you'll have to revert the name of the directory back to its original name or create a separate directory that uses the original directory name. Otherwise, you'll receive an error when you attempt to restore those soft deleted blobs. You also cannot restore a directory or a blob to a filepath that has a directory or blob of that name already there. For example, if you delete a.txt (1) and upload a new file also named a.txt (2), you cannot restore the soft deleted a.txt (1) until the active a.txt (2) has either been deleted or renamed. You cannot access the contents of a soft-deleted directory until after the directory has been undeleted.