DevOps at Microsoft: Our Internal Transformation Story
summary
Microsoft claims it cuts a three‑year release cycle down to three‑week sprints by changing team structure and CI/CD practices, running Azure DevOps and GitHub for source and pipelines, using feature flags for ringed rollouts and rollback, and enforcing green builds that pass 50,000 unit tests before release. Concrete metrics: ~85,000 deployments/day, ~4.5M builds/month, millions of work‑items tracked. Teams reorganize into product‑centric feature teams with production‑first telemetry, OKRs focused on customer value, and security baked into every commit.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 2:00Defining DevOps
- 4:26DevOps under Satya Nadella
- 7:34From TFS to Azure DevOps
- 9:40Customer feedback in DevOps
- 11:02Harmful KPIs for engineers
- 13:07Feature-based team structure
- 18:22Outage transparency
- 20:07Testing strategies
- 21:53Feature flags and deployments
- 22:35Security in DevOps
- 23:38Azure DevOps multi-language
- 26:25Azure Boards Agile
- 28:12GitHub vs Azure DevOps
- 28:52DevOps resources
- 29:57Resistance to DevOps
- 32:27Teams owning both development and operations
- 34:35Team autonomy
- 36:19Standardization vs innovation
- 37:42User feedback in dev
- 39:05OKRs at all levels
- 40:49Azure’s DevOps role
- 42:55Q&A
related talks
49mOur DevOps journey – Microsoft’s internal transformation story
01h 02mBuild a DevOps Culture: Microsoft's Journey to adopt an Agile Mindset and DevOps culture
37mFrom Waterfall to Agile
44m#Devops Journey
07mWhat we learned moving 65,000 Microsofties to DevOps...
01h 02mEffective DevOps for Organizations
53mKeynote: Enterprise transformation (and you can too)
01h 01mPragmatic DevOps - How and Why