One of the more serious issues for Azure B2C is the absolutely awful state of the documentation and samples which often feel unfinished and half baked. Just a quick note on the below – I’ve discussed some of this with MS previously but hopefully they will provide some feedback and I will update if and as appropriate. Proof of concept all the B2C touch points (policies, customisation etc.) and ensure it will do what you need.If you’re considering B2C for a project in the near future I’d suggest a couple of things: If you’re not on that happy path – it might do what you need but getting there is likely to be a time sink and involve a lot of preview features. In theory it provides a flexible and fully managed consumer identity provider inside Azure and while I’ve had a couple of successes after recent experiences I’ve come to the conclusion that its simply not ready for anything other than narrow requirements and am pulling my current projects away from it and onto Auth0 (this isn’t a random choice – I’ve used Auth0 before and found it to be excellent).
I’ve dipped in and out of Azure AD B2C since it first launched. NET, Azure, Architecture, or would simply value an independent opinion then please get in touch here or over on Twitter.
0 kommentar(er)
