Introducing enhanced company branding for sign-in experiences in Azure AD

SashaMars My use case is a React/NodeJS B2B app with external guest users for one tenant then an alternate login for users in our internal tenant. My last two years of developing/managing this app and supporting our clients would've been much better had there been a more customizable user experience for the external users, but I'm fine offloading the login pages to your team with the more customizable approach you are now taking.

Most of our clients (external guest users) are in other Azure AD home tenants, and redirecting to their tenant login forms is common, so a custom self-hosted experience with API calls is not a must-have.

However, I would be interested in testing that flow with an API because we could possibly eliminate one or two steps for some of our clients who fill in their email and are redirected to fill out their email one more time with their password. If we could handle the API call to check our tenant for the user, return that they are in another home tenant or a non-AD user, then present them with the password field for that tenant or the email one-time code in a single step, it would streamline the UX.

For now, the options you added this week are very helpful, though I'd like some additional CSS capabilities, such as allowing :before/:after pseudo elements or allowing custom selectors to slightly tweak the helper text depending on the step of the login process the user is on. This could also be accomplished by providing more options in the company branding settings for each login step.

Lastly, I do have a question about the custom css template you provide. I'm not finding the customizable classes in the html (like .ext-boilerplate-text). Do the classes only get applied to the html elements when styles are added in the file?

Thanks again.