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.
Any updates on this?
We are exploring how to implement this feature without compromising privacy. Thank you for all the feedback!
- Matt, Product Manager
We want to see this in the sub-calls as part of the end to end transaction details. We have API calls that are received on the server and then in turn make sub- API calls to other APIs like MS Graph API and others. We can see the URL request that is made as the sub-call but not the body of the sub-call which would be really helpful.
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
Any update on this? We are currently using the Sign up or Sign in policy and forcing elements to be hidden in order to accomplish this. It would be much better and cleaner to use the intended Sign In Policy properly instead of forcing the Sign up/sign in policy to do something its not really supposed to.
We have started the planning for this feature and hope to have a preview by the end of the calendar year. In the meantime, could you respond to email@example.com with the answers to the following questions:
- In which scenarios do you plan to force the user to change his/her password?
- What kind of information (if any) would you like to get back if the user goes through the reset flow?
- Do you currently or plan to track which users have reset their password?
This is a must have. Its a strange workflow if you are creating users via the Graph API and then sending them the temp password to sign in with, only to have to ask them to then manually reset their own password instead of providing a flow to reset it on first login.
Updating the status to indicate that this is a valid suggestion and in our backlog for the future. Please keep the comments/votes coming, knowing more about how you intend to use this helps us prioritize and design better features.
We have started working on this feature and hope to have another update by Oct 2018.
This is not planned for the next 6 months, however it is on the roadmap.
This is currently not on our roadmap. You can retrieve this value by making a call through the Graph API. If this is needed for your scenarios, please continue voting and we will review at a later date.
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 firstname.lastname@example.org.
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 email@example.com. Feel free to include more details about your scenarios/requirements!
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?
It is possible to add multiple reply URLs within the same domain, unfortunately the experience is a bit clunky and we’re working on fixing this.
At this time, in order to achieve this a setup with client1.domain.com and client2.domain.com as redirect URIs, you must first add the overarching domain as a redirect URI and then add the sub-domains, like so:
Check out this article for more info:
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.
Currently, you can use “App Registration” blade in the Azure Portal (outside of the Azure AD B2C blades) to register an apps that define application permission and the register apps that use client credentials to request these. The caveat is that this is done using the same mechanism that you’d use in regular Azure AD.
Ideally we’d have a first class experience for this in the Azure AD B2C blades or at least have an Azure doc that walks you through the experience I just summarized, so I’m leaving this feature ask open.
It would be great if you guys can add comments with your feedback. What scenarios areyou trying to achieve? Does the approach above help you achieve what you want to achieve? Does the experience to do so work for you guys and if not, what would you like to see?
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
Just to provide an update, we are close to launching a private preview. We are in the final testing stages for this feature. We will have another update in the next few weeks with instructions on how to join the private preview.
We currently have a private preview for custom policies, you can see the documentation here: https://github.com/Azure-Samples/active-directory-b2c-console-custom-policy-api
You can request private preview access by sending an email to email@example.com with your directory name.
We will be following up with other scenarios for programmatic APIs.
This feature is temporarily put on the backlog. Work will resume in the 4th quarter of 2018, so a public preview should be available by the end of 2018.