Microsoft Authenticator watchOS app to be discontinued in January
If you use the Microsoft Authenticator app on your Apple Watch, be prepared to look for an alternative starting January 2023.

Yet another companion app is leaving the Apple Watch, and this time it's the two-factor authentication app, Microsoft Authenticator.
In a support post spotted by 9to5Mac, Microsoft confirmed that a new update to the Microsoft Authenticator iOS app will cause the watchOS companion app to quit working.
Microsoft suggests that anyone who currently has the watchOS app installed to delete it, as it will be nonfunctional sometime in January.
According to Microsoft, watchOS is incompatible with Microsoft Authenticator's security features.
Of course, anyone who needs to use Microsoft Authenticator to access their Microsoft account will still be able to use the app on iPhone or iPad -- it's only Apple Watch that is affected.
This marks another app that is quietly leaving the Apple Watch. In 2017, Google pulled its companion Google Maps app, but later reinstated support for it in 2020.
While eBay introduced its watchOS app in 2015, it removed it in 2017.
In 2018, enterprise messaging platform Slack depreciated its Apple Watch app.
In 2019, Niantic pulled the Pokemon Go companion app from the Apple Watch less than three years after it was introduced.
Read on AppleInsider

Yet another companion app is leaving the Apple Watch, and this time it's the two-factor authentication app, Microsoft Authenticator.
In a support post spotted by 9to5Mac, Microsoft confirmed that a new update to the Microsoft Authenticator iOS app will cause the watchOS companion app to quit working.
Microsoft suggests that anyone who currently has the watchOS app installed to delete it, as it will be nonfunctional sometime in January.
According to Microsoft, watchOS is incompatible with Microsoft Authenticator's security features.
Of course, anyone who needs to use Microsoft Authenticator to access their Microsoft account will still be able to use the app on iPhone or iPad -- it's only Apple Watch that is affected.
This marks another app that is quietly leaving the Apple Watch. In 2017, Google pulled its companion Google Maps app, but later reinstated support for it in 2020.
While eBay introduced its watchOS app in 2015, it removed it in 2017.
In 2018, enterprise messaging platform Slack depreciated its Apple Watch app.
In 2019, Niantic pulled the Pokemon Go companion app from the Apple Watch less than three years after it was introduced.
Read on AppleInsider
Comments
This isn't a show-stopper but it is annoying that I have to have my iPhone next to me to use Authenticator now (and not really being told why...)
all down to developer resourcing I suppose. Every Apple Watch owner that would use Authenticator already has to have the app on their phone anyway.
I use Microsoft Authenticator for my NAS access. I log on with the admin name and password and then it asks me for the authentication code generated through the app.
To access to the authentication app I obviously need biometrics or a PIN code too. Once I've got into the app I choose which device I want the code for and it is generated and valid for a few seconds. It renews automatically.
A watch app simplifies things so those users will be disappointed.
What was this used for? I work on a remote system using Microsoft Remote Desktop. I log into it using an app called Duo, that also logs me into my Microsoft account.
if I don’t need Authenticator to do that, what was it used for?
I'm supposing that in your current setup, if someone got hold of your username and password, they would have access to your account (although you may get message saying a new device had logged into your account). Or perhaps you have 2FA through a different means.
I’m very curious to see how PassKeys will impact the 2FA landscape.
Anyway, thanks. That clarifies things.
Like you, I'm not totally clear on PassKeys but from what I've read on the topic it seems like a more seamless and integrated 2FA model that piggybacks on top of the secure device-based biometric authentication methods already provided by the device, like Face ID, Touch ID, Windows Hello, etc. This reminds me of how third party apps on my iPhone, iPad, and Mac can use Face ID and Touch ID to authenticate with a third party app or web site. I use this with 1Password and MyChart and it's a heck of a lot easier to use than the one-time-passcode (OTP) methods that require you to open the authenticator app and search for the OTP for the app/site that just prompted me for a code. I'm assuming the PassKeys that Apple, Google, et al are moving towards are an extension and standardization of this easier to use 2FA model.
It might be needless worrying, I haven't delved deeply into the implementation details to see if there are protections in place. But at the conceptual level, I am troubled.
I don't know whether I'm more upset because they're cancelling it or because I never got the chance to use it.
The PassKeys reminds me an awful lot of ssh keys. They are cryptographically secure using asymmetric keys. Lose the key, you have to generate a new pair and get it registered with the remote servers. Need access from multiple client machines? You’ll need to copy your key to those systems. If someone gets a hold of your key, they are effectively you. It sounds like iCloud takes care of syncing your encryption key across devices, however, I don’t think it has a good solution if the encryption key is intercepted. At best, there will probably be a way to invalidate a key pair, but that presupposes that you know your keys were compromised. By the time you know that the damage may already be done. 2FA could be used to mitigate this, but key pairs and OTPs are both “something you have”, which is not true 2FA. It would need to include “something you know” (a password) or “something you are” (biometrics).