Forum Discussion
Busted1942
Feb 10, 2020Copper Contributor
Misleading Error Message 53004
I wanted to document an issue I have spent a few months on (off and on) in hopes that the error messaging might be improved. The use case is that I can sign-in to Teams however, when I tried to switch orgs (guest access), I am seeing a "Your sign-in was blocked" error message on the screen with a body of, "We've detected something unusual about this sign-in."... I received the same experience when using the web app or the Teams client as well as both at work and at home. When I went into Azure, the failed authentication event said (example pasted at the bottom.) The actual issue was that there was an old unaddressed risky sign-in event that was never dismissed after it was addressed in August. Of course there is a business process gap however, if the both the user facing message and the Azure failed sign-in event had pointed me in the risky sign-in direction instead of an incomplete MFA registration I would have spent considerably less time trying to resolve this issue. I understand if this post needs to be redirected to a different group but I wanted to start by documenting it here to hopefully save someone else from burning their time and MS premier (though I did not actually find the resolution as a result of that ticket) hours on this.
Date
2/10/2020, 11:34:59 AM
Request ID
e7faa82a-32e7-4d1c-8498-320946ed7500
Correlation ID
d6581197-d1a2-470b-87d9-0c3283e1a1a2
Status
Failure
Sign-in error code
53004
Failure reason
User needs to complete Multi-factor authentication registration process before accessing this content. User should register for multi-factor authentication.
User
REDACTED
Username
REDACTED
User ID
REDACTED
Alternate sign-in name
Application
Microsoft Teams
Application ID
1fec8e78-bce4-4aaf-ab1b-5451cc387264
Resource
Microsoft Teams Services
Resource ID
cc15fd57-2c6c-4117-a88c-83b1d56b4bbe
Client app
Token issuer type
Azure AD
Token issuer name
Latency
391ms
User agent
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; Win64; x64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Zoom 3.6.0)
9 Replies
Sort By
- Gousia_BegumFormer Employee
Busted1942 Looking at the correlation id, the guest user was marked as High Risk by his home tenant and the solution is guest users home tenant should deflag that event.
- TomaszfCopper Contributor
- Busted1942Copper Contributor
Trigger a risky user sign-in event to show up for a test user in Azure Portal>Azure Active Directory>Security>Risk Detections and then try to change Orgs with that user in MS Teams.
- Busted1942Copper Contributor
That is what the fix what. What can I read/learn to be able to decode correlation IDs like a pro as you seem to be able to?Gousia_Begum