Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
We have a private preview of this feature available. If you are interested in joining, please contact firstname.lastname@example.org with the name of your tenant.
An error occurred while saving the commentAbel Espino commented
Be able to relax the B2C directory password policy so that migration from existing on-premise home-made "B2C" directories (credentials) could be easily migrated into Azure ADB2C.
And accompanying the previous one, an option to massively prompt users (send an email) to change their passwords to a more robust one.
We definitely recognize the popularity of this feature, and we discuss it constantly during the planning phases. However there are certain technical limitations in the system that add a large amount of development cost. Because of the cost and the fact that there is a workaround available, other features get prioritized over this one.
That being said, please keep voting for it. The popularity of the feature does help bring it up and makes us reconsider every time.
Apologies for the delay.
We’re doing some research both on the specifics of this ask as well as what it would take to support this.
Is the ask here to do the same thing that regular Azure AD does (see: https://blogs.technet.microsoft.com/enterprisemobility/2014/12/18/azure-active-directory-now-with-group-claims-and-application-roles/) or is are there different requirements around this for Azure AD B2C?