Securing a REST API with Azure Active Directory
summary
Shows how to secure an Azure Functions HTTP REST API with Azure Active Directory so an Angular front end gets a valid JWT and calls protected endpoints. Uses MSAL in the Angular app, configures a protectedResourceMap and HTTP interceptor, and enables App Service Authentication (EasyAuth) on the Function App which creates the app registration and client secret. Covers CORS and the need to allow credentials, the audience must match the app ID or you get 401, and hosts the frontend via static website hosting on Azure Storage; the final demo works with a real bearer token.
AI-written summary · about
chapters (11)
- 0:00Introduction and overview
- 1:05What is Azure Active Directory
- 8:35Azure Functions overview
- 15:41Static website hosting in Azure
- 17:10Authentication libraries for AAD
- 21:49Setting up Azure AD app registration
- 29:06Configuring Azure Functions authentication
- 35:43Azure Storage static hosting setup
- 41:39Angular app integration with MSAL
- 46:02Live demo and testing
- 49:23Resources and closing
related talks
53mWeb API Security With Azure Active Directory
01h 03mServerless and App Service Security on Azure
01h 02mDemystifying Web API Security in Azure
01h 05mBuilding Secure Microservices in Azure
30mEnable Authentication and Authorization with Azure Active Directory
59mDemystifying OAuth, JWTs and Azure AD
52mDemystifying Web API Security in Azure
50mSecuring .NET Apps and Microservices in Azure