Hello. Our apologies for the delay in an update here.
We are actively working on this and have a new ETA of Q2 2021.
Thanks for your patience.
Thanks for the feedback on this. There are several ways to do Azure AD join (OOBE, bulk enrollment and Autopilot) which provide a richer experience to join devices to Azure AD. We’re continuously working to enhance those, so currently this is unplanned for the near future. Please continue to vote to help us prioritize
9 votes3 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! We are reviewing this ask. We believe that this issue is addressed in Windows 10 1809 but are still investigating. Thank you for your feedback!
An error occurred while saving the commentAnonymous commented
@Ovidiu : I stick to your comment. But notice how MS wrote the text in the article you mentioned :
"Your implementation of this policy depends on your security requirements for displayed logon information ... revealing logged on user’s full names or domain account names might contradict your overall security policy.".
It is therefore not an MS recommendation ;-).
But technically, I wonder how someone could technically trigger an SSPR for an account at logon screen without being able to select it for obfuscation reasons... I believe even employees from MS do not use this "Don't display last signed-in" policy anymore.
Maybe MS has better ideas...
Thanks for the feedback! I’m moving this to the Developer Experiences section as this seems like it’s broader than B2B (includes regular user create/update). Please keep adding scenarios and votes.
228 votes20 comments · Azure Active Directory » Developer Experiences · Flag idea as inappropriate… · Admin →
Thank you for the feedback! This is in the backlog and we are looking into this. We don’t have an ETA yet, but we will share once we have one. Please keep voting if this feature matters to you.
3 votesAnonymous shared this idea ·