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>
5.6 KiB
name, metadata, description
| name | metadata | description | ||
|---|---|---|---|---|
| azure-waf-cost-optimization |
|
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.
-
Build financial responsibility (CO:01): Train people, encourage accountability and invest in tooling. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/create-culture-financial-responsibility
-
Maintain a cost model (CO:02): Estimate initial cost, run rate and ongoing cost, with a budget and buffer. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/cost-model
-
Collect and review cost data (CO:03): Capture daily cost, trends and forecasts, and automate alerts on thresholds and anomalies. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/collect-review-cost-data
-
Set guardrails (CO:04): Use release gates, policy, limits and access controls, automated where possible. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/set-spending-guardrails
-
Get the best rates (CO:05): Compare regions, tiers, consumption and commitment pricing, and license portability. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/get-best-rates
-
Align usage to billing increments (CO:06): Understand each meter and shape use to it. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/align-usage-to-billing-increments
-
Optimize components (CO:07): Remove or improve legacy, unneeded and underused features and resources. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-component-costs
-
Optimize environments (CO:08): Set availability, licensing and hours by environment, with strategic trade-offs outside production. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-environment-costs
-
Optimize flows (CO:09): Align each flow's cost with its priority. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-flow-costs
-
Optimize data (CO:10): Tier and retain data by priority, and review replication, backups and formats. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-data-costs
-
Optimize code (CO:11): Meet requirements with fewer or cheaper resources. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-code-costs
-
Optimize scaling (CO:12): Compare scaling configurations against the cost model and the limits of each scale unit. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-scaling-costs
-
Optimize personnel time (CO:13): Reduce effort on low-priority tasks without degrading outcomes. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/optimize-personnel-time
-
Consolidate (CO:14): Increase density, and use shared services outside the workload. Grounding document: https://learn.microsoft.com/azure/well-architected/cost-optimization/consolidation
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.