DOCEVENT AGENT (ON-PREM) IN. AZURE BLOB OUT. NO SCRIPTS.

Send files from a folder on your machine to Azure Blob Storage

The DocEvent Agent watches a folder on your own machine - picked from the web console - and each new file is delivered into your Azure Blob Storage container. No AzCopy, no cron scripts, outbound TLS only, full audit trail.
From
DocEvent Agent (on-prem)
To
Azure Blob
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
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 DocEvent Agent (on-prem) to Azure Blob routing works

Source

DocEvent Agent

A DocEvent Agent running on your own machine watches a folder and sends new files into 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 DocEvent Agent (on-prem)

Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
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 DocEvent Agent (on-prem) Azure Blob channel.
  • Upload ERP or instrument output to Azure with no tooling installed
  • Replace AzCopy cron scripts with a console-managed watched folder
  • Pick the watched folder remotely from the web console
  • Outbound TLS only - no storage keys on the machine
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the DocEvent Agent (on-prem) or Azure Blob side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
DocEvent Agent
Enroll the agent once and manage everything from the web console — browse the machine remotely to pick the watched folder, with no local config files. It connects outbound over TLS (no inbound ports) and confirms every transfer.
A DocEvent Agent running on your own machine watches a folder and sends new files into 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

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

Get started for free