Hello @harsh waghela ,
Thank you for reaching out Microsoft Q&A.
This is common behavior where a rich client is used as a browser for application sign-ins. Regarding your mention of "Password in the cloud," this occurs when a user enters their password while logging into the application, indicating a user-interactive sign-in.
For Token Protection and the Sign-In Session Status Code, you will observe the same code because the sign-in was initiated from the same network without any activity of a man-in-the-middle attack. A rich client can also act as a device browser for first-party applications, primarily during non-interactive sign-ins.
I recommend reviewing the user's sign-ins to check for any unusual activity. If everything appears normal except for the device browser behavior, you can safely ignore it. Attaching screenshot from my test tenant for reference.
I hope this information is helpful. Please feel free to reach out if you have any further questions.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Thanks,
Goutam Pratti.