SFTP for Azure Blob Storage

SFTP for Azure
Blob Storage,

With the identity controls
you already expect.

The architecture Active path
SFTP.cloud architecture Partners and staff reach you over standard SFTP, FTPS or HTTPS. SFTP.cloud terminates the protocol, authenticates the user and enforces your rules. The Storage Connector runs next to your storage and opens an outbound, mutually authenticated connection to SFTP.cloud. Data moves between your storage and your user across the Connector's own channel and is never written to a disk SFTP.cloud owns. SFTP · FTPS · HTTPS OUTBOUND, MUTUALLY AUTHENTICATED There is no disk here for it to be written to. Partners and staff the client they already use SFTP.cloud terminates the protocol · authenticates the user enforces your rules Storage Connector you install it · you hold its keys Your storage Azure Blob container

Azure has native SFTP support for Blob Storage, and for simple cases it is a reasonable choice. It is worth knowing what it does and does not do before you commit to it.

Start your 14-day free trial

No credit card. No feature locks. Walk away by doing nothing.

See how it works

The comparison

Native SFTP is fine for simple cases.
Here is where it stops.

Azure native SFTP

Local users only
a password Azure generates or an SSH key
No MFAmultifactor authentication is not supported
Hourlycharge while enabled
  • Requires hierarchical namespace on the storage account, a decision you cannot reverse later
  • Local users "do not interoperate with other Azure Storage permission models such as RBAC and ABAC"
  • Microsoft recommends turning it off when you are not actively transferring

SFTP.cloud

Entra ID single sign-on
transfer accounts follow the identity provider you already run
MFAfor administrators and transfer accounts
One Gatea leaver in Entra ID is a leaver here
  • No hierarchical namespace requirement. No decision you cannot undo
  • Geo-fencing and automatic blocking of attacking addresses
  • Dual signed audit trails you can verify yourself with a tool you download
Start your 14-day free trial
No credit card required

How it works

How it works with Azure

1

Deploy a Storage Connector in your Azure subscription

Usually in the same region as your storage account. It authenticates to Blob Storage using credentials you create, held inside your subscription, which never reach us.

2

Your partners connect over SFTP, FTPS, FTPES or HTTPS

Files stream between your container and your partner through the Connector's outbound channel, and they are never written to a disk we own.

3

Optionally, encrypt the blobs themselves

With a key that stays on your Connector.

Features

What you get

  • Every protocol your partners use

  • Full identity integration

  • Automation running on your Connector, next to your data

  • A published price, from $2,400 a year, with no per-gigabyte charge

Start your 14-day free trial

See how it works →