Get started
SFTP / FTPS SERVER IN. AZURE BLOB OUT. NO SCRIPTS.

A hosted SFTP server that delivers uploads into Azure Blob Storage

DocEvent hosts an SFTP, SCP and FTPS server: senders upload to it with their own login and every completed upload is delivered into your Azure Blob Storage container, standard or Data Lake Gen2. Hosted SFTP-to-Azure ingestion with retries and a full audit trail - no VM to run.
From
SFTP / FTPS Server
To
Azure Blob
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.

How SFTP / FTPS Server to Azure Blob routing works

Source

SFTP / FTPS Server

DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
DocEvent Channel
routes · retries · logs
Destination

Azure Blob

Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.
1

File arrives via SFTP / FTPS Server

A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
2

Channel routes it

DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3

Delivered to Azure Blob

Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.

Common use cases

Real workflows that teams automate with a SFTP / FTPS Server → Azure Blob channel.
  • Receive partner deliveries over SFTP into a Blob container - flat or Data Lake Gen2
  • Works with any storage account - no hierarchical namespace required
  • Replace a self-managed SFTP VM in front of Azure Storage
  • Per-sender logins, an IP firewall and a full audit trail
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the SFTP / FTPS Server or Azure Blob side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
SFTP / FTPS Server
A hosted upload server, not a poll of yours: SFTP and SCP on port 22, explicit (AUTH TLS, port 21) and implicit (port 990) FTPS - cleartext FTP is refused. Usernames, passwords and SSH keys are managed in the console, with a per-service IP firewall and a browser uploader for people without a client. The login is upload-only: a file leaves the server the moment its upload completes, so nothing sits on it and there is nothing to poll.
DocEvent hosts an SFTP, SCP and FTPS server for you. Customers, partners and your own systems upload to it with their own login, and every completed upload enters the channel.
Destination:
Azure Blob
Delivery into an Azure Blob Storage container, authenticated with the storage account name and access key. One endpoint type covers both standard (flat-namespace) storage accounts and hierarchical-namespace accounts (Azure Data Lake Storage Gen2). Configurable folder (prefix) inside the container, and a built-in connection test that verifies the account, container and key before the first file flows.
Files are delivered into your Azure Blob Storage container - standard and Data Lake Gen2 accounts alike.
Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages

Related channel integrations

Other destinations from SFTP / FTPS Server
Other sources to Azure Blob
View all 154 channel integrations

You focus on integration,
we'll focus on delivery.

Get started for free