When trying to login to Teams on a remote computer in a different country than my host computer I get error 53003. It seems to be linked to conditional access policy, but it's not clear how. Is there a workaround for this problem?

Question

I'm trying to connect to a remote computer via Azure VDI from another country. The connection is fine, but when I try to login to Teams I get error 53003.

My coworkers tell me that connecting to the remote computer from another computer in the same country and signing into Teams works fine. And logging into Teams directly from a computer in the country of the host computer works fine.

But connecting to the remote computer from the host computer country then into Teams from the remote computer, doesn't work. This behavior is consistent with the Teams app or Microsoft Edge web browser.

Any ideas? Or workarounds?

Answer 1

Hi @A A

There is a Conditional Access policy (error 53003) that is blocking your sign in. If an Administrator who has access to Azure AD checks your recent sign-ins they will be able to track down which Conditional Access Policy is blocking you.

There is no way around this policy unless they exclude you from the policy that is blocking your sign-in.

Troubleshooting sign-in problems with Conditional Access

https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/troubleshoot-conditional-access

-------------------------------

If this is helpful please accept answer.

Answer 2

Hello @A A ,

Welcome to the MS Q&A Forum.

As @Dillon Silzer stated, error failure 53003 means your sign-in request was blocked due to a conditional access policy configured on the Tenant where you tried to authenticate. Means, Tenant Admin configured CA Policy to control what a specific user can access, and how and when they have access: block user/group membership or block based on the specific location/device/application, etc. CA sign-in logs in Azure AD should show the reason for the failure. There are could be hundreds of different scenarios on why access was blocked. Depending on the CA Policy configuration itself.

First reason which came on my mind, as example, access could be blocked based on the 'User-Risk' Score. There is the list of Risk types and detection.

Above just one simple example and there are so many flavors. Means, without reviewing the sign-in logs details it's a little bit complicated to provide the more accurate answer.

Hope this information will help you in your investigation.

Please let me know if you have any additional questions or concerns.

Sincerely,
Olga Os