Kazzan
My feedback
-
1,062 votes
We’re continuing to investigate options for adding this support. There are technical challenges to overcome in order to make this happen. We thank you for all your valuable comments so far, and welcome any additional feedback you have on what are the most important use cases involved with these scenarios.
Kazzan
supported this idea
·
-
13 votes3 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Kazzan
supported this idea
·
-
67 votes8 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Kazzan
supported this idea
·
-
97 votes17 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
StrongAuthentication data can be read via PowerShell, but StrongAuthenticationUserDetails can’t be set via PowerShell. It is planned to expose the StrongAuthentication data via Graph, but no ETA to provide yet.
Kazzan
supported this idea
·
-
95 votes7 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Kazzan
supported this idea
·
-
79 votesKazzan
supported this idea
·
-
22 votesKazzan
commented
This is must have. Calling support when AD (and AAD Connect Server) is not online is not feasible and fast enough.
Kazzan
shared this idea
·
-
24 votes8 comments · Azure Active Directory » Self-Service Password Reset · Flag idea as inappropriate… · Admin →
Hi folks! Thank you for your feedback. We are looking into ways to make CAPTCHA better and will keep you up to date on our progress.
Kazzan
supported this idea
·
-
1 vote0 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →Kazzan
shared this idea
·
-
19 votesKazzan
supported this idea
·
-
8 votes
Thanks for the suggestion Peter. Can you give a bit more detail on the use case? You can apply conditional access policy to Azure SQL today. Is the additional requirement here to lock down access to specific devices (for example: not all compliant devices)?
-Caleb
Kazzan
supported this idea
·
-
628 votesKazzan
supported this idea
·
-
315 votes26 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
Kazzan
supported this idea
·
-
215 votes31 comments · Azure Active Directory » Role-based Access Control · Flag idea as inappropriate… · Admin →
Just wanted to post another update that this is a high priority, but we do not have any details to announce yet.
Cheers,
/Stuart and VinceKazzan
supported this idea
·
-
54 votes7 comments · Azure Active Directory » Multi-factor Authentication · Flag idea as inappropriate… · Admin →
We’ll take this in consideration as we plan new features. In the short term, we are working on Graph API‘s that will allow you to change phone numbers in the StrongAuthentication fields.
Richard
Kazzan
supported this idea
·
-
111 votes
Hi – this is not a feature we are planning in AADConnect. We’re currently designing a new feature based on a new technology that would allow us to write back users and group from AAD to various different targets – AD, other directories, applications – and hope to be able to tell you more about it in the coming months.
Rob de Jong
Kazzan
supported this idea
·
-
230 votes
We are currently working on an approach that will allow Tenant Admins to do key rollover from the Azure AD portal; without the need for PowerShell or scripting. This will be released within the next 4-6 months. Subsequently, we will release an update that will perform key rollover automatically every 30 days
Swaroop
Kazzan
supported this idea
·
-
133 votes
We hear you loud and clear! We know this is a frequent ask and we do have this on our backlog. Unfortunately, I don’t have a timeline to share right now.
Kazzan
supported this idea
·
-
191 votes
Do you really want this for Azure Active Directory Domain Services or is this for Azure Active Directory joined windows 10 machines. If so, we are looking into it.
Kazzan
supported this idea
·
-
234 votes
Hi,
Just a quick update. This is still on the roadmap, but not work that has started. The comments here are useful as we start the design. ThanksKazzan
supported this idea
·
There should be support for that for rollout of SSPR and MFA. Or for the meantime, it should at least warn in setup.