Securing Serverless Applications in Azure
summary
Step-by-step demo shows an Azure Functions app wired to a Storage Queue, retrieving secrets from Azure Key Vault, using Managed Identity to avoid embedded credentials, and calling the Microsoft Graph invitation API to create external users via an app registration and client secret. ClaimsPrincipal binding surfaces caller email and claims into the function, secure outputs hide secret values from logs, and Application Insights + Azure Monitor capture live invocation metrics and alerts — the end-to-end flow runs and is monitored.
AI-written summary · about
chapters (17)
- 0:00Securing serverless in Azure
- 1:53Why serverless needs security
- 5:06Cost and ops benefits
- 10:11Secure Azure Functions from scratch
- 13:27Demo: secure message queue function
- 21:55Auth and authorization in Functions
- 23:55Managed identities for Functions
- 27:53Demo: managed identity access
- 32:54Register apps in Azure AD
- 36:27Permissions for external users
- 40:40Managed identity with Key Vault
- 42:10Securing Logic Apps outputs
- 46:43Monitoring with Application Insights
- 51:05Application Insights dashboards
- 54:49Alerts for security monitoring
- 56:57Security standards for serverless
- 59:17Q&A
related talks
50mSecuring Serverless Applications in Azure
47mSecuring Serverless Applications in Azure
01h 03mServerless and App Service Security on Azure
50mSecuring .NET Apps and Microservices in Azure
42mService Principals and Managed Identities
01h 01mServerless Architecture With Azure
01h 01mServerless Azure Data handling
01h 05mBuilding Secure Microservices in Azure
