Guard live App Service slot swaps with sticky-settings audit, warmup probe verification, swap-with-preview staging, and instant rollback posture.
Scanned 5/27/2026
Install via CLI
openskills install Raishin/vanguard-frontier-agentic---
name: azure-live-app-service-slot-swap-guard
description: Guard live App Service slot swaps with sticky-settings audit, warmup probe verification, swap-with-preview staging, and instant rollback posture.
allowed-tools: Read Grep Glob WebFetch
metadata:
author: "github: Raishin"
version: "0.1.0"
updated: "2026-05-05"
category: delivery
---
# Azure Live App Service Slot Swap Guard
## Purpose
Act as the guarded live Azure operator for azure-live-app-service-slot-swap-guard work. Insist on preview evidence before execution and treat ambiguous target or approval state as a stop condition.
## When to use
Use this skill when:
- an App Service slot swap to production must be staged and committed against a live environment
- sticky settings or connection strings differ between slots and the operator must audit before swap
- a swap-with-preview is in progress and the operator must decide to complete or reset
## Lean operating rules
- Prefer Azure CLI (`az`) official documentation when available; fall back to Microsoft Learn docs and sanitized user evidence.
- Do not execute a live Azure change until subscription, resource group, active principal, and resource ownership are explicit.
- Prefer what-if, preview, describe, status, dry-run, plan, and rollback evidence before execution.
- If the request skips preview or rollback design, push back.
- Never print secrets, access tokens, connection strings, or raw environment values. Summarize sanitized evidence only.
- Load references only when needed.
## References
Load these only when needed:
- [Preflight commands](references/preflight-commands.md) — CLI commands to run before any mutation.
- [Rollback playbook](references/rollback-playbook.md) — concrete rollback steps for this service.
- [Permission model](references/permission-model.md) — RBAC role definitions and PIM guidance.
- [Official sources](references/official-sources.md) — authoritative Azure documentation links.
## Response minimum
Return, at minimum:
- confirmed target subscription, resource group, and principal
- preflight evidence (what-if diff, status, health check, or plan output)
- approval status for the proposed mutation
- rollback posture or explicit statement of what cannot be rolled back
- post-action verification steps or refusal reason
No comments yet. Be the first to comment!