AAD B2C has poor SLA and applying your own login page design takes much effort. And this is just a tip over unnecessary complications under the hood. I would not recommend it over storing users in your own database.
Well, you'd need look a bit closer than just scanning long(?) list of features from some presentation slides. Some of the features are hard to find, other are hard to configure (have fun with XML), some are plain missing while you get them in "normal" AAD. And on top, you get no observability... unless you already mastered logs... but then it still will not answer simple question "how many users could not sign-in because of B2C outage?" Overall - yes, you are better off with plain database based on Microsoft.AspNetCore.Identity. Or just pay for quality product like Auth0 or Okta. It is only my advice based on past 9 months and I am not trying to convice you, just take my advice and avoid rubbish service that is pain to use.
where can we find the .NET code of the examples that are shown at the end?
Hi sir, I have a question, I implemented b2c recently in my enterprise application but it stores user log in information twice for each login.
Is this similar to IdentityServer but running on Azure?
is this module available in free trial or just with pay as you go ?
why is javascript not enabled on the custom pages, any idea ?
This is really disappointing to see it’s a basic overview. Setup and calls were expected based on your description
why not using blazor wasm on your frontend?
AAD B2C has poor SLA and applying your own login page design takes much effort. And this is just a tip over unnecessary complications under the hood. I would not recommend it over storing users in your own database.
What would be an alternative to Azure AD B2C? AWS Cognito or something else?
Auth0
wow
How would a database with a bunch of tables and users replace an extremly complex system (in terms of features offered) like azure b2c?
Well, you'd need look a bit closer than just scanning long(?) list of features from some presentation slides. Some of the features are hard to find, other are hard to configure (have fun with XML), some are plain missing while you get them in "normal" AAD. And on top, you get no observability... unless you already mastered logs... but then it still will not answer simple question "how many users could not sign-in because of B2C outage?"
Overall - yes, you are better off with plain database based on Microsoft.AspNetCore.Identity. Or just pay for quality product like Auth0 or Okta.
It is only my advice based on past 9 months and I am not trying to convice you, just take my advice and avoid rubbish service that is pain to use.