AAD B2C is a pretty complex tool which IMHO is still underrated in most customers minds. I think this is mainly because Microsoft did a pretty bad job in distinguishing it from another feater called Azure AD B2B. The latter is simply about inviting people from other Azure ADs or Microsoft Accounts into a tenant. A lot of folks I spoke to told me that this is the reason they never looked deeper in B2C even if they discovered it. I already did 2 blog posts in German about this issue (see Links section above). Now I recognized that a lot of stuff in the Azure UI has changed and I decided to reramp the complete series. My international guests will appreciate the restart too, I think.
I’m planning to split the issue into several articles. Currently the planned structure is:
- Introduction: This is the part you are reading now. I’ll introduce you into some wordings and concepts around Azure AD, Open ID and explain how B2C fits into this.
- Configuration and Integration: This part will show how to integrate B2C into .NET Core applications. It will cover creation of a tenant, configuration of identity providers and apps and so on.
- Indentiy Providers: Because providers are a central concept in B2C we’ll cover them in more depth here. This will include connection to Azure AD and providers like Google.
- Customization: B2C can be customized in a lot of ways. We’ll learn here about UI customization, internationalization and alike.
- Automation: As many other Azure services B2C can be configured and managed using Microsoft Graph. We’ll look into this in this part.
Please be aware that I don’t know if this structure is representing the finite result yet. My blog-project is pretty agile and I will react to your feedback. As always I’m not trying to make this short and painless! If you know my blog you also know that one of my targets is to give you a comprehensive inside. This leads to longer articles than you might be used to. My blog - my rules 😎.