
Setting up Azure Storage SFTP is a straightforward process that can be completed in a few easy steps. You'll need to create a storage account and enable SFTP.
To create a storage account, go to the Azure portal and click on "Create a resource" > "Storage account." You can choose from several options, including Standard and Premium storage accounts.
Once you've created your storage account, you'll need to enable SFTP. To do this, navigate to the "Settings" tab and click on "SFTP" under the "Security" section. Make sure to enable the "SFTP" feature.
With SFTP enabled, you can now configure your storage account to use SFTP. This includes setting up a username and password, as well as configuring the SFTP protocol settings.
Expand your knowledge: Do I Need Onedrive on My Computer
Azure Storage SFTP Setup
To set up Azure Storage SFTP, you'll need to create a storage account. This involves logging in to the Azure Portal, clicking on +Create a resource, and selecting Microsoft Storage account resource. You'll also need to choose a subscription, resource group, and storage account name, which must be globally unique and no longer than 24 characters.
Consider reading: Do I Need Dropbox
The storage account must be in a region that currently supports SFTP, and you should select the Standard performance tier and Zone-redundant storage (ZRS) for redundancy. You'll also need to enable hierarchical namespace under the Data Lake Storage Gen2 subheading and click Enable SFTP.
You can create a new storage account using an Azure Bicep file, which can be deployed to a Resource Group. To enable SFTP on your storage account, navigate to the Storage account blade and click on SFTP. You'll then need to add a local user, choosing a username and authentication method such as SSH Password.
You can create up to 1000 local users, but there's no integration with Azure AD or other authentication services. You'll also need to create a top-level container and set its permissions, such as Read, Create, Delete, List, and Write.
Here's a summary of the steps to enable SFTP on your Azure Storage account:
- Log in to the Azure Portal
- Navigate to the Storage account blade
- Click on SFTP and click + Add local user
- Type in the username of the user you'd like to use
- Choose an authentication method, such as SSH Password
- Create a top-level container and set its permissions
- Set the Home directory for the user, if desired
Once you've completed these steps, you can test connectivity to your SFTP Azure Storage account using a tool such as Windows 11.
Curious to learn more? Check out: Nasuni
Storage Account Configuration
To configure your Azure Storage account for SFTP, you'll need to create a standard general-purpose v2 or premium block blob storage account. This account type must have its account redundancy option set to either locally-redundant storage (LRS) or zone-redundant storage (ZRS); GRS is not supported.
The hierarchical namespace feature of the account must be enabled for existing storage accounts. To enable this feature, you can follow the upgrade process outlined in the Azure documentation. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through port 22, which is used by SFTP.
Here are the key storage account configuration options to keep in mind:
- Account redundancy: LRS or ZRS (GRS is not supported)
- Performance tier: Standard (premium is supported but requires selecting Blob)
- Region: Only specific regions currently have SFTP support
- Redundancy: LRS or ZRS (for replication between availability zones)
Enabling Storage Account
To enable your Azure Storage account for SFTP, you'll need to create a standard general-purpose v2 or premium block blob storage account. This account type supports SFTP, and you can even enable it as you create the account.
The account redundancy option of the storage account should be set to either locally-redundant storage (LRS) or zone-redundant storage (ZRS); GRS is not supported. This means you have two options for data redundancy, but GRS is not an option.
Consider reading: Azure Storage Not Displaying
To enable hierarchical namespace, which is required for SFTP, you'll need to upgrade your Azure Blob Storage to Azure Data Lake Storage Gen2 capabilities. This will allow you to organize objects (files) into a hierarchy of directories and subdirectories.
If you're connecting from an on-premises network, make sure your client allows outgoing communication through port 22. SFTP uses port 22, so this is an important consideration.
Here are the steps to create an Azure Storage account for SFTP:
- Log in to the Azure Portal
- Click on +Create a resource
- Type in: Storage account and click on the Microsoft Storage account resource and click Create
- Select your Subscription and Resource Group
- Select your storage account name and Region
- Select your performance tier and Redundancy
- Click Next: Advanced
- Leave the Security options as-is and check: Enable hierarchical namespace
- Click Enable SFTP
- Click Next: Networking
- SFTP supports Private Endpoints, but you can also use a Public endpoint (all networks)
- Click Next: Data Protection
- Review your configuration and click Create
Networking Considerations
SFTP is a platform level service, so port 22 will be open even if the account option is disabled.
To ensure secure access, you may want to limit public access through configuration of a firewall, virtual network, or private endpoint.
These settings are enforced at the application layer, which means they aren't specific to SFTP and will impact connectivity to all Azure Storage Endpoints.
Audit tools may return TLS versions in addition to the minimum required version when run directly against the storage account endpoint.
For more information on firewalls and network configuration, see Configure Azure Storage firewalls and virtual networks.
Enforcing a minimum required version of Transport Layer Security (TLS) for requests to a storage account is also crucial for security.
If this caught your attention, see: Google Storage Area Network
Security and Authentication
You can authenticate with Azure Storage SFTP using a public-private key pair, which is the most common form of authentication for Secure Shell (SSH).
The private key should be kept secret and known only to the local user.
A public key is stored in Azure and is used to validate the user and key.
You can generate a new public-private key pair, use one already stored in Azure, or provide Azure the public key of an existing pair.
Each local user can have a maximum of 10 public keys.
Azure validates the message and checks that the user and key are recognized by the storage account.
Related reading: Where Are Onedrive Files Stored
Supported Clients and Limitations
Azure Storage SFTP has a wide range of supported clients, including AIX, AsyncSSH 2.1.0+, and Cyberduck 7.8.2+, among others.
The list of supported clients is not exhaustive and may change over time, so it's essential to check the official documentation for the most up-to-date information.
A fresh viewpoint: Connections - Oracle Fusion Cloud Applications
To connect using SFTP, you'll need to ensure that your client of choice is on the list of supported clients.
Here are some of the supported clients:
- AIX
- AsyncSSH 2.1.0+
- Axway
- curl 7.85.0+
- Cyberduck 7.8.2+
- edtFTPjPRO 7.0.0+
- FileZilla 3.53.0+
- Five9
- JSCH 0.1.54+
- libssh 0.9.5+
- MobaXterm v21.3
- Maverick Legacy 1.7.15+
- Moveit 12.7
- Mule 2.1.2+
- OpenSSH 7.4+
- paramiko 2.8.1+
- phpseclib 1.0.13+
- PuTTY 0.74+
- QualysML 12.3.41.1+
- RebexSSH 5.0.7119.0+
- Ruckus 6.1.2+
- Salesforce
- ssh2js 0.1.20+
- sshj 0.27.0+
- SSH.NET 2020.0.0+
- WinSCP 5.10+
- Workday
- XFB.Gateway
If you're experiencing trouble connecting, be sure to check the official documentation for known issues and limitations.
Known Supported Clients
If you're looking to connect to Azure Blob Storage using SFTP, you'll want to know which clients are supported. There are many options out there, but not all of them are compatible.
Here are some of the known supported clients:
- AIX
- AsyncSSH 2.1.0+
- Axway
- curl 7.85.0+
- Cyberduck 7.8.2+
- edtFTPjPRO 7.0.0+
- FileZilla 3.53.0+
- Five9
- JSCH 0.1.54+
- libssh 0.9.5+
- MobaXterm v21.3
- Maverick Legacy 1.7.15+
- Moveit 12.7
- Mule 2.1.2+
- OpenSSH 7.4+
- paramiko 2.8.1+
- phpseclib 1.0.13+
- PuTTY 0.74+
- QualysML 12.3.41.1+
- RebexSSH 5.0.7119.0+
- Ruckus 6.1.2+
- Salesforce
- ssh2js 0.1.20+
- sshj 0.27.0+
- SSH.NET 2020.0.0+
- WinSCP 5.10+
- Workday
- XFB.Gateway
Keep in mind that this list may not be exhaustive and can change over time. If you're having trouble connecting, be sure to check the Limitations and known issues with SSH File Transfer Protocol (SFTP) support for Azure Blob Storage.
Limitations
Limitations can be a real challenge when working with SFTP support for Azure Blob Storage.
Some limitations and known issues exist with SFTP support for Azure Blob Storage, so be sure to check the article for a complete list.
You can find a complete list of limitations and issues with SFTP support for Azure Blob Storage in the dedicated article.
Readers also liked: Does Dropbox Support Version Tracking
Pricing and Management
Azure Storage SFTP offers a pay-as-you-go pricing model, which means you only pay for the storage and data transfer you use. This can help you save costs compared to traditional storage solutions.
The pricing model is based on the amount of data stored and the number of requests made to the storage account. You can estimate your costs using the Azure Pricing Calculator.
Azure Storage SFTP also offers a free tier, which includes a certain amount of storage and data transfer, making it a great option for small projects or testing purposes.
Pricing and Billing
Enabling SFTP has an hourly cost, so it's essential to keep track of your usage to avoid unexpected charges. For the latest pricing information, check out Azure Blob Storage pricing.
To avoid passive charges, consider enabling SFTP only when you're actively using it to transfer data. This way, you can minimize the impact on your wallet.
All SFTP transactions get converted to Read, Write or Other transactions on your storage accounts. This includes all SFTP commands and API calls, which can add up quickly.
Transaction, storage, and networking prices for the underlying storage account apply. This means you'll need to factor these costs into your overall budget.
To learn more about the billing model, check out the full billing model for Azure Blob Storage.
Migrate Critical Apps to Cloud
Migrating business-critical applications to the cloud can be a game-changer for companies like SNCF Réseau, which manages over 28,000 kilometers of railway lines and handles 5 million passengers daily.
SNCF Réseau's experience shows that cloud migration can simplify data transfer workflows and reduce maintenance overhead.
SFTP servers enable secure communication between the cloud and on-premises data centers, as SNCF Réseau discovered when using SFTP support for Azure Blob Storage.
By leveraging a fully managed, highly available, and massively scalable SFTP PaaS, companies can focus on innovation rather than maintenance.
Troubleshooting and Setup
If you're having trouble setting up SFTP on your Azure storage account, start by checking that you've created a compatible storage account. You can have up to 1000 local users, but there's no integration into Azure AD, Active Directory, or other authentication services currently.
To troubleshoot common issues, make sure you're using the correct username and password. In this article, I used the username "lukeftpuser" and a password that was automatically generated by Azure. The password length was 89 characters, so be sure to copy and store it in a password vault.
If you're still having trouble, check your container permissions. You can set permissions for Read, Create, Delete, List, and Write on the container, not the folder. This means your users may have permissions to other folders in the same container if not managed appropriately.
Discover more: Reset Dropbox Password
Test Connectivity
Testing connectivity to your Azure Storage account is a crucial step in ensuring everything is set up correctly. You've already created a connection and now it's time to test it.
First, you'll need to test connectivity via SFTP. Congratulations, you've already done this and it's a good feeling to know it's working.
If you're using Windows, you can test connectivity using the command prompt. This is a great way to verify that everything is working as expected.
To test using SFTP from Windows, follow these steps:
- Make sure you have a copy of the Connection String and user password from the SFTP user account created earlier.
- Open Command Prompt
- Type in `sftp CONNECTIONSTRING` and press Enter.
- If you get a prompt to verify the authenticity of the host matches, type in `Yes` to add the storage account to your known host's list.
- Press Enter and paste in the copy of the Password that was generated for you earlier.
Once you've connected to SFTP using the command line, you can type in `?` to get a list of all the available commands. This will give you an idea of what you can do with SFTP, such as uploading files.
Setup
To set up SFTP on your Azure storage account, you'll need to log in to the Azure Portal and navigate to the Storage account you've created for SFTP.

You'll see the Storage account blade with various settings, including SFTP, which you'll need to click on to proceed. Next, click on the "+" Add local user button to create a new user.
You can have up to 1000 local users, but there's no integration with Azure AD, Active Directory, or other authentication services currently. I'll use the username "lukeftpuser" as an example.
You can use either SSH keys or passwords, and I'll be using passwords in this example. Select "SSH Password" and click Next to continue.
Now, you'll need to create a top-level container, which I'll name "ftp". You can also set the Public access level to Private (no anonymous access) if you prefer.
To set the permissions, you can give the user Read, Create, Delete, List, and Write access to the container. This is optional, but it's worth noting that these permissions are for the Container, not the folder.
You'll also need to set the Home directory, which is the directory that the user will be automatically mapped to. This is optional, but it's recommended to fill in the Home directory to avoid manual connections.
A different take: Block Level Storage

Azure will automatically create a new password for the account if you select Password as the authentication method. Make sure to copy and store this password in a password vault of some kind, as it's very long (89 characters in my example).
Here's a quick summary of the steps:
- Log in to the Azure Portal
- Navigate to the Storage account
- Click on SFTP and add a local user
- Create a top-level container
- Set permissions and Home directory
- Copy and store the generated password
Featured Images: pexels.com


