Anonymous
My feedback
-
46 votes7 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
265 votes41 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hey folks! Thank you for your feedback. We are reviewing this ask and will keep you up to date on our findings. We have also added information about this limitation in our documentation. Thank you!
Anonymous
supported this idea
·
-
822 votes122 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We’re really pleased to let you know that we’ve released the first authentication method APIs to public preview:
https://docs.microsoft.com/graph/api/resources/authenticationmethods-overview
So far there are APIs for managing phone numbers and password resets. When phone numbers are set with the API, the user can use that number for MFA and SSPR (as allowed by your tenant’s policy).
The team is hard at work at building out APIs for all of the other authentication methods, and we’ll update the response here as they’re released.
Anonymous
supported this idea
·
-
171 votesplanned · 24 comments · Azure Active Directory » Conditional Access · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
775 votes65 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
For requiring additional factors with Windows Hello for Business, please see – https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/feature-multifactor-unlock
For why PIN is better than a password, please see https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-why-pin-is-better-than-password
For Authenticator app sign in to Azure AD, please see https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-phone-sign-in
As always, other feedback is welcome
/Ravi
Anonymous
supported this idea
·
-
597 votes
We’re working on a solution and will update you when we know more.
Anonymous
supported this idea
·
-
33 votes
This is something we are looking to add.
-Daniel Wood.
Anonymous
supported this idea
·
-
159 votes22 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
548 votes71 comments · Azure Active Directory » Role-based Access Control · Flag idea as inappropriate… · Admin →
Folks,
We are working on it. There is an elevation of privilege concern associated with this feature. If a group is assigned a role, any IT admin who can manage group membership can manage that group’s membership and indirectly manage who gets the role. So, we have to ensure that the feature is secure.We are taking a staged approach to execute this feature –
Stage 1: Supporting cloud groups to be assigned to roles
Stage 2: Supporting on-prem groups to be assigned to rolesStay tuned!
Regards,
Abhijeet Kumar Sinha
Azure Active Directory TeamAn error occurred while saving the comment Anonymous
supported this idea
·
-
148 votesAnonymous
supported this idea
·
-
7 votes
We are hoping to do this! Please upvote it!
Anonymous
supported this idea
·
-
85 votes
We definitely want to support AAD! Please vote this request up if you’d like to see it in the app.
Thank you for your feedback!
Anonymous
supported this idea
·
-
1,050 votes80 comments · Azure Active Directory » Groups/Dynamic groups · Flag idea as inappropriate… · Admin →
Thank you for your feedback! The feature team is aware of this suggestion and will keep it under consideration. There are technical challenges to overcome in order to make this happen. Please keep the votes coming if this feature matters to you.
Chen
Anonymous
supported this idea
·
-
1,277 votes246 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
This feature is now on the roadmap. The MFA team is planning to adjust admin roles or create a new role that will allow delegation of MFA registration and credentials to an admin role.
Anonymous
supported this idea
·
-
1,901 votes
We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.
Use case A: nested group in a cloud security group inherits apps assignment
Use case B: nested group in a cloud security group inherits license assignment
Use case C: nesting groups under Office 365 groupsAnonymous
supported this idea
·
-
403 votes50 comments · Azure Active Directory » Groups/Dynamic groups · Flag idea as inappropriate… · Admin →
Our feature team is looking into options for addressing this scenario, but we do not yet have any timelines to share. For now as a workaround, you can manually trigger the reprocessing by updating the membership rule to add a whitespace at the end. We’ve also added the ability to check the membership processing status, to keep track of the status and know if processing is complete.
Anonymous
supported this idea
·
-
1,298 votes233 comments · Azure Active Directory » End user experiences · Flag idea as inappropriate… · Admin →
Folks,
Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).
First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.
Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this…
Anonymous
supported this idea
·
-
767 votes
We’ll be wrapping up work soon, after making updates from feedback we’ve received so far. We should have a public date soon.
-Caleb
Anonymous
supported this idea
·
-
698 votes81 comments · Azure Active Directory » User Creation, Deletion, and Profile Management · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
54 votesAnonymous
supported this idea
·
Would like an update on this.