AZURE BLOB PULL IN. GCS OUT. NO SCRIPTS.

Move files from Azure Blob Storage to Google Cloud Storage

DocEvent polls a folder in your standard (flat) Azure Blob container on a schedule and delivers each new file into your Google Cloud Storage bucket. Azure-to-GCS transfer with no Event Grid, no scripts and a full audit trail.
From
Azure Blob Pull
To
GCS
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 Azure Blob Pull to GCS routing works

Source

Azure Blob

DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
DocEvent Channel
routes · retries · logs
Destination

Google Cloud Storage

Files are delivered into your Google Cloud Storage bucket.
1

File arrives via Azure Blob Pull

Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
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 GCS

Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.

Common use cases

Real workflows that teams automate with a Azure Blob Pull GCS channel.
  • Bridge Azure application output into a Google Cloud data platform
  • Collect partner drops from a Blob container into your own GCS bucket
  • Migrate from Azure to Google Cloud while both stay live
  • Cross-cloud delivery with no Event Grid or transfer tooling
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Azure Blob Pull or GCS side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Azure Blob
Scheduled polling of a standard Azure Blob Storage container using the storage account name and access key — the flat namespace, which is what a storage account has unless the hierarchical namespace was enabled at creation. Collects from a folder (prefix) with filename pattern filtering, then each collected file is deleted or copied to an archive prefix and removed. For hierarchical-namespace accounts use the Azure Data Lake source instead.
DocEvent checks a folder in your Azure Blob container on a schedule and collects new files. Works with standard (flat) storage accounts.
Destination:
Google Cloud Storage
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Files are delivered into your Google Cloud Storage bucket.
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