Thanks for the feedback. We will take this under review, and report back.
Given that a Azure AD B2C tenant should only be used for configuring Azure AD B2C, would having programmatic API’s to configure all of the Azure AD B2C settings be useful or is there more that you are looking to achieve using ARM templates?
We’ve put out a new version of the sign in policy called sign in v2. This is available through the new portal experience and we have rebranded policies as user flows. Please give this a try and give us feedback through this link: https://microsoft.qualtrics.com/jfe/form/SV_0Gu45RkBy2YR1kh
/SamSzymon Bartnik commented
Do you have this one on your roadmap?
It's unbelievable for me that you expect business people don't want customize sign in/sign up pages. Sign-in/sign-up policy customization works like a charm but unfortunately we require sign in & sign up separated. We implemented it blindly trusting such obvious functionality will be available (maybe our fault). Otherwise we won't use B2C definitely because our expectation was it will speed up our development process.
Please let know it's meant to be fixed in near future.
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.
We have a sample for this use case here: https://github.com/azure-ad-b2c/samples/tree/master/policies/invite
Let us know what you think and if this fits your use case.
We continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an ETA.