Everything a .NET developer needs to know about configuration & secret management
summary
Covers how .NET configuration resolves providers by precedence and why the Options pattern with validate on start prevents runtime surprises; recommends user secrets for local dev and replacing baked-in secrets with Azure Key Vault plus Managed Identities so production services fetch secrets at runtime (demo shows an ASP.NET Core app retrieving a DB connection string with ActiveDirectoryDefault and no passwords). Calls out secret trend data — 28.5M new secrets detected in 2025 — and warns DefaultAzureCredential can add ~30s to local startup.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:33Why config & secrets matter
- 9:23Basics of .NET config
- 19:20Problems with config & options
- 33:47Development secrets with user secrets
- 44:53Production secrets strategies
- 54:18Demo: Azure Key Vault & identities
- 1:00:18Q&A
related talks
55mEverything a .NET dev needs to know about configuration and secret management
43mSecure Development
51mService Principals and Managed Identities - the Identity tools every Azure developer should know
47mManaging your Secrets in a Cloud Environment
10mCan you keep it a secret?
46mSecrets Management for the Modern Tech. Pro
50mSecuring configuration settings for applications in Azure
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core