Service Principals and Managed Identities
summary
Demo builds an ASP.NET (dotnet5) app that reads secrets from Key Vault without embedding credentials, deploys via GitHub Actions using an ARM template, and first uses a JSON service credential for the pipeline (service principal). Then a VM self-hosted runner with a managed identity logs in via az login --identity, so no pipeline secrets are stored. Azure Arc adds a local managed-identity endpoint for testing; deployments succeed and secrets never land in the repo.
AI-written summary · about
chapters (10)
- 0:00Introduction to service principals
- 8:23What are service principals
- 10:06Demo: Secretless local app
- 16:46Demo: Secure CI/CD pipeline
- 22:22Managed identities explained
- 25:32Demo: Managed identity on VM
- 31:27Demo: Secretless GitHub Actions
- 36:38Limitations of managed identities
- 37:19Azure Arc for local development
- 41:12Summary and Q&A
related talks
51mService Principals and Managed Identities - the Identity tools every Azure developer should know
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core
26mAzure Managed Identities: Why are you still using anything else?!?
01h 00mSecuring Serverless Applications in Azure
50mSecuring .NET Apps and Microservices in Azure
46mSecrets Management for the Modern Tech. Pro
01h 03mBuilding Secure Microservices in Azure
01h 05mBuilding Secure Microservices in Azure