SFTP to Azure
SFTP access for your Azure Blob container
Keep Azure Blob Storage as the storage layer and add SFTP in front of it. Firepipe gives each person or system a standard SFTP login, maps that access to your container, and runs the gateway so you do not have to operate an SFTP server.
Your Azure storage · managed SFTP · per-user access
The short version
Firepipe connects a managed SFTP endpoint to an Azure Blob container you own. Users work through ordinary SFTP clients while file contents live at rest in Azure. Firepipe keeps no lasting copy of those contents and handles the SFTP service around your existing storage.
How it works
Connect one container, define user access, then use standard SFTP clients.
Connect your container
Provide a scoped Azure credential for the container. Firepipe stores it encrypted using an AES-256-GCM envelope under a KMS-managed key, decryptable only by the gateway. You can revoke the credential from Azure.
Define user access
Give each person or system a separate password or SSH-key login. Set a path prefix so each account sees only the part of the container it should use.
Use SFTP normally
Clients upload and download over SFTP. Firepipe maps those operations onto Blob Storage, while Azure remains the place where file contents are stored at rest.
Why use Firepipe with Azure
Keep storage in Azure
Firepipe is the SFTP layer, not another place to store the files. The container stays in your Azure subscription, and revoking its scoped credential locks Firepipe out.
Manage SFTP users separately
Create individual credentials, set path prefixes, and revoke access without sharing one SFTP account. Audit logs record login and file activity with user, path, byte count, source IP, timestamp, and status.
Meter transfer, not operations
Firepipe pricing is based on transfer, with no Firepipe per-operation or per-listing charge. Azure continues to bill your storage and cloud usage directly.
Simple, metered pricing
Metered transfer. No per-operation or per-listing fees from Firepipe.
Early-access pricing, these starting tiers may change. Your own cloud usage is billed by your provider, directly to you.
Frequently asked questions
What does "SFTP to Azure" mean?
It means putting an SFTP service in front of an Azure Blob Storage container. SFTP clients connect to Firepipe, and Firepipe translates their file operations to Blob Storage so you can keep using Azure as the backend.
Do my files stay in my Azure container?
Yes. File contents remain stored at rest in the Blob container you own. Firepipe streams them through the gateway during transfers and uses Azure as the storage backend.
Doesn’t Azure already have its own SFTP?
Azure Blob Storage offers an optional built-in SFTP feature on supported storage accounts. If that fits your requirements, it is a reasonable choice. Firepipe is an alternative when you want the same managed SFTP layer across Azure, Amazon S3, and Google Cloud, with Firepipe’s user management and exportable audit trail.
Can each user be limited to a folder?
Yes. Create a password or SSH-key credential for each user and jail it to a path prefix. Revoking a credential also ends any live session.
How does Firepipe access my container?
You provide a scoped Azure credential. Firepipe stores it encrypted using an AES-256-GCM envelope under a KMS-managed key, decryptable only by the gateway. The credential is revocable from your Azure account.
Put SFTP in front of Azure Blob
Use the container you already have, add SFTP users, and keep Blob Storage as the backend.
Start free