Let Azure control your DevOps Pipelines
summary
The talk shows how Azure governance actually enforces pipeline behavior: use service principal defaulting to Contributor (don’t do that), create least-privilege Azure RBAC roles, block or allow deployments with release gates via Azure Monitor and Azure Policies, and gate releases on work‑item queries or SonarCloud scans. Demos wire Azure DevOps to Azure Alerts, REST APIs and Azure Functions; evaluations run every ≈5 minutes; the presenter’s prebuilt demos work and cites ~94 marketplace security extensions as a surprising count.
AI-written summary · about
chapters (12)
- 0:00Azure DevOps pipeline control
- 1:26Pipelines need governance
- 6:24Azure governance fundamentals
- 9:12Service principles setup
- 14:57Branch policies and approvals
- 20:29Pipeline approvals and checks
- 23:40Release Gates and validation
- 31:51Work item validation
- 34:38Azure Monitor alerts
- 40:22YAML pipelines governance
- 43:41Checks in YAML pipelines
- 45:05Q&A
related talks
01h 03mA lap around Azure Devops
27mBuilding powerful DevOps pipelines with Microsoft Azure DevOps
50mBest Practices for Securing CI/CD Pipelines
50mBest practices for securing CI/CD pipeline
46mAutomating Infrastructure as Code with Azure DevOps
50mCode repos and automated deployment
59mAzure DevOps: The Expert Panel
42mAzure DevOps security - Lessons learned