Technical & DevelopmentIntermediate
cloud-solution-architect
Design well-architected Azure cloud systems
Developer Setup
Setup & Installation
bash
npx skills add https://github.com/microsoft/skills --skill cloud-solution-architectnpx skills add https://github.com/microsoft/skills --skill cloud-solution-architectOr paste this URL into your assistant to install:
Overview
What This Skill Does
Turns the agent into a Cloud Solution Architect trained on Azure Architecture Center guidance. Covers architecture style selection, cloud design patterns, technology choices across Azure services, and Well-Architected Framework reviews. Use it when designing new systems, reviewing existing ones, or making Azure service decisions.
Application
When to use this Skill
- Configuring integration settings for custom agent workflows.
- Optimizing query execution and response latency in production.
- Developing clean, standard-compliant implementations for enterprise services.
- Troubleshooting connection timeouts and authentication handshakes.
- Monitoring API rate limits and execution pipelines programmatically.
Documentation
Show Skills.md file
Cloud Solution Architect
Overview
Design well-architected, production-grade cloud systems following Azure Architecture Center best practices. This skill provides:
- 10 design principles for Azure applications
- 6 architecture styles with selection guidance
- 44 cloud design patterns mapped to WAF pillars
- Technology choice frameworks for compute, storage, data, messaging
- Performance antipatterns to avoid
- Architecture review workflow for systematic design validation
Ten Design Principles for Azure Applications
| # | Principle | Key Tactics |
|---|---|---|
| 1 | Design for self-healing | Retry with backoff, circuit breaker, bulkhead isolation, health endpoint monitoring, graceful degradation |
| 2 | Make all things redundant | Eliminate single points of failure, use availability zones, deploy multi-region, replicate data |
| 3 | Minimize coordination | Decouple services, use async messaging, embrace eventual consistency, use domain events |
| 4 | Design to scale out | Horizontal scaling, autoscaling rules, stateless services, avoid session stickiness, partition workloads |
| 5 | Partition around limits | Data partitioning (shard/hash/range), respect compute & network limits, use CDNs for static content |
| 6 | Design for operations | Structured logging, distributed tracing, metrics & dashboards, runbook automation, infrastructure as code |
Lines 1 - 25 of 309
Recommendations