04-10-2019 11:18 PM
Below is the issue with Microsoft Teams when conditional access is configured (Issue exist for non-federated environment as well)
When I click on the ‘X’ mark to close the message “You cannot access this right now” I am prompted to enter my credentials again. When I click on the ‘X’ again it loads the MS Teams client with below error:
D'oh! Something went wrong...
Restart
If that doesn't work, try signing out and back in.
desktop-c501e9c8-a6b2-47d5-b8ef-b5776b580f40
Error code - 4c7
There's a more permanent way to sign in to Microsoft Teams. If you're having trouble completing the process, talk to your IT admin.
(Attached is the screen shot of the error message)
D'oh! Something went wrong...
Restart
If that doesn't work, try signing out and back in.
desktop-c501e9c8-a6b2-47d5-b8ef-b5776b580f40
Error code - 4c7
There's a more permanent way to sign in to Microsoft Teams. If you're having trouble completing the process, talk to your IT admin.
As per the Microsoft Teams desktop client logs:
Tue Apr 09 2019 21:07:13 GMT+0530 (India Standard Time) <5580> -- info -- Modern authentication failed here, but you'll still be able to sign in. Your status code is 4c7. diag:0
I do Microsoft Teams to not launch when a user clicks on the ‘X’ of the Conditional Access message
04-11-2019 12:35 AM
That's because the Teams client fallbacks to using a different auth method upon detecting the failure. It shouldn't trigger if the failure is intentional, as is the case with CA, so this is a bug in my book. Open a support case and have it reported.
04-11-2019 01:08 AM
@Vasil Michev Thank you for your response. I have created a ticket with the support team. Let's see what they have to say.
I shall kept you updated about how this goes.
04-12-2019 09:04 AM
@ApoorvaKasbekar The support team informed me that they have routed the request to the product group team.
04-18-2019 11:46 PM
Microsoft got back to me stating this is by design. Annoying but true. @Vasil Michev
04-19-2019 12:04 AM
Let me see if I can get someone from the Teams team to look into this...
04-26-2019 08:40 PM
Any luck? @Vasil Michev
04-27-2019 08:51 AM
Sorry, forgot to follow up here. It's confirmed as bug, but no idea when it will be fixed.
06-05-2019 06:15 AM
@Vasil Michev- Any updates on this? Is this already on the known issues page?
https://docs.microsoft.com/en-us/microsoftteams/known-issues
Regards,
Kailash
06-05-2019 10:35 AM
Havent heard anything, will follow up...
08-14-2019 12:17 AM
Any news on this?
I can see that there are currently two similar bugs, which is connected to MS teams and conditional access.
Do we know if this is being actively worked on or how to work around (and with thew CA)?
01-29-2020 09:17 PM
05-14-2020 12:53 AM
@Vasil Michev Any updates on this? I'm having the same problem when having been added as a guest to a Teams org
08-05-2020 07:14 AM
@ApoorvaKasbekar we are having the same problem with a few of our users. Nothing we have tried fixes the issue. Are there any updates from Microsoft on this?
08-05-2020 08:52 AM
I am seeing this issue pop up over the last week across two different organizations.
The only way I can get teams to launch is to run teams as an admin....
Same error code as @h892gu .
10-19-2020 10:22 AM
This is still happening now for several of our users and they can only access Teams on company provided machines on our Network via VPN. I have not experienced this issue myself.