EMAIL IN. AZURE BLOB OUT. NO SCRIPTS.
Save email attachments straight into Azure Blob Storage
Give partners an email address and every attachment is delivered into your Azure Blob Storage container automatically. DocEvent extracts each inbound attachment and writes it to the container and folder you choose - no mailbox polling, no scripts, fully audited.
From
Email
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 Email to Azure Blob routing works
SourceEmail
Email attachments are captured automatically via inbound email (Amazon SES).
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 Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
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 Email → Azure Blob channel.
- Land emailed invoices or orders in the container your pipeline reads
- Give suppliers an email drop-box that archives into Azure automatically
- Feed AI Document Intelligence or OCR workflows from inbound email
- Keep the original attachments in object storage you control
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Email or Azure Blob side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Email
Inbound email processed via Amazon SES. Attachments extracted and routed through the channel.
Email attachments are captured automatically via inbound email (Amazon SES).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 sources to Azure Blob
- Amazon S3 → Azure Blob
- HTTP Upload → Azure Blob
- AS2 → Azure Blob
- Filerouter (on-premise) → Azure Blob
- FTP Pull → Azure Blob
- SFTP Pull → Azure Blob
- S3 Compatible (pull) → Azure Blob
- GCS Blob Pull → Azure Blob
- Azure Blob Pull → Azure Blob
- Azure Data Lake Pull → Azure Blob
- Azure Files Pull → Azure Blob
- SharePoint → Azure Blob
- DocEvent Agent (on-prem) → Azure Blob