Limitations and known issues with SSH File Transfer Protocol (SFTP) support for Azure Blob Storage (preview)
This article describes limitations and known issues of SFTP support for Azure Blob Storage.
Important
SFTP support is currently in PREVIEW and is available on general-purpose v2 and premium block blob accounts. Complete this form BEFORE using the feature in preview. Registration via 'preview features' is NOT required and confirmation email will NOT be sent after filling out the form. You can IMMEDIATELY access the feature.
After testing your end-to-end scenarios with SFTP, please share your experience via this form.
See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
Known unsupported clients
The following clients are known to be incompatible with SFTP for Azure Blob Storage (preview). See Supported algorithms for more information.
- Axway
- Five9
- Kemp
- Moveit
- Mule
- paramiko 1.16.0
- Salesforce
- SSH.NET 2016.1.0
- Workday
- XFB.Gateway
Note
The unsupported client list above is not exhaustive and may change over time.
Unsupported operations
| Category | Unsupported operations |
|---|---|
| ACLs | chgrp - change groupchmod - change permissions/modechown - change ownerput/get -p - preserving permissions |
| Resume operations | reget, get -a- resume downloadreput. put -a - resume upload |
| Random writes and appends | |
| Links | symlink - creating symbolic linksln - creating hard links |
| Capacity Information | df - usage info for filesystem |
| Extensions | Unsupported extensions include but are not limited to: fsync@openssh.com, limits@openssh.com, lsetstat@openssh.com, statvfs@openssh.com |
| SSH Commands | SFTP is the only supported subsystem. Shell requests after the completion of the key exchange will fail. |
| Multi-protocol writes | Random writes and appends (PutBlock,PutBlockList, GetBlockList, AppendBlock, AppendFile) are not allowed from other protocols on blobs that are created by using SFTP. Full overwrites are allowed. |
Authentication and authorization
Local users is the only form of identity management that is currently supported for the SFTP endpoint.
Azure Active Directory (Azure AD) is not supported for the SFTP endpoint.
POSIX-like access control lists (ACLs) are not supported for the SFTP endpoint.
Note
After your data is ingested into Azure Storage, you can use the full breadth of Azure storage security settings. While authorization mechanisms such as role-based access control (RBAC) and access control lists aren't supported as a means to authorize a connecting SFTP client, they can be used to authorize access via Azure tools (such Azure portal, Azure CLI, Azure PowerShell commands, and AzCopy) as well as Azure SDKS, and Azure REST APIs.
Account and container level operations are not supported for the SFTP endpoint.
Networking
To access the storage account using SFTP, your network must allow traffic on port 22.
When a firewall is configured, connections from non-allowed IPs are not rejected as expected. However, if there is a successful connection for an authenticated user then all data plane operations will be rejected.
There's a 4 minute timeout for idle or inactive connections. OpenSSH will appear to stop responding and then disconnect. Some clients reconnect automatically.
Security
- Host keys are published here. During the public preview, host keys may rotate frequently.
Integrations
Change feed and Event Grid notifications are not supported.
Network File System (NFS) 3.0 and SFTP can't be enabled on the same storage account.
Performance
For performance issues and considerations, see SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage.
Other
Special containers such as $logs, $blobchangefeed, $root, $web are not accessible via the SFTP endpoint.
Symbolic links are not supported.
ssh-keyscanis not supported.SSH and SCP commands, that are not SFTP, are not supported.
FTPS and FTP are not supported.
Troubleshooting
To resolve the
Failed to update SFTP settings for account 'accountname'. Error: The value 'True' is not allowed for property isSftpEnabled.error, ensure that the following pre-requisites are met at the storage account level:The account needs to be a general-purpose v2 and premium block blob accounts.
The account needs to have hierarchical namespace enabled on it.
To resolve the
Home Directory not accessible error.error, check that:The user has been assigned appropriate permissions to the container.
The container name is specified in the connection string for local users don't have a home directory.
The container name is specified in the connection string for local users that have a home directory that doesn't exist.
See also
- SSH File Transfer Protocol (SFTP) support for Azure Blob Storage
- Connect to Azure Blob Storage by using the SSH File Transfer Protocol (SFTP)
- Host keys for SSH File Transfer Protocol (SFTP) support for Azure Blob Storage
- SSH File Transfer Protocol (SFTP) performance considerations in Azure Blob storage
Povratne informacije
Pošalјite i prikažite povratne informacije za