Service Principals and Managed Identities - the Identity tools every Azure developer should know
summary
Shows a working .NET Core web app that drops all hardcoded secrets and acquires Key Vault secrets via the Azure Identity library, running locally with Azure CLI credentials and on Azure using a system-assigned managed identity that has only list/get permissions and successfully reads a secret. Demonstrates creating a service principal for CI/CD (az ad sp create‑for‑rbac output includes client secret), plus GitHub Actions, Azure DevOps and Terraform patterns that fetch Key Vault values at deploy time. Mentions Azure Arc for giving non‑Azure VMs managed identities. All demos run end‑to‑end.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 0:55Why are we here
- 1:44Identity is hard
- 2:23Identity is insecure
- 3:32The trojan horse
- 5:07Azure Active Directory
- 9:37Rotating secrets
- 12:52Azure Mass Identity
- 13:25Service Principals
- 16:30Managed Identities Demo
- 17:01Office and Graph
- 17:18Application
- 17:44Demo
- 22:55Key Vault
- 26:14Managed Identity
- 28:28Service Principles
- 30:04Service Business
- 30:49Creating a Service Principal
- 31:38Demo 1 Azure DevOps
- 34:45Demo 2 GitHub
- 35:18Demo 2 Main
- 36:00Demo 2 Terraform
- 38:56Why use Service Principals
- 40:14Summary
- 40:52Language
- 42:32Azure SDK
related talks
42mService Principals and Managed Identities
26mAzure Managed Identities: Why are you still using anything else?!?
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core
55mEverything a .NET dev needs to know about configuration and secret management
01h 02mEverything a .NET developer needs to know about configuration & secret management
43mSecure Development
47mSecuring Serverless Applications in Azure
19mEnhancing Security in Azure Cosmos DB: Best Practices