Dec 15 2022 04:08 AM
Dec 15 2022 04:08 AM
According to this article:
The Microsoft Authenticator app is being discontinued on Apple Watch. I find this very disappointing. I used it many times per day. Yes, it was a bit buggy and unreliable, but it sure was better than picking up my phone every time! Please keep supporting the Watch app!
Dec 21 2022 02:17 AM
Dec 22 2022 01:18 AM
Dec 23 2022 05:07 PM
Dec 23 2022 08:43 PM - edited Dec 23 2022 08:44 PM
This is one of the most disappointing announcements to come out of Microsoft - it was a killer feature of the AzureAD/Authenticator combo and something I relied on and promoted heavily as part of rolling it out - and was much loved by those who used it!
I remain hopeful that this is reconsidered - for those that have deployed such solutions it was a really great way to show how frictionless MFA can be…
Dec 28 2022 08:47 AM
Extremely bad move on Microsoft's behalf and totally useless. Just fix the issue you have with Face ID and use the standard bypass of this request when the watch is worn and unlocked... Seriously, this is a really bad move.
Jan 10 2023 09:04 AM
Jan 14 2023 10:35 AM
Jan 26 2023 01:10 PM
Jan 28 2023 01:48 AM
Jan 28 2023 04:20 PM
Some people cannot use their phones for Microsoft Authenticator. There are certain situations where phones with cameras are not allowed. So, the phone is secured and an Apple Watch is used to respond to MFA push notifications.
If support for Apple Watch is removed, it can mean a significant expense for organizations and particularly for contractors that don’t get phones provided to them. It means switching to an Android phone with no camera, most of which are expensive rugged models, or trying to find some other watch that will continue to support Microsoft Authenticator and work with iPhones, if there is such a watch. It can also mean the expense of another monthly phone bill.
Please consider the impact that this will have, particularly with such short notice.
Jan 28 2023 06:31 PM
The only explanation I can find for dropping support for the companion app for watchOS is that it’s "due to it being incompatible with Authenticator security features." The only place I can find this in Microsoft's documentation is in the How to use number matching in multifactor authentication (MFA) notifications - Authentication method... article. In that article, it says that Microsoft will enforce the number match experience tenant-wide for all users starting February 27, 2023. Because of the similar timeframe, it's likely this feature that is incompatible. Further evidence of that is in Microsoft's response to a post in the New Microsoft Authenticator security features are now available! article: "Additional Context preview is supported for Apple Watch. However, if the user has Number Matching enabled, they will be unable to use the Apple Watch for authentication. We are working with Apple to address this limitation."
I don't understand why this can't be resolved since a similar number matching feature is working with Microsoft personal accounts. In fact, it's how I authenticated before writing this post. The only difference I see is that I'm prompted to choose one of three numbers when using my Microsoft account while the Azure AD number matching feature requires entering the number. Apple Watch allows entering numbers several ways so I don't see why this would be a limiting factor.
If number matching is the issue, I hope Microsoft will give admins the option to have users select one of x numbers instead of entering a number so that the watchOS companion app can continue to work, at least until the incompatibilities can be resolved.
Jan 31 2023 05:57 AM
As a Help Desk tech, I authenticate to many services each day. Being able to tap "Approve" on my watch makes the login flow much easier than "pull out phone, faceID to phone, open Authenticator app, faceID again, then tap approve". I've also been getting users moved over from SMS to Microsoft Authenticator and touting the convenience of "just tapping approve on your watch" as compared to getting an SMS or call and entering a code.
If I can't use the Authenticator app, I'll just need to set up a third-party TOTP app that I can sync to my watch for ease of access.
Feb 07 2023 07:52 PM
Just hopping on to echo the other sentiment in this thread - removing this feature is a major step backwards and a huge disappointment. As a Systems Engineer, I used this feature several dozen times a day. It offered an excellent blend of security and convenience. I hope Microsoft revisits this decision.
Feb 16 2023 02:39 PM
Feb 20 2023 11:57 PM
@DJTentman84 I'm extremely disappointed with this announcement. Today I went to approve a notification on my watch, to find that only the Dismiss option was available & the app has been removed from my watch.
I used this multiple times a day & is so convenient.
Bad move Microsoft!
Mar 07 2023 05:33 PM
Mar 13 2023 01:12 PM
This is really bad... I also used a lot the approval button option on my iwatch, yes with some glitches, but it save me a lot of time.... If I grab my phone, it takes a lot more of time...
It's a shame than a billion dollar company, can't figure it out how to make the iwatch "approval" button works again.... If they can't make it work? Then How do Microsoft expect other developers keep using your tools to make hybrid solutions?
Now than we are speaking of.... please REMAKE Microsoft Authenticator.... it needs to be more usable, you need to think like users, not developers
iWatch - Notification, turn the wrist, click approve.
Phone: Notification, Unblock phone, go to notifications or open the Microsoft Authenticator App, unblock the Authenticator App, Approve...
Some one knows if other watches work with authenticator to approve as simple as iwatch was?