Forum Discussion
Code - 50173
Hi,
I see a number of Risky Sign-ins with the code 50173 - Fresh auth token is needed. Have the user re-sign using fresh credentials. And the status is "Failure".
But I noticed the IP address captured is of another country. How to interpret the error code?
Thanks.
- Moe_KinaniBronze ContributorHi cllee,
Not sure why it shows from different country, but this message refers to token expiration and needs to be refreshed. There are some ways to extend the token lifetime like Conditional Access.
Are you checking the logs from MCAS? If not, I would check from that side as the logs more organized.
https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes- clleeBrass Contributor
Is there a possibility where someone else has also setup the access to the user account from another country?
Thanks.- Moe_KinaniBronze ContributorDo you have MFA in place?If yes, It could be false alarm.
Again I would check Microsoft Cloud App Security for more details about the incident.
Moe
- Thijs LecomteBronze Contributor
If you get an alert from Identity Protection, you can never be 100% sure why it was flagged as risky as Microsoft keeps these methods confidential.
I would suggest you check with the never if he has any clue why this login occurred ( he might be travelling, using roaming data or VPN).
If he doesn't know anything about this login, I would advise you to change his password and expire all his tokens. Even if he has MFA, his account could still be breached.
- clleeBrass Contributor
Thanks for your advice. I have reset the password.
If the status of the code shows "Failure", is that also indicating that the user account has been compromise? Or someone did successfully gain access to the account prior to this?
Or it could be just an attempt? Thanks.- Moe_KinaniBronze ContributorHi cllee,
Failure means not ‘compromised’ and didn’t get access. Anytime you mistype your password or someone tries to brute force your account, it gets logged on Azure/ MCAS.
You can use Security & Compliance Console (Compliance now)->Search->Audit Log Search. This should give you more details about the incident.
Moe