srikanth
My feedback
-
63 votes7 comments · Azure Active Directory » User Creation, Deletion, and Profile Management · Flag idea as inappropriate… · Admin →srikanth
supported this idea
·
-
15 votes
Thanks for the feedback, we have this work in planning.
srikanth
supported this idea
·
-
67 votessrikanth
supported this idea
·
-
16 votessrikanth
supported this idea
·
-
2 votes0 comments · Azure Active Directory Application Requests » Single Sign-On · Flag idea as inappropriate… · Admin →
Thanks for your app request. In order to evaluate your request, can you please fill out this app request form at http://aka.ms/aadappsurvey? It will help us prioritize the request and be able to follow up with you.
/Luis
srikanth
supported this idea
·
-
33 votes6 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →srikanth
supported this idea
·
An error occurred while saving the comment -
95 votes12 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
There is planned work to address this scenario. We don’t feel that backup codes provide a good security option as they’re often misplaced. Also, it’s hard to have users print them out and have them when they’re needed. Instead, we are looking at a time-limited passcode that could be generated either by the user (just in time when it’s needed) or by an admin (for example a helpdesk agent). The organization admin would have control over when a user could generate these codes. The code can be used for a limited time, then it will no longer be valid.
Note – for areas with limited cellphone connectivity (or roaming charges), the code generated in the authenticator app will allow MFA login. The time-limited passcode is meant to stand in if the user temporarily forgot/lost their phone.
Richard
An error occurred while saving the comment srikanth
commented
This is a required feature for enterprises to seriously consider Azure MFA.
srikanth
supported this idea
·
-
55 votes
This not planned for the next 6 months, but it is on the roadmap.
/Parakh
srikanth
supported this idea
·
-
349 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!
srikanth
supported this idea
·
-
52 votes
We are working to enable this feature. We should have another update by Dec 2018.
/Parakh
srikanth
supported this idea
·
-
50 votes
Not currently planned for the next 6 months, but it is in our roadmap.
/Parakh
srikanth
supported this idea
·
-
8 votes
We’re working on an improved error controller that includes suggested remediations for errors. However, your client app should never change behavior based on specific error codes – these are internal and subject to change at any time.
srikanth
supported this idea
·
-
19 votessrikanth
supported this idea
·
-
45 votes
Authenticating using a SAML identity provider is now in public preview via custom policies. You can check out the instructions on how to set up a sample SAML identity provider like Salesforce here – https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-setup-sf-app-custom.
/Parakh
srikanth
supported this idea
·
-
5 votessrikanth
supported this idea
·
-
9 votessrikanth
supported this idea
·
-
89 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.srikanth
supported this idea
·
-
4 votes0 comments · Azure Active Directory Application Requests » User Provisioning · Flag idea as inappropriate… · Admin →
Hi we can quickly integrate it into our platform for provisioning. Does the app support the SCIM standard (it is a standard for provisioning the way SAML / OIDC are used for SSO).
Learn about SCIM – https://Aka.ms/SCIMOverview
Request the app to be added in our gallery for provisioning (if it supports SCIM) – https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-app-gallery-listing
/Arvind
srikanth
supported this idea
·
-
7 votesunder review · 0 comments · Azure Active Directory Application Requests » Single Sign-On · Flag idea as inappropriate… · Admin →srikanth
supported this idea
·
-
7 votes0 comments · Azure Active Directory Application Requests » User Provisioning · Flag idea as inappropriate… · Admin →
Hi we can quickly integrate it into our platform for provisioning. Does the app support the SCIM standard (it is a standard for provisioning the way SAML / OIDC are used for SSO).
Learn about SCIM – https://Aka.ms/SCIMOverview
Request the app to be added in our gallery for provisioning (if it supports SCIM) – https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-app-gallery-listing
/Arvind
srikanth
supported this idea
·
We also need this. To tie Authenticator App MFA to managed device during enrollment.