PagerDuty Maintenance Window Scheduler

Overview

This flow keeps PagerDuty alerting quiet during planned work by syncing a Dataverse change calendar into PagerDuty maintenance windows. On an hourly schedule it reads approved change windows due to start soon, creates a matching PagerDuty maintenance window over the affected services (suppressing alerts for the duration), and posts a confirmation to Microsoft Teams. Windows that overlap an organisational change freeze are flagged for manual review instead of being auto-suppressed. Rows flagged for early cancellation have their PagerDuty window removed, and windows whose end time has passed are reconciled back to Completed.

Why it matters: Planned maintenance generates alerts that page on-call for nothing. Automatically suppressing the right services for the exact window keeps responders focused on real incidents and gives change managers a governed, auditable record of every suppression. Ships Off (demo); going live requires only connection authorization and environment-variable configuration.

Use Case

An operations team books maintenance in a Dataverse change calendar and wants PagerDuty alerting suppressed on the affected services automatically for each window - no manual maintenance-window creation, and no accidental suppression during a change freeze.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
PagerDuty	shared_pagerduty	POST /maintenance_windows DELETE /maintenance_windows/{id}
Microsoft Dataverse	shared_commondataserviceforapps	ListRecords UpdateRecord
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.

Service Map

Edit flowlibs_ServiceMap so each change-calendar System Key maps to the PagerDuty service ids it should suppress, e.g. {"billing-prod":["P123ABC"]}.

Change freeze

Set flowlibs_ChangeFreezeStart / End to your organisation's freeze period; overlapping windows are flagged in Teams instead of suppressed.

Look-ahead

Tune flowlibs_LookAheadHours (how far ahead of start the window is created).

Early cancel

Set a row's Status to Cancel Requested to have the flow DELETE its PagerDuty window before the scheduled end.

Different source

Swap the Dataverse ListRecords for a ServiceNow / Freshservice change-table read.

Auto-extend

Extend a window if the linked change is still in progress at its end time.

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(greaterOrEquals(ticks(items('Apply_To_Each_Window')?['flowlibs_start']), ticks(utcNow())), lessOrEquals(ticks(items('Apply_To_Each_Window')?['flowlibs_start']), ticks(addHours(utcNow(), int(variables('varLookAheadHours'))))))

@and(less(ticks(items('Apply_To_Each_Window')?['flowlibs_start']), ticks(variables('varFreezeEnd'))), greater(ticks(items('Apply_To_Each_Window')?['flowlibs_end']), ticks(variables('varFreezeStart'))))

@coalesce(json(variables('varServiceMap'))?[items('Apply_To_Each_Window')?['flowlibs_system']], json('[]'))

@body('Create_Maintenance_Window')?['maintenance_window']?['id']

@concat('flowlibs_status eq ''Scheduled'' and flowlibs_end lt ', utcNow('yyyy-MM-ddTHH:mm:ssZ'))

Customize & download