Merge pull request #281425 from mikewill4/patch-74

[SFTP] Improve docs for blob naming and undelete support

Author: prmerger-automator[bot]

articles/storage/blobs/secure-file-transfer-protocol-known-issues.md

@@ -6,7 +6,7 @@ author: normesta
 
 ms.service: azure-blob-storage
 ms.topic: conceptual
-ms.date: 06/24/2024
+ms.date: 07/22/2024
 ms.author: normesta
 
 ---
@@ -53,6 +53,7 @@ To transfer files to or from Azure Blob Storage via SFTP clients, see the follow
 | Multi-protocol writes | Random writes and appends (`PutBlock`,`PutBlockList`, `GetBlockList`, `AppendBlock`, `AppendFile`)  aren't allowed from other protocols (NFS, Blob REST, Data Lake Storage Gen2 REST) on blobs that are created by using SFTP. Full overwrites are allowed.|
 | Rename Operations | Rename operations where the target file name already exists is a protocol violation. Attempting such an operation returns an error. See [Removing and Renaming Files](https://datatracker.ietf.org/doc/html/draft-ietf-secsh-filexfer-02#section-6.5) for more information.|
 | Cross Container Operations | Traversing between containers or performing operations on multiple containers from the same connection are unsupported.
+| Undelete | There is no way to restore a soft-deleted blob with SFTP. The `Undelete` REST API must be used.|
 
 ## Authentication and authorization
 
@@ -96,6 +97,8 @@ To learn more, see [SFTP permission model](secure-file-transfer-protocol-support
 
 - Only SSH version 2 is supported.
 
+- Avoid blob or directory names that end with a dot (.), a forward slash (/), a backslash (\), or a sequence or combination of the two. No path segments should end with a dot (.). For more information, see [Naming and Referencing Containers, Blobs, and Metadata](/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata).
+
 ## Blob Storage features
 
 When you enable SFTP support, some Blob Storage features will be fully supported, but some features might be supported only at the preview level or not yet supported at all.