AZURE FILES PULL IN. GCS OUT. NO SCRIPTS.
Move files from an Azure Files share to Google Cloud Storage
DocEvent polls your Azure Files (SMB) share on a schedule and delivers each new file into your Google Cloud Storage bucket. The application keeps writing to the share; the files land in the bucket your pipelines read.
From
Azure Files 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 Files Pull to GCS routing works
Source
Azure Files
DocEvent checks your Azure Files share on a schedule and collects new files.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via Azure Files Pull
Scheduled polling of an Azure Files (SMB) share using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
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 Files Pull → GCS channel.
- Archive output from a lift-and-shift SMB application into GCS
- Feed a Google Cloud data lake from software that only writes to a file share
- Bridge a Windows file share to Google Cloud without sync tooling
- Collect share drops into object storage on a schedule
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 Files Pull or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Azure Files
Scheduled polling of an Azure Files (SMB) share using the storage account name and access key. Collects from a directory with filename pattern filtering and completed-file detection, then each collected file is deleted or moved to an archive folder.
DocEvent checks your Azure Files share on a schedule and collects new files.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
Related channel integrations
Other destinations from Azure Files Pull