This repository was archived by the owner on Nov 16, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please see 5 common queries for contribution.
Recent security alerts
Return triggered security alerts in the last 24 hours.
Signins by username
Return signin activity by username from the Azure SigninLogs table/log.
Signins by ip
Return signin activity by one or more ip address from the Azure SigninLogs table/log.
Office365 activity by username
Return activity from the Office365 unified audit log by username.
Office365 activity by ip
Return activity from the Office365 unified audit log by one or more ip addresses.
Use case
I usually start with
Recent security alerts
, look for obvious anomalous behaviour. Then i copy the unfamiliar IPs and runSignins by ip
and look at the activity for that IP. I compare it withSignins by username
. Then i runOffice365 activity by ip
to see what activity was done by this IP/user and usually this is enough to confirm compromise or not.