Nik
My feedback
-
155 votes
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 aadb2cpreview@microsoft.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 MFAIf both, which do you prefer more?
Again, please email your feedback to aadb2cpreview@microsoft.com. Feel free to include more details about your scenarios/requirements!
Nik
supported this idea
·
-
730 votes
We are prioritizing this customer ask on team and are looking at options to enable this broadly for customers.
Nik
commented
Would it be possible for Microsoft to hire someone just to deliver this small feature please
Nik
supported this idea
·
-
478 votes
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.
If you are looking to use custom domains to use javascript, we are now looking to enable that experience by providing a new (non-customizable) domain. Please look for updates here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/15493536-add-support-for-javascript-inside-the-custom-ui-br
/Parakh
Nik
commented
Any ETA?
Nik
supported this idea
·
-
52 votes
There is a current configuration to allow users to choose to remember a device for MFA: https://docs.microsoft.com/en-us/azure/multi-factor-authentication/multi-factor-authentication-whats-next#remember-multi-factor-authentication-for-trusted-devices
Additionally, we’re looking at providing more controls for this through conditional access.Nik
supported this idea
·
-
20 votesNik
commented
This is standard feature on all websites these days :-(
Nik
supported this idea
·
-
2,205 votes
Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at azurestoragefeedback@microsoft.com.
Nik
supported this idea
·
-
272 votes
We have released the public preview for this feature! Learn more about how to use it here: https://docs.microsoft.com/azure/active-directory-b2c/active-directory-b2c-setup-oidc-azure-active-directory
/Sam
Nik
commented
Anyone working on this? any timelines? any project plan? anything?
Nik
supported this idea
·
-
173 votes
Thank you. We will examine the experience of duplicate sign ups across Identity providers. Would performing this check by using the email address be sufficient?
BTW, Linking multiple provider accounts to one user is in our roadmap and we’ve already achieved it in preview…
We look forward to your feedback
/Jose Rojas
Nik
commented
Having been using B2C for a year now, we are a couple of weeks from ditching it... its far more restrictive and painful than any value if brings now and progress on fixing anything is glacial to non existent.
Nik
supported this idea
·
-
291 votes
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.
Nik
commented
Why aren’t you working on features that more people need and have voted for?
-
19 votesNik
commented
Me too - hopeless for new users
Nik
supported this idea
·
-
13 votesNik
supported this idea
·
-
13 votesNik
supported this idea
·
-
34 votes
We’re looking at this feedback and along with work for verification emails, looking to do some work around customization to completely remove the Microsoft brand and allow this depth in customization. Please bear with us as we are looking at how best to prioritize these changes.
/Sam
Nik
supported this idea
·
-
20 votes
We would like more specifics on this scenario. How would you user to self identify for MFA?
Nik
supported this idea
·
-
281 votes
Hi all,
This is currently available for custom policies, you can find the instructions here: https://docs.microsoft.com/azure/active-directory-b2c/javascript-samples
We will be bringing this to built in as well in the coming weeks.
/Sam
Nik
commented
If you need a test user, let me know :-D
-
12 votesNik
supported this idea
·
-
97 votes
Hi all, unfortunately we don’t have plans to share out a public roadmap. This is constantly changing as we’re listening to customer requests. We will continue to update feedback.azure items as they come up so feel free to suggest anything you are curious about.
Nik
supported this idea
·
-
60 votes
We are looking for private preview customers who are interested in using Azure AD (single tenant only) or any other custom OIDC compliant identity providers in your built-in policies. If you are interested, please send an email specifying this specific request to aadb2cpreview@microsoft.com with your Azure AD B2C tenant name.
Nik
supported this idea
·
-
136 votes
This is not planned for the next 6 months, but is on the roadmap.
/Parakh
Nik
commented
Lots of copies of web apis, each configured with different clientids as far as I can tell.. or everything in your entire site using one clientid (applicationId)
Nik
supported this idea
·
Sounds like it’s time to grow the team ;-)