What does that mean? It means all users will have to register for some form of MFA by default within the first 14 days after first sing-on. That is one good reason to use OATH TOTP Hardware tokens with Azure MFA.Īlso remember that when you setup a new Azure tenant, it is possible security defaults are already enabled. So you want to be able to deploy MFA to all of your users, even those who don’t have access to a (mobile) phone. No matter how good your communication plan, some users just don’t want to install the Microsoft Authenticator app. There are also users who simply don’t want to install any work related apps on their personal phones. Perhaps you never thought about it but, many customers have users who don’t have a phone available when they need to authenticate and use MFA. Although in public preview, I’m very pleased with OATH TOTP Hardware tokens support in Azure. Personally I prefer other methods like FIDO2 or simply go with the Microsoft Authenticator app (Software OATH token ) installed on my phone.

In this post we’ll be looking at using OATH TOTP Hardware tokens with Azure MFA instead of other MFA options.

The past few post I mainly wrote about Windows Information Protection and although it is a nice series of posts, I thought it’s about time to write about another topics.

Azure security defaults