Blog Post

Azure Architecture Blog
10 MIN READ

Cloud Native Platforms: Run

KishoreKumarPattabiraman's avatar
KishoreKumarPattabiraman
Icon for Microsoft rankMicrosoft
May 21, 2026

Part 2 of three on cloud-native platform engineering on Azure. This part covers the operational disciplines that decide whether a platform stays trusted in production: incident response, alert hygiene, change governance, cost discipline, and the team interface.

Audience: SREs (Site Reliability Engineers), platform engineers, engineering managers running production systems Reading time: 8 minutes Series: Cloud Native Platforms. Build, Run, Evolve. This i...
Published May 21, 2026
Version 1.0
apps & devops
armchair architects
infrastructure
well architected
KishoreKumarPattabiraman's avatar
KishoreKumarPattabiraman
Icon for Microsoft rankMicrosoft
May 23, 2026

This article is Part 2 of a three-part series. To explore the complete journey:

Part 1 — Build: Cloud Native Platforms: Build
Part 3 — Evolve: Cloud Native Platforms: Evolve

The series is structured as Build → Run → Evolve to reflect the natural progression of platform maturity.

If you are in the foundational stage or designing a new platform, start with Build.
If your platform is already live and your focus is on reliability, scalability, or cost optimization, continue with Run.
If you are evaluating advanced capabilities such as AI integration and long-term evolution, Evolve will be most relevant.