Environment Variable Drift Detector

Overview

The Environment Variable Drift Detector is a scheduled governance flow that compares environment variable values across multiple Power Platform environments against a designated baseline. It identifies variables that have drifted (values differ) or are missing in target environments, logs findings to a Dataverse tracking table, and posts a styled HTML alert to Microsoft Teams.

Use Case

In multi-environment ALM setups (Dev → UAT → Prod), environment variables often drift out of sync due to manual edits, incomplete solution imports, or missed config steps. This flow automates weekly detection of drift and missing variables across target environments. The drift report helps platform admins catch config mismatches before they cause production issues.

The flow is ideal for teams that:

• Value drift: A variable exists in both environments but has different effective values (currentValue or defaultValue)
• Missing variables: A variable exists in the baseline but is entirely absent from a target environment

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.

Add more environments

Update flowlibs_MonitoredEnvironments with a comma-separated list of all environment IDs to scan (e.g., env-id-dev,env-id-uat,env-id-prod).

Change baseline

Set flowlibs_BaselineEnvironment to whichever environment represents your source of truth (typically Prod).

Adjust schedule

Edit the Recurrence trigger to run daily, bi-weekly, etc.

Filter specific variables

Add a Filter Array action after Parse Baseline Env Vars to only compare variables with a specific prefix.

Add email notification

Insert an Outlook SendEmailV2 action alongside the Teams post in the drift-found branch.

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.

coalesce(currentValue, defaultValue, '(not set)')

split(variables('varMonitoredEnvironments'), ',')

equals(item()?['properties']?['schemaName'], items('For_Each_Baseline_Var')?['properties']?['schemaName'])

not(equals(trim(items('For_Each_Target_Environment')), variables('varBaselineEnvironment')))

https://api.bap.microsoft.com/providers/Microsoft.BusinessAppPlatform/scopes/admin/environments/{envId}/environmentvariables?api-version=2021-02-01