I’m very new to authn/authz that doesn’t come out of the box from Visual Studio templates and have a question regarding new users registering on a public-facing application hosted in Azure (just a personal project for practice). I have app registrations for the React frontend and the .NET Core 8 API.

When I reviewed how Entra ID app registrations go in general (and how I set it up), it looks like we have to pre-add users and assign them their various roles for the app in Azure. This did work but how would a regular (“just stumbled across this app, I’d like to register”) user sign up (let’s say with username/password) such that I don’t have to pre-enroll them? Perhaps a default role?

I guess the better question is “Is Entra ID the right resource to use for public-facing applications for the scenario above?” I want to restrict certain API routes to Administrators so I still need RBAC.

I read in a comparison that AD B2C is more for this scenario (public-facing applications not focused on B2B or more intricate connections to other services), but there’s so much documentation regarding both my head is spinning.

I’m used to the AspNetUsers and related Identity tables that come from the VS template, but I think I’m missing something very obvious as migrating authz from localhost to Azure App Service is proving to take longer than I thought (again, completely new myself so any help is greatly appreciated).