PR Detail Sync to Planner

Overview

This demo flow bridges GitHub and Microsoft Planner so project managers can see live pull request status inside their Planner board without leaving the tool. Once a day at 9:00 AM Eastern, the flow scans every task in a configured plan, looks for a GitHub PR URL in the task description, fetches the PR's current state from GitHub, and appends a status block (marked with an HTML comment sentinel) to the Planner task description. Subsequent runs update the block in place rather than stacking duplicates.

Use Case

Project managers live in Planner but engineers live in GitHub. When a PM asks "is this PR merged yet?" they shouldn't have to chase down a developer — the information should be in the card. This flow gives PMs a read-only view of PR health directly in the Planner task description: title, state (open/closed/merged), author, mergeable status, and last-update timestamp.

The flow is ideal for teams that:

• Mixed PM + engineering teams using Planner and GitHub.
• PMs who don't want to context-switch out of Planner to check PR status.
• Want PR status copied passively — no Planner workflow changes for engineers.
• Sentinel-based update so re-runs replace the block in place.

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.

Match different Git hosts

Change Init_varMatchTokenRepo to gitlab.com/ or dev.azure.com/ and swap the GitHub connector for the equivalent host's REST step.

Include check/review status

Add a GetChecksForRef call after Get_PR_Details and append to the status block.

Filter to a label

Add a Condition after Get_PR_Details that only updates when the PR has a tracked label.

Run faster

Switch the trigger to Hour or Minute. Watch GitHub rate limits (5000/hr with PAT, 60/hr unauthenticated).

Handle private repos

Use a PAT with repo scope. Store the token in a Dataverse Secret env var if you need rotation.

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.

and(contains(outputs('Compose_TaskDescription'), variables('varMatchTokenRepo')), contains(outputs('Compose_TaskDescription'), variables('varMatchTokenPull')))

substring(outputs('Compose_TaskDescription'), add(indexOf(outputs('Compose_TaskDescription'), variables('varMatchTokenRepo')), length(variables('varMatchTokenRepo'))))

first(split(first(split(outputs('Extract_PR_URL_Path'), ' ')), decodeUriComponent('%0A')))

if(equals(outputs('Get_Task_Details')?['body/description'], null), '', outputs('Get_Task_Details')?['body/description'])