Building Secure Microservices in Azure
summary
Shows a concrete .NET 6 system: an Azure App Service API, an Azure-hosted client and an external daemon client built with Pulumi for infra as code, using client credentials for machine-to-machine calls, application permissions (app roles) for authorization, and managed identity for Azure-hosted clients. Uses Azure AD, auth0 for external user sign-in, Microsoft.Identity.Web/Microsoft.Identity.Client/Azure.Identity libraries and Swagger local-dev auth. Demo issues: Swagger local flow successfully obtains tokens; external client gets 403 on write (only read role assigned); managed identity path works and removes secret management.
AI-written summary · about
chapters (18)
- 0:00Securing microservices in Azure
- 1:51Distributed microservices challenges
- 3:37Authentication and authorization
- 6:46Zero trust security model
- 8:10Azure AD for consistent security
- 10:15OAuth 2.0 flow scenarios
- 12:21Authorizing callers with permissions
- 14:49Simplifying security use cases
- 15:53Defining roles by business use
- 18:45Demo setup and Azure AD
- 24:50Azure AD authentication server
- 31:53Local dev with Azure AD
- 34:23Assigning roles to users
- 40:28Securing Swagger UI
- 43:23External clients with credentials
- 52:27Managed identities for Azure
- 55:56Configuring Azure clients
- 1:01:06Summary
related talks
01h 05mBuilding Secure Microservices in Azure
01h 02mDemystifying Web API Security in Azure
52mDemystifying Web API Security in Azure
50mSecuring .NET Apps and Microservices in Azure
53mWeb API Security With Azure Active Directory
01h 03mServerless and App Service Security on Azure
56mEasier infrastructure and safer secrets with Pulumi, Azure, and .Net Core
50mSecuring Serverless Applications in Azure