@JacquesQ ,
Its highly unlikely that the google crawler is trying to sigin on behalf of user. With all the details provided , it seems that the user may have used Google read aloud cloud service on the Office 365 logon page while trying to access their Exchange mailbox. The crawler does not
From the developer page for read aloud user agent, we find the following.
Google-Read-Aloud is the user agent for the Google Read Aloud service. This service enables reading web pages using text-to-speech (TTS). This service is activated when an end user has text to speech enabled and visits a page. The Read Aloud service is used by Google Go, Google Read it, Read Aloud on the Google app, and other Google text-to-speech services.
I have not seen this before . However if you continuously see this then I would filter by timestamp and see who all are the users trying to access the exchange online at the same time. Because if a MFA prompt was triggered then the user would get some notification . If its the right user , the user would know aout the logon or the activity they were trying when this log got generated. If the user whose signin identifier is shown does not know then there may be an issue. Considering the security aspect , I would always suggest to check and verify with the user what device they were using and where all they tired to logon . This is the tricky part as many a times users may not even know but may have clicked something and will miss providing all information to the IT team .
I doubt that the web crawler is trying to sign in as a user. The sigin is clearly user initiated and the user agent value says about the google web crawler. The user agent simply is the browser or application that the user may be using to access the logon page on Microsoft side. As I mentioned above the only explanation that I can think of is that the user have read aloud enabled on the browser agent and they might have tried to logon to the exchange service . and maybe abandoned the logon later but we cant be sure without checking this with the user.
So in a nutshell ,
- Should this activity create an security incident ? Yes it should. We cant be more careful these days.
- With the above details , is it a high level security issue ? No, it is not . Though it would be good for the Sec Ops team to verify with the user .
Hope the explanation helps. Should you have any further queries , feel free to let us know and we will be happy to help .
Thank you,
----------------------------------------------------------------------------------------------------------------------------------------------------------
- Please don't forget to click on
or upvote
button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how
- Want a reminder to come back and check responses? Here is how to subscribe to a notification
- If you are interested in joining the VM program and help shape the future of Q&A: Here is how you can be part of Q&A Volunteer Moderators