Forum Discussion
macOS 10.15.4 Internet Accounts Intune device not recognized
- Apr 01, 2020
ollie_bk Still no fix. Microsoft and Apple would need to acknowledge the issue before a fix will be worked on. If someone from Microsoft is working on this then please acknowledge here so that we can know this is being worked on.
careyjung - Seeing the same on a newly updated Mac. Did you ever find a solution to this?
ollie_bk Still no fix. Microsoft and Apple would need to acknowledge the issue before a fix will be worked on. If someone from Microsoft is working on this then please acknowledge here so that we can know this is being worked on.
- alta94May 08, 2024Copper Contributor
- andreas_koerberApr 15, 2020Copper Contributor
Does anybody know that this issue was acknowledged either by Microsoft and/or Apple and they are working on a fix?
If not can anyone file a bug or open a support ticket?
- SyswpitApr 15, 2020Brass Contributor
andreas_koerber
I created a ticket, but as always, you are given a support agent that is there to help with level 1 issues. They can't really escalate bugs higher up until they are fixed. They will close the ticket and tell you put it on feedback.azure.com. So yeah...
- thinkladApr 06, 2020Copper Contributor
Aaron Marks Same here, been testing within our own org and seem to confirm that was introduced in 10.15.4 (and not fixed in current beta 1 for 10.15.5). Oddly, this seems to work for some people on 10.15.4.
10.15.4 https://support.apple.com/en-ca/HT210642 this feature, which sounds somewhat adjacent: "OAuth authentication support with Outlook.com accounts for improved security". It could be that the new Exchange implementation in Catalina mistakes O365 accounts for consumer Office.com accounts, but that is pure speculation on our side.
- Aaron MarksApr 06, 2020Iron Contributor
If this is happening only for some people and not for others then I'd imagine that it has to do with a conditional access requirement that affect some people and not others.
- thinkladApr 06, 2020Copper Contributor
Microsoft pushed Company Portal 2.3.200301 as part of the Slow Ring sometime on 6 April; once the update is installed, it looks like for us, authenticating first while on the corporate VPN (so Conditional Access doesn't apply) allows to get a more durable OAuth token even once disconnected from the corporate network (tested by a few of my colleagues over the past few hours, now testing on my machines).
Update: it looks like the issue persists after all, I had to re-authenticate after about an hour. Sorry about the false hope.
Update 2:
the workaround seems to work for users that have a single macOS machine (with or without iCloud Keychain enabled) but fails for users with multiple macOS devices + iCloud Keychain sync, presumably because the Keychain sync attempts to copy the original OAuth token to other Macs, triggering the re-auth.Nope.