Because I also have my normal phone as a backup for this purpose in case out in the field something happens to my work phone. And my personal phone is rooted.
The main problem as I see it is if I have to download authenticator onto my personal device because something has happened to my work device. That’s the only way I could see this being a problem since I use Graphene OS on my personal phone. Even then I would probably just use the authenticator on my work computer rather than going to that trouble.
Only if the company supports OTP methods for Entra login (logging in to M365 account).
But I’d say most don’t anymore, as there has been a push towards Microsoft Authenticators push-method for a while (where the website/app shows a number and you have to type it in to the authenticator), as it is a slightly safer method than OTP, and can be used passwordless.
It also made people ready for passkeys, as the authenticator supports easy activation off passkey on accounts that are saved with push-method (you pretty much just click a button in the app), and authenticator is easy to set up on the admin side if you require device bound and attestation for passkey.
You can use other authenticators. I use ente auth for my microsoft account
I can’t. The authenticator for my job was set up on my work device by my IT department.
If your work requires you to have a Microsoft Authenticator-compatible device, they should provide you with one.
Which would never be rooted or jailbroken in the first place so why even bring it up in this this context?
Because I also have my normal phone as a backup for this purpose in case out in the field something happens to my work phone. And my personal phone is rooted.
Oh yeah I get it, I was mostly answering the “why bring it up”, since this whole chain of comments started because of the comment I quoted.
Sucks to have that. Have you tried asking IT if you could use a different one?
The main problem as I see it is if I have to download authenticator onto my personal device because something has happened to my work device. That’s the only way I could see this being a problem since I use Graphene OS on my personal phone. Even then I would probably just use the authenticator on my work computer rather than going to that trouble.
That sucks. I refused so they gave me a Yubikey instead.
I have a yubikey (two actually, one from a previous employer). New company won’t actually let me use it.
My work MS account requires MS authenticator specifically, can’t use another 2fa app
Depends on how your M365 tenant is configured. Both conditional access policies and authentication strengths can enforce the requirement
Only if the company supports OTP methods for Entra login (logging in to M365 account).
But I’d say most don’t anymore, as there has been a push towards Microsoft Authenticators push-method for a while (where the website/app shows a number and you have to type it in to the authenticator), as it is a slightly safer method than OTP, and can be used passwordless.
It also made people ready for passkeys, as the authenticator supports easy activation off passkey on accounts that are saved with push-method (you pretty much just click a button in the app), and authenticator is easy to set up on the admin side if you require device bound and attestation for passkey.