Google Drive to OneDrive Continuous Sync

Overview

This flow mirrors a Google Drive folder into OneDrive for Business on a 15-minute schedule. Each run lists the source folder, copies new and changed files into OneDrive, and records every sync in a Dataverse sync-map ledger so files are never duplicated and only changed files are re-copied. A run summary is posted to Microsoft Teams.

Why it matters: Users who work in OneDrive need current copies of Google Drive content without manual downloads. A tracked, idempotent sync keeps the Microsoft-side copy aligned with the Drive source.

Status: Built and verified - Flow Checker 0 errors / 0 warnings. Ships Off; going live needs only connection authorization + environment-variable values.

Use Case

A team collaborates in a Google Drive folder, but downstream Microsoft 365 users live in OneDrive. This flow continuously mirrors the Drive folder into OneDrive, copying new files on first sight and re-copying files whose modified time has changed, while a Dataverse ledger prevents duplicate copies and supports change detection.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Google Drive	shared_googledrive	ListFolder GetFileContent
OneDrive for Business	shared_onedriveforbusiness	CreateFile
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.

Cadence

Change the Recurrence interval (default 15 minutes) to match how fresh the OneDrive copy must be; cap files per run for very large folders to avoid throttling.

Subfolders

ListFolder is non-recursive. To mirror a tree, add a recursive pattern (list each subfolder id) or set flowlibs_OneDriveRoot per subfolder. OneDrive CreateFile auto-creates intermediate folders from the target path.

Conflict policy

Current rule is newer-wins by Drive modified time. For changed files, swap CreateFile for OneDrive UpdateFile (by file id) to overwrite in place rather than risk a duplicate name.

Filters

Extend Filter Files Only to include/exclude by file type or size.

Two-way sync

Add a reverse OneDrive -> Drive branch if both sides must stay aligned.

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.

@equals(item()?['IsFolder'], false)

@{concat('flowlibs_googledrivefileid eq ''', items('Apply_to_each_File')?['Id'], '''')}

@or(equals(length(body('Lookup_Sync_Map')?['value']),0), not(equals(string(first(body('Lookup_Sync_Map')?['value'])?['flowlibs_modifiedtime']), string(items('Apply_to_each_File')?['LastModified']))))

@equals(length(body('Lookup_Sync_Map')?['value']),0)

@{concat(variables('varOneDriveRoot'),'/',items('Apply_to_each_File')?['Name'])}

@first(body('Lookup_Sync_Map')?['value'])?['flowlibs_drivesyncid']

Customize & download