Anonymous
My feedback
-
33 votes1 comment · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
134 votes16 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
20 votes2 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
148 votes13 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
293 votes
We are currently investigating how to implement this. The expiration status is not a directory attribute so it is not straight forward how to sync it.
Anonymous
supported this idea
·
-
82 votes11 comments · Azure Active Directory » Groups/Dynamic groups · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
276 votes
We are currently investigating how we can best implement this feature.
An error occurred while saving the comment Anonymous
supported this idea
·
-
7 votes
An error occurred while saving the comment Anonymous
commented
I could see a minimum supported value here like 5 or 10 minutes to keep folks from doing crazy every minute policies... but supporting down to 15 or 10 minutes could get us to mimicking a screen lock policy for key SSO apps.
Anonymous
supported this idea
·
-
184 votes
Thanks for your feedback. Microsoft is currently working with third party MDM providers to enable this scenario. We will update this thread once we have more information to share.
Anonymous
supported this idea
·
-
35 votes6 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
103 votes
We’re working on a few features in this space that will likely help address this scenario but don’t have an ETA yet to share. Thanks to the folks who have added additional details of what they’re looking for, and if you have more scenarios for how this capability could help you please do add them as comments.
Thanks,
ElisabethAnonymous
supported this idea
·
-
207 votes
Thank you for your feedback! Would you like the feature to be controlled by the admin or available for everyone?
Thanks,
Sadie HenryAnonymous
supported this idea
·
-
16 votesunder review · 1 comment · Azure Active Directory » Application Proxy · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
47 votes
We have enabled a contains() function. We will be working on the capability to Replace().
/Luis
Anonymous
supported this idea
·
-
76 votes9 comments · Azure Active Directory » Azure AD Connect Health · Flag idea as inappropriate… · Admin →
Thanks for the feedback. Connect Health team is planning to integrate Connect Health data with Log Analytics in phases. The first stream of ADFS data will be available in 3-6 months for preview.
Please reach out to askaadconnecthealth at microsoft.com for preview request.Anonymous
supported this idea
·
The EnforceCloudPasswordPolicyForPasswordSyncedUser capability is a definite help here, but would additionally like to see the ability to sync on-premises PasswordNeverExpires to Azure AD DisablePasswordExpiration policy.
Original PHS behavior - Azure creds never expire.
EnforceCloudPasswordPolicyForPasswordSyncedUser - Azure creds always expire.
Desired behavior -- option to synchronize on-premises password never expires so that Azure expiration matches.