GCS BLOB PULL IN. AZURE BLOB OUT. NO SCRIPTS.

Move files from Google Cloud Storage to Azure Blob Storage

DocEvent polls your Google Cloud Storage bucket on a schedule with a service-account key and delivers each new blob into your Azure Blob Storage container. GCS-to-Azure transfer with no Pub/Sub, no scripts and a full audit trail.
From
GCS Blob Pull
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 GCS Blob Pull to Azure Blob routing works

Source

Google Cloud Storage

DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.
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 GCS Blob Pull

Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
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 GCS Blob Pull Azure Blob channel.
  • Bridge GCS pipeline output into an Azure data platform
  • Collect partner drops from a GCS bucket into your own container
  • Migrate from Google Cloud to Azure while both stay live
  • Cross-cloud delivery with no Pub/Sub or transfer-service setup
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the GCS Blob Pull or Azure Blob side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
Google Cloud Storage
Scheduled polling of a Google Cloud Storage bucket using a service-account key. Collects blobs from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No Pub/Sub, no bucket notifications, no event plumbing.
DocEvent checks your Google Cloud Storage bucket on a schedule and collects new blobs — no Pub/Sub or notifications needed.
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