I'm relatively new to Azure (my experience is mostly with AWS at the practitioner level) and I've been assigned to work on a project involving Microsoft's MCT platform. We have a demo app for multiple customers, likely set up with separate deployments. Right now, I only have access to the demo tenant, which uses an email ending with 'redacted.onmicrosoft.com,' and the platform URL appears as 'redacted-abcdefg.z03.azurefd.net.' My plan is to first implement the solution in the demo environment before extending it to my customers.
The main goal is to create a custom login page that includes a 'show password' feature. From my research, I found that Azure AD B2C seems to be the way to go for login page customization, but when I checked the Azure AD B2C service, it only provided options to create a new account or learn more, which isn't very helpful.
In the Entra ID, I noticed user flows under 'External Identities,' and I can interact with them, but real customization for the login page seems absent. The only options I found under 'Company branding' are limited to basic branding and CSS tweaks. There's definitely no option for inserting custom JavaScript or enabling a 'show password' toggle.
Therefore, my question is: Is it actually feasible to implement this using Entra External Identities and user flows, or do I need to consider Azure AD B2C or another approach? Any insights from those who have tackled similar tasks would be incredibly helpful, as I'm feeling a bit stuck here.
3 Answers
Interestingly, Entra External ID does feature the ability to show passwords out of the box, but it's not something you can configure extensively. The UI is quite similar to what you would find on outlook.live.com. If you want to have more customization, consider using the native authentication APIs. However, for a demo purpose, that's not really recommended.
Just so you know, Azure AD B2C has effectively been deprecated, so it's better to stick with Entra External Identity for new developments. Don't build anything new using B2C; you'll run into more complications down the line.
It sounds like you're dealing with the confusion that's come from Microsoft's recent rebranding and feature shifts. If you're using the standard user flows in Entra, customization options are pretty limited. You might be able to add some branding elements like logos or colors, but adding custom JavaScript for features like a show password toggle often isn't an option there. For more extensive UI modifications, people typically turn to custom policies in Azure AD B2C or manage the authentication through their own frontend while using Entra for identity flows.
Thanks for the clarification! That makes things a bit clearer for me.