PagerDuty Major-Incident Stakeholder Status Page

Overview

This flow keeps non-technical stakeholders informed during business-impacting PagerDuty incidents - without pulling responders off the incident to write status updates. On a schedule it pulls all PagerDuty incidents, keeps only the business-impacting ones, regenerates a branded HTML status page in SharePoint, and emails subscribed stakeholders whenever an incident's state changes (new, update, or a resolved all-clear). A Dataverse ledger remembers each incident's last known state so emails fire only on a genuine change.

Why it matters: During major incidents the response team should focus on the fix. Automating the public status page and the subscriber comms keeps executives, operations, and customers informed with consistent, timely messaging that is driven entirely from PagerDuty state. Built and verified (Flow Checker 0 errors / 0 warnings). Ships Off as a FlowLibs reference implementation - going live requires only authorizing the four connections and setting the environment variable values.

Use Case

A team needs reliable stakeholder/customer communications during major incidents, driven from PagerDuty, with no manual status writing. Business-impacting is configurable (by PagerDuty urgency and/or priority), the status page lives in SharePoint where it can be surfaced to a wider audience, and a subscriber list is emailed at each state transition. Typical audiences: Executives and Operations who need at-a-glance incident status, and customer-comms teams who maintain a status page.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
PagerDuty	shared_pagerduty	GetIncidents
SharePoint	shared_sharepointonline	CreateFile
Office 365 Outlook	shared_office365	SendEmailV2
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords CreateRecord

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.

Severity scoping

Adjust flowlibs_BusinessImpactUrgency and flowlibs_BusinessImpactPriorities to control what counts as business-impacting (e.g. only P1 to reduce noise).

Templated messaging

Edit the Compose Email Subject / Body and Compose Status Body actions for standard per-state phrasing (investigating / identified / monitoring / resolved).

Public status page

Surface the SharePoint document (or a Power Pages page reading the same library) to a public audience; point flowlibs_StatusPagePublicUrl at the externally reachable URL.

Polling cadence

Change the Recurrence interval (default 5 minutes) to balance freshness against run volume.

Add a Teams customer-comms channel

Add a PostMessageToConversation action inside the state-change branch to mirror the email into a comms channel.

Subscriber management

flowlibs_StatusStakeholderEmails is a simple semicolon list a business owner can edit; for larger audiences point it at a distribution list.

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.

@or(equals(toLower(coalesce(item()?['urgency'],'')), toLower(variables('varBusinessUrgency'))), contains(split(variables('varBusinessPriorities'),','), coalesce(item()?['priority']?['summary'],'__none__')))

@not(equals(toLower(coalesce(item()?['status'],'')),'resolved'))

@concat('flowlibs_incidentid eq ''', items('Foreach_Impacting_Incident')?['id'], '''')

@not(equals(outputs('Compose_Prev_Status'), items('Foreach_Impacting_Incident')?['status']))

@if(equals(toLower(items('Foreach_Impacting_Incident')?['status']),'resolved'),'[RESOLVED] ', if(empty(outputs('Compose_Prev_Status')),'[NEW INCIDENT] ','[UPDATE] '))

Customize & download