Release gates in Azure Pipelines are the correct mechanism for this scenario. They provide automated control over the promotion of a release from one stage to the next. Gates can be configured to periodically query external services, such as Azure Monitor, for health signals. In this case, a gate can be set up on the production stage to check for active performance-related alerts in the staging environment. If the gate detects alerts that violate the defined performance baseline, it will fail and prevent the deployment to production until the conditions are met.

A. an Azure Scheduler job: Azure Scheduler is a deprecated service for running jobs on a schedule; it is not an integrated control-flow mechanism within an Azure release pipeline.

B. a trigger: Triggers initiate a pipeline or a stage based on an event (e.g., a code commit or completion of a previous stage), but they do not perform conditional health checks to approve a deployment.

D. an Azure function: While an Azure Function can be invoked by a gate to perform a custom health check, the gate itself is the pipeline feature that controls the deployment flow based on the function's result.

1. Microsoft Docs

"Control deployments by using gates": This document explicitly states

"Gates allow automatic collection of health signals from external services and then promote the release when all the signals are successful... Before or after any stage

you can define release gates to query external health services. For example

a gate can query Azure Monitor for active alerts."

Source: Microsoft Learn

"Release gates and approvals overview"

Section: "Use gates to control your deployment".

2. Microsoft Docs

"Control deployments by using gates": This page details the available gate types

including "Query Azure Monitor alerts". It explains

"Use this gate to verify that there are no active alerts for your application. The gate succeeds if there are no alerts at the time of sampling." This directly addresses the scenario of checking performance baselines via alerts.

Source: Microsoft Learn

"Control deployments by using gates"

Section: "Gate types".

3. Microsoft Docs

"Release deployment control using gates": This article provides a use case: "A common use case for release gates is to ensure that the release is deployed to the next stage only if there are no blocking bugs in the product and no active incidents in the monitoring system." This aligns perfectly with preventing deployment due to negative performance impacts.

Source: Microsoft Learn

"Release deployment control using gates"

Section: "Why use gates?".