Conditional access for Microsoft Teams causing issues

[Apoorva_MSGTECH]

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.

1. 
   Click on Microsoft Teams client
2. Enter the username
3. You are redirected to the organization sign-in page
4. Enter the Password and you receive the message, “You cannot access this right now” (Everything seems fine until now)
5. Click on the ‘X’ mark to close the above message
6. You are prompted with a window to enter your username (The user should not be provided with a window to enter his user name again)
7. Click on the ‘X’ mark to close the new sign-in page window and the Microsoft Team client loads with the following error message. (Microsoft Teams client should not load with the error once you click on the ‘X’ in step 5.

(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

[#2]

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.

[#3]

@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. 

[#4]

@Apoorva_MSGTECH The support team informed me that they have routed the request to the product group team. 

[#5]

Microsoft got back to me stating this is by design. Annoying but true. @Vasil Michev 

[#6]

Let me see if I can get someone from the Teams team to look into this...

[#7]

Any luck? @Vasil Michev 

[#8]

Sorry, forgot to follow up here. It's confirmed as bug, but no idea when it will be fixed.

[#9]

@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

[#10]

Havent heard anything, will follow up...

[#11]

@Vasil Michev 

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)?