Securing organizations pipelines and integrations in Azure DevOps Q&A
summary
Demos show three tenant policies that admins can enable now: restrict global personal access tokens, block creation of full‑scope PATs, and enforce a maximum PAT lifespan (example default 30 days) with allow‑list exceptions. A sample Azure Function moves from a long‑lived PAT to a managed identity migration and gets 60‑minute AAD tokens. Pipelines gain an audit‑only mode for queue‑time variables (audit log CSV export), and Azure service connections can use workload identity federation so no secrets are stored.
AI-written summary · about
chapters (5)
- 0:00Session introduction
- 4:46Personal access token policy
- 12:02Managed identity integration
- 21:34Pipeline and secret security
- 35:22Audience Q&A
related talks
46mLet Azure control your DevOps Pipelines
01h 01mFive best Azure Access Control practice
49mAzure DevOps security - Lessons learned
44mAzure DevSecOps
42mAzure DevOps security - Lessons learned
45mSecuring Identity with Zero Trust
39mDon't Destroy Your Datacenter with Azure DevOps
40mCreate and Deploy Multi Tenant Applications on Azure with Azure DevOps
