The signup/singin policy does not automatically redirect to password update by design.
I’m leaving this item open though, to capture the ask to streamline this experience so as not to require the application to do this detection of the error code and subsequent redirection to the password reset policy.
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?
We have started working on this feature and hope to have another update by Oct 2018.
More details on Azure Cosmos DB on Azure Stack will follow as we make progress on it.
Thanks for the feedback.keerthi commented
i agree,i'm also waiting for a fully managed cosmos db