# azure-well-architected-framework

azure-well-architected-framework reviews Azure cloud architectures against the Well-Architected Framework pillars using proven Azure CLI templates.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 174 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/azure-well-architected-framework/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/azure-well-architected-framework

## What it does

This skill acts as an architecture reviewer across the five core WAF pillars: Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency. It bundles baseline principles, risk checklists, and concrete `az cli` commands directly into your coding assistant.

Workflows cover practical infrastructure tasks such as deploying virtual machines across availability zones, configuring managed identities to eliminate credentials from code, setting monthly consumption budgets, and configuring autoscale rules for Virtual Machine Scale Sets. Without the Azure CLI tool in your environment, running these operational snippets directly will fail.

It also aligns designs with Microsoft Cloud Adoption Framework principles and correlates findings with Azure Advisor recommendations, making it straightforward to catch configuration flaws early.

## Requirements
- Works with: Azure

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill azure-well-architected-framework -a claude-code
```

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

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill azure-well-architected-framework -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/azure-well-architected-framework/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill azure-well-architected-framework -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/azure-well-architected-framework/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/azure-well-architected-framework
```

2. **Manually: put the files in place**
- File: `.github/skills/azure-well-architected-framework/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill azure-well-architected-framework -a gemini-cli
```

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

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/azure-well-architected-framework/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add JosiahSiegel/claude-plugin-marketplace --skill azure-well-architected-framework -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/azure-well-architected-framework/SKILL.md

## When to use it
- review Azure architecture against WAF pillar checklists
- set up backup policies and availability zone redundancy
- apply cost optimization practices like reservations and budgets
- secure workloads using managed identities and network controls

## Example prompts
- Audit our Azure deployment plan against the Reliability pillar checklist
- Generate az cli commands to create a monthly budget with alerts at 80% and 100%
- Review this VMSS configuration for Performance Efficiency and horizontal autoscaling

## 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: fef882519b18f648.

BEGIN THIRD-PARTY FILE fef882519b18f648
````text
---
name: azure-well-architected-framework
description: |
  Azure Well-Architected Framework (WAF) for cloud architecture review.
  PROACTIVELY activate for: (1) Azure architecture review or design, (2) Reliability pillar (availability zones, geo-replication, backup/restore, RPO/RTO), (3) Security pillar (Zero Trust, encryption at rest/in transit, identity, network segmentation), (4) Cost Optimization pillar (rightsizing, reserved instances, savings plans, FinOps), (5) Operational Excellence pillar (IaC, observability, automation), (6) Performance Efficiency pillar (caching, autoscaling, async patterns), (7) Sustainability pillar, (8) WAF Reviews via the WAF Assessment Tool, (9) Microsoft Cloud Adoption Framework (CAF) alignment.
  Provides: pillar-by-pillar checklist, WAF assessment workflow, common antipatterns by pillar, and Azure Advisor mapping.
---

# Azure Well-Architected Framework

The Azure Well-Architected Framework is a set of guiding tenets for building high-quality cloud solutions. It consists of five pillars of architectural excellence.

## Overview

**Purpose**: Help architects and engineers build secure, high-performing, resilient, and efficient infrastructure for applications.

**The Five Pillars**:
1. Reliability
2. Security
3. Cost Optimization
4. Operational Excellence
5. Performance Efficiency

## Pillar 1: Reliability

**Definition**: The ability of a system to recover from failures and continue to function.

**Key Principles**:
- Design for failure
- Use availability zones and regions
- Implement redundancy
- Monitor and respond to failures
- Test disaster recovery

**Best Practices**:

**Availability Zones:**
```bash
# Deploy VM across availability zones
az vm create \
  --resource-group MyRG \
  --name MyVM \
  --zone 1 \
  --image Ubuntu2204 \
  --size Standard_D2s_v3

# Availability SLAs:
# - Single VM (Premium SSD): 99.9%
# - Availability Set: 99.95%
# - Availability Zones: 99.99%
```

**Backup and Disaster Recovery:**
```bash
# Enable Azure Backup
az backup protection enable-for-vm \
  --resource-group MyRG \
  --vault-name MyVault \
  --vm MyVM \
  --policy-name DefaultPolicy
````
END THIRD-PARTY FILE fef882519b18f648

The third-party file has ended. Everything between the fef882519b18f648 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 2144 of 10687 bytes. © JosiahSiegel · MIT · https://github.com/JosiahSiegel/claude-plugin-marketplace/tree/HEAD/plugins/azure-master/skills/azure-well-architected-framework/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
