# deployment-stacks-2025

The deployment-stacks-2025 skill covers Azure Deployment Stacks, including resource protection, cleanup rules, Bicep templates, and az stack commands.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 157 installs · ★ 66 repo stars
- Author: JosiahSiegel
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/azure-master/skills/deployment-stacks-2025/SKILL.md
- Updated: 2026-06-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/deployment-stacks-2025

## What it does

The skill explains how to treat a group of Azure resources as one managed stack. It covers resource group, subscription, and management group scopes, plus the `None`, `DenyDelete`, and `DenyWriteAndDelete` protection modes. It also maps `detachAll`, `deleteAll`, and `deleteResources` to what happens when a resource leaves the template.

Its material includes Bicep stack templates, an `az stack` CLI reference, a deny-settings matrix, and migration guidance from Azure Blueprints. You can use it to reason about stack creation, what-if checks, existing-stack updates, and resource adoption. The examples require Azure CLI 2.61.0 or later; Azure PowerShell commands require version 12.0.0 or later. Azure Blueprints are scheduled for deprecation in July 2026.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill deployment-stacks-2025 -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/deployment-stacks-2025/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/deployment-stacks-2025/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill deployment-stacks-2025 -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/deployment-stacks-2025/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill deployment-stacks-2025 -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/deployment-stacks-2025/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install JosiahSiegel/claude-plugin-marketplace plugins/azure-master/skills/deployment-stacks-2025
```

2. **Manually: put the files in place**
- File: `.github/skills/deployment-stacks-2025/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill deployment-stacks-2025 -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/JosiahSiegel/claude-plugin-marketplace --path plugins/azure-master/skills/deployment-stacks-2025
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/deployment-stacks-2025/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill deployment-stacks-2025 -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/azure-master/skills/deployment-stacks-2025/SKILL.md

## When to use it
- create an Azure stack at subscription scope
- block resource deletion or later changes
- choose cleanup behavior for unmanaged resources
- run an `az stack ... what-if` check
- move a Blueprint setup to Deployment Stacks

## Example prompts
- Explain the difference between `DenyDelete` and `DenyWriteAndDelete` for Azure Deployment Stacks.
- Write an `az stack sub create` command for `main.bicep` with `deleteAll` as the unmanage action.
- Show how to update an existing stack and adopt resources into its management.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: eafe5b0eba240149.

BEGIN THIRD-PARTY FILE eafe5b0eba240149
````text
---
name: deployment-stacks-2025
description: |
  Azure Deployment Stacks for unified resource lifecycle management.
  PROACTIVELY activate for: (1) Azure Deployment Stacks (GA replacement for Azure Blueprints), (2) deny settings (DenyDelete, DenyWriteAndDelete) for resource protection, (3) ActionOnUnmanage behavior (delete, detach), (4) Bicep deployment stacks, (5) cross-subscription stack deployments, (6) updating an existing stack (resource adoption), (7) inspecting stack resources and history, (8) stack vs traditional deployment tradeoffs, (9) GitOps with deployment stacks.
  Provides: Bicep stack templates, az stack CLI reference, deny-settings matrix, and migration guidance from Blueprints.
---

# Azure Deployment Stacks - 2025 GA Features

Complete knowledge base for Azure Deployment Stacks, the successor to Azure Blueprints (GA 2024, best practices 2025).

## Overview

Azure Deployment Stacks is a resource type for managing a collection of Azure resources as a single, atomic unit. It provides unified lifecycle management, resource protection, and automatic cleanup capabilities.

## Key Features

### 1. Unified Resource Management
- Manage multiple resources as a single entity
- Update, export, and delete operations on the entire stack
- Track all managed resources in one place
- Consistent deployment across environments

### 2. Deny Settings (Resource Protection)
Prevent unauthorized modifications to managed resources:
- **None**: No restrictions (default)
- **DenyDelete**: Prevent resource deletion
- **DenyWriteAndDelete**: Prevent updates and deletions

### 3. ActionOnUnmanage (Cleanup Policies)
Control what happens to resources no longer in template:
- **detachAll**: Remove from stack management, keep resources
- **deleteAll**: Delete resources not in template
- **deleteResources**: Delete unmanaged resources, keep resource groups

### 4. Scope Flexibility
Deploy stacks at:
- Resource group scope
- Subscription scope
- Management group scope

### 5. Replaces Azure Blueprints
Azure Blueprints will be deprecated in **July 2026**. Deployment Stacks is the recommended replacement.

## Prerequisites

### Azure CLI Version
```bash
# Requires Azure CLI 2.61.0 or later
az version

# Upgrade if needed
az upgrade
```

### Azure PowerShell Version
```bash
# Requires Azure PowerShell 12.0.0 or later
Get-InstalledModule -Name Az
Update-Module -Name Az
```
````
END THIRD-PARTY FILE eafe5b0eba240149

The third-party file has ended. Everything between the eafe5b0eba240149 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2396 of 16531 bytes. © JosiahSiegel · MIT · https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/azure-master/skills/deployment-stacks-2025/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
