Box New File to SharePoint Governance

Overview

This flow centralizes Box content into governed Microsoft 365 storage. When a file is added to a watched Box folder, the flow downloads it, copies it into a structured SharePoint document library (organized by yyyy/MM), stamps governance metadata on the new item, and notifies the owner channel in Microsoft Teams.

Why it matters: content split between Box and Microsoft 365 is hard to govern. Mirroring Box files into SharePoint with consistent metadata, a retention label, and a unique governance ID brings that content under Microsoft Purview / SharePoint policy and gives the team a single, auditable record of every captured file.

Ships Off (demo).

Use Case

A team receives working files in Box (from external partners, scanners, or line-of-business apps) that must ultimately be governed inside SharePoint Online. Instead of manual drag-and-drop, this flow watches the Box folder and automatically mirrors each new file into the governed library, tagging it so records managers can apply retention and disposition policy.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Box	shared_box	OnNewFilesV2 GetFileContent
SharePoint	shared_sharepointonline	CreateFile ODataStylePatchFileItem
Microsoft Teams	shared_teams	PostMessageToConversation

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

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.

Create the SharePoint columns

Add single-line-text columns SourceSystem, BoxFileId, RetentionLabel, GovernanceId and a date/time CapturedDateTime so Update file properties can write them (use one-word internal names to avoid _x0020_ encoding).

Apply a real retention label

The standard SharePoint connector has no apply-retention-label op, so this flow records the label as a column. To apply an actual Purview label, add an HTTP call to the SharePoint REST SetComplianceTag endpoint (or Graph) with an AAD-OAuth connection.

Dedup

Skip files whose hash or Box ID already exists in the library (add a lookup + Condition before CreateFile).

Routing

Choose the destination library or subfolder by Box folder or file type - branch on the file name extension or path.

Two-way sync

Add an OnUpdatedFiles trigger to keep Box and SharePoint aligned after edits.

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.

concat(variables('varArchiveLibrary'), '/', formatDateTime(utcNow(),'yyyy/MM'))

triggerOutputs()?['body']

body('Create_File_In_SharePoint')?['ItemId']

guid()