I picked back up the towel I through in a couple days back and started down the path of customizing the UI through the Azure AD B2C provided framework. These were the articles that resonated the most as to why I should avoid this: Multi-factor authentication, email verification, etc. Talking with my peers, by peers I mean people way smarter than me, I was quickly hand-slapped for even thinking about ROPC, citing the potential security concerns and the things I would be given up out of the box, e.g. I needed to do this so the user could change their password if they wanted.

This worked, but I soon ran into an issue where I could not call the Microsoft Graph API with the authenticated user’s access token. I created an ASP.NET Core MVC application and used the Resource Owner Password Credentials (ROPC) policy in Azure AD B2C to authenticate my users. If my memory was serving me correctly, which is often not the case, I thought this was possible, just didn’t know what challenges or issues I was going to encounter.Īfter a day or two of aggravation fighting HTML and CSS, I through in the towel on customizing the UI and decided on another direction, a direction where I had absolute control over the UI. One of my most recent requests was to customize the Sign In and Sign Up pages. Lately I have been working a lot with Azure AD B2C.

Azure b2c login