Forum Discussion
Surface Hub 2 - Problem with Microsoft Teams
cezarcretu We see now the partner requirements changed somewhat. Don't know when. The way I read it now is MFA for all cloud services, from any device, at any location, no exceptions. So we're now stuck with Surface Hubs and Microsoft Teams Room systems. App passwords work for SfBO and EXO on an MTR, but not Teams.
I'm not the only one seeing the irony of Microsoft forcing partners to use modern authentication and recommending app vendors switch to the graph, while simultaneously not following their own recommendations?
Hell, even ConnectWise Manage has been updated to the graph and modern authentication (did ours over the long weekend).
Tristan Griffiths , you are absolutely right and we are aware of the pain this causes. Currently the Surface Hub OS is not able to handle modern authentication but we are working hard on this. There is currently no ETA but this will be fixed soon.
Thank you,
Cezar
- cezarcretuDec 07, 2021
Microsoft
Hello Guzm0Apex,
This isn't an issue with the app itself but a sign-in issue which could be caused by different reasons. Make sure the device is fully updated and if you still have this issue, check the sign-in logs in Azure AD for any Conditional Access policies blocking the sign-in.
If you still have issues, please open a support case
Thank you,
Cezar
- Guzm0ApexDec 06, 2021Copper Contributor
Hey Cezar
I’m just checking in its been over a year since I see people have started to have this issue were teams don’t load.
any updates or fixes I haven’t found any myself we are still able to use teams on the web but once we start teams from the app it says “something went wrong” and closes and try’s to re-open but fails every time after that ive even factory reset it and still comes up with the same issue.
It has all the windows updates .
thank you .
- Steve HernouNov 09, 2020Iron Contributor
alankinane485 , I think it's also fixed in the latest big update of Windows 10 Team Edition (the native version running on Hubs) that was scheduled to be released in October but not 100% sure it's rolled out everywhere yet.
With us being back in lockdown I have not been in the office for over a month 🙂
- alankinane485Nov 09, 2020Copper Contributor
NaraeB As far as I know the issue is still there. However, you can now install Windows 10 Enterprise on the Surface 2s which is what I have done and this OS has no issue.
https://docs.microsoft.com/en-us/surface-hub/surface-hub-2s-migrate-os
- NaraeBNov 09, 2020Copper ContributorIs this issue still on-going?
- Steve HernouMar 04, 2020Iron Contributor
cezarcretu are there any updates on this topic?
We setup a CA policy last year to block basic auth for EXO/SPO for the 'Other clients' category (so older Office clients, POP, SMTP, IMAP,etc..) and even though the Surface Hub device accounts are subject to this CA, they are all still working.
On the other hand, when I look in the sign-in logs I see lots of failures from those accounts to Office 365 Exchange Online using 'other clients' but also a lot of successful logins using Exchange ActiveSync (user agent BAV2ROPC).
What is the current Microsoft recommendation for Surface Hub and MTR devices? Exclude them from all CA policies which block anything that does basic auth?