MSAL Authentication: Auth ain't... (But it isn't easy either)
summary
Claims that MSAL works but PowerShell suffers assembly‑load and implementation pitfalls, then shows actual PowerShell code that uses MSAL and PKCE, spins up an HTTP listener for interactive and device‑code flows, and implements client‑credentials plus certificate and managed identity approaches. Demonstrates an Azure Function using a federated credential and workload identity federation to call Microsoft Graph across tenants with no secrets, and the demo runs and returns device lists, proving the pattern works.
AI-written summary · about
chapters (9)
- 0:00Authentication challenges
- 3:16MSAL in PowerShell
- 10:43MSAL problems in PowerShell
- 21:41Secure auth without MSAL
- 31:49Interactive auth flows
- 37:48Non-interactive client secrets
- 40:15Managed identities explained
- 47:20Cross-tenant access
- 49:20Q&A
related talks
59mDemystifying OAuth, JWTs and Azure AD
39mSecure Mobile Apps with the Microsoft Identity Platform
01h 02mDemystifying Azure AD, JWTs & OIDC
26mAzure Managed Identities: Why are you still using anything else?!?
23mAndroid Application with Microsoft Identity Platform
41mEasy-Auth: The Easiest Way to Secure Your Application in Azure App Service
01h 05mBuilding Secure Microservices in Azure
48mAn in-depth review of the latest advancements in authentication for Azure SQL and SQL Server 2022