Files
Jonathan Boniface bc84ee4df6
Some checks failed
check agents / check (push) Failing after 13s
Solution architecture outcome pattern: agent and its MCP servers
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate
stream from the individual and sub-agent patterns.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

5.6 KiB

name, metadata, description
name metadata description
azure-waf-cost-optimization
category
WellArchitectedFramework
Generates cost optimization guidance for Azure workloads based on the Cost Optimization pillar of the Azure Well-Architected Framework. Use when estimating, governing or reducing Azure spending, choosing pricing models, or balancing cost with other requirements.

Azure Well-Architected Framework skill for the Cost Optimization pillar

Overview

The Cost Optimization pillar seeks a good return on investment: spending that matches the value a workload delivers, while it still meets its functional and non-functional requirements. It is a continuous practice, tied to the wider governance of cost management.

Core principles

The recommendations below follow the published framework. Written for this agent from Microsoft's published design review checklist. Codes are Microsoft's.

Relevant products

The following are examples of products relevant to this pillar:

  • Visibility: Microsoft Cost Management, budgets, cost anomaly alerts, tags
  • Rates: Azure Reservations, Azure savings plans, Azure Hybrid Benefit, Spot Virtual Machines
  • Estimation: Azure Pricing Calculator
  • Data: Blob Storage access tiers and lifecycle management
  • Governance: Azure Policy, Azure Advisor

Workload assessment questions

Ask appropriate questions to understand the requirements and constraints of the workload and the organization. Choose from this list:

  • What is the monthly budget, and who owns it?
  • What drives the workload's cost, and how predictable is its usage?
  • Is the demand steady enough for a reservation or savings plan?
  • Which existing licenses could be reused?
  • What are the hours and availability needs of non-production environments?
  • How long must data be kept, and how often is it read?
  • How are costs tagged and attributed?
  • Which cost trade-offs against reliability or performance are acceptable?

Validation checklist

Use this checklist to evaluate the architecture against this pillar:

  • A cost model exists, with a budget and buffer.
  • Budgets and anomaly alerts are configured.
  • Resources are tagged so cost can be attributed.
  • Sizing is justified by usage, not guessed.
  • Autoscaling and scale-to-zero are used where demand varies.
  • Reservations, savings plans and Azure Hybrid Benefit are considered.
  • Non-production environments are reduced or shut down outside hours.
  • Storage lifecycle rules follow data retention needs.
  • Data transfer between regions is estimated.