For Microsoft Teams I have no choice but to direct the call to a Twilio number and use a script to answer it and automatically hit #.
If you want 2FA, have support for hardware keys. Period.
For Microsoft Teams I have no choice but to direct the call to a Twilio number and use a script to answer it and automatically hit #.
If you want 2FA, have support for hardware keys. Period.
Hardware keys are supported on Teams, along with software phones (that have a static number / extension) and a linked desktop/mobile app.
In fact FIDO2 hardware keys like Yubikey are part of what Microsoft refers to as ‘passwordless’ - see https://docs.microsoft.com/en-us/azure/active-directory/auth...
I assume you aren’t an admin on the account just because otherwise you could just disable 2FA properly rather than disabling it with a weird twillio workaround, although I have to give you credit, this is the most effort I have seen someone put in to subvert a security policy.
An app doesn't work for me either, When I have a big rack-mounted immobile desktop that should if anything BE the 2FA device, if anything, not a 6-inch easily-stealable device.
You could use it to unlock a single oauth account that you could then use to login to other places. Problem with those systems is trading privacy for convenience.
Why it's a feature: if you lose a key you can log in with another key and disable the lost key.
If you lose your house key you have no option but to change the lock, if you want to be safe from thieves.
IMO it's a mis-feature and will keep it from eliminating passwords. In fact I think it will only reinforce password use as the one good case for it is to lock your password manager.
There is absolutely nothing stopping you from making a copiable FIDO key, and, in fact, most Bitcoin hardware wallets are just that, since they come with FIDO apps and you can copy the keys over to another hardware key. Or, you can write some Arduino firmware to make your own, copiable, FIDO2-compatible key.
Thanks for raising this point though. Lack of copy-ability is more an implementation issue than a problem with the standard.
The protocol is open, though, so in theory you could semi-easily make your own FIDO2 key out of commodity hardware. The Solo 2 Hacker edition might also be copiable.
Not only do only about half a dozen services I use actively support hardware security keys, even fewer support enrolling more than one. Worse, many only support SMS 2FA as the backup option, which I just can't abide.
Seriously, deprecate SMS already. I deprecated it 10 years ago.