302 votesplanned · 8 comments · API Management » API management experience · Flag idea as inappropriate… · Admin →
We are looking to add additional MFA options for Azure AD B2C in the next few months. As part of the investigation, we want to learn more about your requirements. Email your feedback to email@example.com.
When you say “support for Microsoft Authenticator”, which feature are you referring to?
1. The ability to see the codes in the authenticator app
2. The ability to receive push notifications for MFA
If both, which do you prefer more?
Again, please email your feedback to firstname.lastname@example.org. Feel free to include more details about your scenarios/requirements!
We are in the process of planning this feature and hope to have a preview available by the end of november. In the meantime, could you please respond to email@example.com with your responses to the following questions:
- If you had a “password change” policy, what kind of information would you like to get back once the policy has been executed?
- Would you prefer to have a policy that forces you to sign in first, and then asks you to change the password, or one that let’s you do it all on the same page?
- Would you want an email to get sent out to the user whenever the password is changed?
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 restarted work on this feature. However, we don’t have a date for public preview yet.
Thanks would love to know more details on why the full URL is insufficient
This is not planned for the next 6 months, but is on the roadmap.
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 continue evaluating several alternatives to provide full email customization. We are actively working on an alternative.
Unfortunately we do no yet have an 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 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 commentAnonymous commented
We have different segments of customers. We would like to able adjust the password policies accordingly to minimize friction in the sign-up process for some customers
We are currently prioritizing Azure AD as and identity provider into B2C. We will review this request after that work is done. Keep the requests coming! /Jose Rojas
This is not planned for the next 6 months. If this is needed for your scenario, please continue voting and we will re-evaluate at a later.
327 votesunplanned · 44 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →