Quick Notes206 words
Checks and approvals with YAML environments — quick notes
Checks and approvals — quick notes
| Fact | Detail |
|---|---|
| Who defines checks | The resource owner, not the pipeline author |
| Where they attach | Environments · service connections · agent pools · variable groups · secure files · repositories |
| Category order | 1 Static → 2 Pre-check approvals → 3 Dynamic → 4 Post-check approvals → 5 Exclusive lock |
| Static checks | Branch control · Required template · Evaluate artifact |
| Dynamic checks | Approval · Azure Function · REST API · Business Hours · Query Azure Monitor alerts |
| Within a category | Run in creation order |
| Timeout reached | Stage does not execute |
| Rejected approval | Terminal — stage does not execute |
| Enforce a mandatory template | Required template check |
| Prevent concurrent releases | Exclusive lock |
| Lock behavior omitted | runLatest — only the latest waiting run acquires the lock |
lockBehavior: sequential | Every waiting run acquires the lock in turn |
Traps
- Conditions are author-side; checks are resource-owner-side.
- Exclusive lock is last, not first.
- "Required template" is a check — the enforcement partner of
extends:.