Azure Standardization Guide
Contents
Before you design, build, and operate systems on Azure, we've organized what to decide first into chapters. Start with the contents, then read the chapters you need.
Chapter list
Click a chapter to open its explanation page with diagrams and checklists.
System-wide Architecture Design
SLA IaaS/PaaS cost review naming subscriptions network and
2Application Architecture Design
Languages, performance, availability, errors, app security, DevOps, API, fail-soft.
3Quality Management
Test and validate to confirm it works as designed before release.
4Security Architecture Design
Organize cloud security, auditing, governance, identity, and access rights.
5High-Reliability Design
Raise resiliency so the system can recover even when failures occur.
6Operations Design
Disaster recovery, backup, monitoring, incidents, request handling, maintenance.
7Configuration Management
Strengthen against change with change, capacity, and source-code management.
See the whole picture in one diagram
Grasp the whole through the flow of design, build, protect, run, and change.
Why standardize
The cloud offers great freedom, so without rules each person builds differently. Aligning standards makes reviews easier and the environment more robust.
Struggling with Azure design?
We can map this guide's content to your systems, starting from an initial consultation.