While making administrative logins more burdensome can be a valid security tradeoff, if you made your non-admin users use three authentication factors, it would likely raise the ire of most of your those users. He had to use Microsoft Authenticator to authenticate to a clients VPN, and then Duo to MFA into a remote desktop session. I saw an example of this when working with a colleague this morning. As you all know, helping your end users have better security hygiene is a big challenge.Īdding security always adds a burden to users. A contrast is that I've been trying to get my dad (unsuccessfully) to use a password manager for several years now. However, we are a very small team of very experienced technology professionals.

After that, I started using a password manager (1Password) and enabling multi-factor authentication (MFA) on most of my accounts, especially important ones like banks.Īt my job at DCAC, all of our team uses password managers and multi-factor authentication. Finally, after several data breaches, my password was compromised and I decided to follow best practices. I used to have terrible password practices, including using a standard password with minor changes depending on the account in use. The problem is most users practice bad password hygiene because passwords are terrible. As mentioned in the latest Microsoft Authenticator news story, some parts of these features have reached 'general availability.' During Ignite, I had the opportunity to speak with the PM team to be understand some of these enhancements.Įveryone needs passwords to provide some baseline level of security. One of the key topics at Microsoft Ignite 2022 was the security enhancements within Windows 11, and how some of these features tie back into Azure Active Directory.

Microsoft passwordless account