47 votesunder review · 8 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →
78 votesstarted · 8 comments · Azure Active Directory » Privileged Identity Management · Flag idea as inappropriate… · Admin →
Is there an update on this?
30 days of logs is often not nearly enough. Especially when running a forensic investigation where suspected activites took place several weeks ago.
96 votes14 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! Thank you for your feedback. We don’t yet have plans to release this feature, but we are still considering it. We will update you if anything changes.
The feature in Windows 10 logon should be re-labeld as "Manage Password" or some similar. It absolutely needs to cover both password changes and account unlock functionality.
109 votes19 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! This feature is still in progress and will go to public preview soon. I will update this request once it’s in public preview. I apologize for the delay – we know how important this is!
Very much looking forward to more accurate reporting on SSPR activities.! Right now if a new user registers or an existing user updates their registration in anyway, the events in the logs are exactly the same. There is no way to generate reports differentiating New vsa Existing.
We’ve begun this work.
Is there an ETA on this? Not being able to bulk import for over 700 sites is a big drawback. Being able to bulk import all the various subnets in CIDR form, along with additonal columns for fields like Name, IP Addr or Region, Mark as Trusted (Y or N). Should also show a Preview before applying. Highlight any matches to existing subnets, or which subnets are new, etc.
We will be working on enabling this transformation soon. Thanks for the feedback.
Absolutely need this feature! So many third-party iDP's don't necessarily align 1to1 with respect to claims attributes. ADFS has had this ability for quite a while now. This is the one missing feature that is keeping us on ADFS for a number of applications.
1 voteAnonymous shared this idea ·
207 votes32 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.