How can we improve Azure Active Directory?

Customer-owned domains

Run Azure AD B2C's sign-up & sign-in pages under a custom domain, for e.g., login.contoso.com, instead of login.microsoftonline.com.

499 votes
Sign in
(thinking…)
Password icon
Signed in as (Sign out)

We’ll send you updates on this idea

AdminAzure AD Team (Software Engineer, Microsoft Azure) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

Due to various technical limitations, the first iteration of the customer-owned domains functionality will not be available for a few more months. We will provide an update as soon as we can get a more specific ETA.

If you are looking to use custom domains to use javascript, we are now looking to enable that experience by providing a new (non-customizable) domain. Please look for updates here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br

/Parakh

54 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Anonymous commented  ·   ·  Flag as inappropriate

    Please provide an update. We're coming up on 2 years since your last update, which indicated the functionality would be available in "a few more months"...

  • Rami Karhu commented  ·   ·  Flag as inappropriate

    Any updates on this? It's a long hoped for feature. And a pretty basic one, too. Having to send users to register and login via microsoftonline.com not only looks shady, but also breaks the conversion paths in our analytics.

  • Anonymous commented  ·   ·  Flag as inappropriate

    The microsoft domain is deemed unacceptable for us because it does not build trust with the user. I am looking at options to display the login form as a popup. Looks like the MSAL js library provides a way to show a new popup window but no modal popup. If a modal popup can be used then I think it would make a workaround for the trust issue.

  • Anonymous commented  ·   ·  Flag as inappropriate

    In July 2017 we were told we would have to wait "for a few more months". Those months have passed and so has the year. What's happening?

  • Sad Customer commented  ·   ·  Flag as inappropriate

    I'm disappointed that MS has not implemented this feature or provided a clear answer to when it will be implemented. Is this a true technical limitation or simply an incompetent project manager at MS?

  • Anonymous commented  ·   ·  Flag as inappropriate

    We need this feature for a big corporation with +50 million end-consumer clients.
    We would prefer Azure B2C, but this missing feature is blocking.
    Otherwise, we need to consider other vendors like Auth0 or Okta.

  • Anonymous commented  ·   ·  Flag as inappropriate

    It's a year after this was promised "in a few more months". Can we please have a real ETA?

← Previous 1 3

Feedback and Knowledge Base