Entra ID and Blazor. Both being Microsoft Technologies it should an auth partnership made in heaven.

Unfortunately, more than often that is not the case. From the complexity of setting up, to ensuring the correct values are in the application. There are Blazor experts that avoid this in favor of 3rd party solutions.

It doesn't have to be that way.

By walking through the traps I fell into and setting up a live application — mistakes included — you'll leave with the knowledge and confidence to implement it yourself.

Together we'll set up an Entra App for authentication, as well as a separate app for downstream authentication. Then we set up a Blazor Web App, including a minimal API, as well as a seperate minimal API app acting as that downstream API we need to authenticate against.

Whether you need to control access for internal or external users, Entra ID, RBAC, and Blazor work beautifully together. Consider this your shortcut — leave empowered to implement it yourself, war stories optional.

This session looks at the mistakes I made when first working with Blazor and Entra ID — and why they made it so hard to get working.
Live demo: a Blazor Web/WASM application with a downstream API, hooking up a new Entra app registration in real time — so you can see exactly what options are needed and why.