User Profile Photo Sync to SharePoint

Overview

A scheduled cloud flow that periodically pulls every Office 365 user's profile photo and uploads it to a central SharePoint document library. The library becomes the single, predictable source of user photos for custom apps, Power Pages directories, intranet people pickers, and any other surface that needs portrait images without hitting Microsoft Graph at runtime.

Use Case

Custom apps and Power Pages sites that need to render user photos run into the same wall: the Office 365 Users connector's UserPhoto action requires the calling user's permission to read every target user, and Microsoft Graph rate-limits photo endpoints aggressively when a popular surface fans out to many users. Caching photos in a SharePoint image library breaks both constraints — the app now reads files from a familiar SharePoint library, the flow handles the Graph traffic on a schedule, and IT controls refresh cadence by tweaking the recurrence trigger.

Typical consumers: a Power Apps employee directory, a SharePoint org chart web part backed by REST, a Power Pages staff profile site, and any HR onboarding flow that needs a headshot reference.

The flow is ideal for teams that:

• Power Apps employee directories that render user photos without hitting Graph at runtime
• SharePoint org chart web parts backed by REST that key off a predictable image library
• Power Pages staff profile sites needing cached portraits for anonymous visitors
• HR onboarding flows that need a stable headshot reference per user
• IT teams that want to control photo refresh cadence and avoid Graph throttling on popular surfaces

Flow Architecture

Environment Variables

Connectors & Connections

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.

Change the schedule

Edit the Recurrence_Daily_8AM trigger. For weekly off-hours runs, set frequency: "Week", interval: 1, and pick a weekDays value plus an hours value that fits your maintenance window. For more frequent refresh during a migration, switch to frequency: "Hour" with interval: 4 — but expect Graph throttling above ~1 photo/sec sustained.

Scope which users sync

Update the flowlibs_UserSearchFilter env var. SearchUserV2 accepts a single search term that matches against display name, mail, and userPrincipalName. To scope by department, surname, or office, set this to the value you want to match (for example Sales or Smith). For an everyone sync, leave it empty — the flow already passes isSearchTermRequired: false. To go beyond 100 users, add a paging loop using the skipToken query param of SearchUserV2.

Change the destination library

Update flowlibs_UserPhotoLibraryName. The Init_varFolderPath action automatically converts the library display name into the server-relative path SharePoint actually uses (replacing - with to match SharePoint's path-encoding behavior). If you point at a library on a different site, also update flowlibs_SharePointSiteURL.

Change the file naming convention

The Upload_Photo_To_SharePoint

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('/', replace(variables('varLibraryName'), ' - ', '  '))

@items('Apply_to_each_User')?['id']

@{items('Apply_to_each_User')?['userPrincipalName']}.jpg

@body('Get_User_Photo')

@string(length(coalesce(outputs('Search_For_Users')?['body/value'], createArray())))