Google Drive Backup to Azure Blob

Overview

This flow provides an off-platform, verifiable backup of Google Drive content into Azure Blob Storage. On a nightly schedule it lists a configured Google Drive folder, backs up every new or changed file into a date-organized Blob path, writes a JSON manifest (per-file integrity record) to the container, and posts a run summary (counts + correlation id) to Microsoft Teams. Idempotency and change-detection are handled by a Dataverse ledger keyed on the Drive file id + ETag, so unchanged files are skipped and failures are recorded for retry.

Why it matters: A single-platform copy is a risk. A dated, manifested Blob backup with a Dataverse ledger gives recoverable, auditable, incremental off-site protection.

As-built status: Built and verified - Flow Checker 0 errors / 0 warnings (in-designer); ships Off.

Use Case

IT Admins and Developers want a nightly, incremental, verifiable backup of a critical Google Drive folder to Azure Blob, with an integrity manifest and a Teams status report - without re-copying unchanged files.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Drive	shared_googledrive	ListFolder GetFileContent
Azure Blob Storage	shared_azureblob	CreateFile_V2
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord UpdateRecord
Microsoft Teams

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Multiple folders

Make flowlibs_GDriveBackupFolderId a comma list and wrap the list/loop in an outer Foreach, or clone the List action per folder.

True checksums

Add an Azure Function (or Drive md5Checksum via HTTP) after Get_Drive_File_Content and store the hash alongside the ETags in the manifest/ledger.

Immutability / ransomware resilience

Enable WORM (immutable blob) + versioning on the container; add lifecycle policies for per-folder retention.

Restore flow

Build a companion flow that reads a manifest and restores files from Blob back to Drive/SharePoint.

Recursive folders

Drive ListFolder is non-recursive; add a sub-folder walk if nested backup is needed.

Schedule

Adjust the Recurrence trigger (frequency/hour) to the desired backup window.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@formatDateTime(utcNow(),'yyyy/MM/dd')

@concat(variables('varBlobContainer'),'/',variables('varDatePath'))

@equals(items('For_Each_Drive_Item')?['IsFolder'], false)

@or(equals(length(coalesce(body('Lookup_Existing_Ledger_Row')?['value'], json('[]'))),0), not(equals(first(body('Lookup_Existing_Ledger_Row')?['value'])?['flowlibs_driveetag'], items('For_Each_Drive_Item')?['ETag'])))

@concat('manifest-',formatDateTime(utcNow(),'yyyy-MM-dd'),'-',variables('varCorrelationId'),'.json')

@guid()

Customize & download