Hahah, sure, faggot. 99% of the time no one checks the permissions logs, or even assigns proper permissions to global accounts, breakfix, etc.
It's fucking fun as fuck.
So many people share one admin account, you can jump onto an active RDP, or even better, use one that is for outsource password reset and there you go.
With powershell, you don't even need to logon to the account, you can set redirection, mailbox mirroring and more as long as you can connect to azure ad. But this is more of pro gamer move that probably you or op has no idea about.
>but user, what about the logs?
Logs are reactive, no one has true active alarms for most accounts that are useful to you.
You can review how help desk, curries or filipinos reset users passwords and piggy back on that.
You can even use a reverse shell if they have VNC, screenconnect, or if you're on the domain, easily. Most computers have a localadmin password that's the same throughout the org that'd allow you to grab the local SAM file which you can force crack.
If you have server creds, just copy the shadowcopy of the SAM, why not.
There's many more ways, of course, but, most of the faggots on here are going to go cry foul, no, that's not possible, not on my system when at most they may run graphite that looks for event ID's that *may* be piped to a mailbox to be reviewed by a overworked, underpaid itsec guy, or worse, curries/filipinos.
And it's also friday, the netsec guy is not going to be working hard vs fucking around with the Ops teams about read only friday.
Fuck you faggot.