Forensics workflow
Microsoft 365 · Identity · Audit · Cloud

Microsoft 365 Account Compromise → Cloud Forensics & Cross-Platform Scoping

A structured investigation workflow for collecting Microsoft 365 evidence, reconstructing identity and user activity, checking persistence, and determining whether related activity extends into Azure or AWS.

HawkEntra IDUnified Audit LogM365 AuditAzureAWS
AUTHORIZECOLLECTIDENTITYAUDITCORRELATESCOPERESPONDREPORT
Investigation Question

Did one compromised identity affect email, cloud resources, or both?

The workflow starts with Microsoft 365 evidence and expands only when the identity, IP, application, session, or timeline creates a defensible reason to investigate Azure or AWS.

Initial signalSuspicious Microsoft 365 authentication or mailbox activity
Primary subjectUser identity, sessions, mailbox, applications, and audit trail
Cloud pivotShared identity, source IP, API event, resource, or time window
Final outputEvidence timeline, scope decision, response actions, and limitations
Evidence Sources

Each technology answers a different question.

Hawk

Collect Microsoft cloud evidence

PowerShell-based collection for tenant and user investigation packages that support account-compromise and BEC analysis.

Entra ID

Reconstruct identity activity

Review sign-ins, risk, MFA, Conditional Access, devices, applications, service principals, and identity changes.

UAL

Establish who did what

Search the Unified Audit Log for user, administrator, mailbox, file, application, and collaboration activity.

M365 Audit

Expand service-level context

Correlate activity across Exchange Online, SharePoint, OneDrive, Teams, and other audited Microsoft 365 workloads.

Microsoft Azure

Check cloud-resource impact

Review Azure Activity, resource changes, role assignments, virtual machines, network controls, and relevant diagnostic logs.

AWS

Scope separate cloud activity

Review CloudTrail, IAM, EC2, security groups, console access, API events, and source-IP or identity overlaps.

01 · AUTHORIZE & PRESERVE

Define scope before collection.

Record the incident trigger, authorized tenant, affected identity, investigation window, timezone, assigned analyst, data-retention limits, and evidence location. Preserve original exports and record collection time before analysis.

Decision: collect only from systems and tenants included in the authorized lab or incident scope.
02 · HAWK COLLECTION

Build a tenant and user evidence package.

Use Hawk to collect Microsoft cloud investigation artifacts, then preserve the output as read-only source evidence. Document modules, account permissions, collection start/end times, errors, and missing datasets.

# Representative authorized-lab collection sequence
Install-Module -Name Hawk -Scope CurrentUser
Import-Module Hawk
Start-HawkTenantInvestigation
Start-HawkUserInvestigation -UserPrincipleName user@tenant.example
Expected evidence: tenant configuration, user-focused artifacts, mailbox and forwarding context, audit-related exports, and collection notes. Exact output depends on permissions, licensing, retention, and Hawk version.
03 · ENTRA IDENTITY

Reconstruct authentication and account changes.

Review interactive and non-interactive sign-ins, source IPs, location, device state, user agent, application, authentication detail, MFA result, Conditional Access, risk, session identifiers, role changes, credential changes, device registrations, and application consent.

SigninLogs
| where TimeGenerated between (datetime(START_TIME) .. datetime(END_TIME))
| where UserPrincipalName =~ "user@tenant.example"
| project TimeGenerated, UserPrincipalName, IPAddress, Location,
          AppDisplayName, ClientAppUsed, AuthenticationRequirement,
          ConditionalAccessStatus, ResultType, CorrelationId
| order by TimeGenerated asc
04 · UAL & M365 AUDIT

Determine what the identity did after sign-in.

Search the Unified Audit Log by user, operation, workload, IP, object, and time. Review Exchange mailbox activity, inbox rules, forwarding, delegates, Send/SendAs, searches, file access, sharing, downloads, Teams activity, application consent, and administrator changes.

Search-UnifiedAuditLog `
  -StartDate $StartUtc `
  -EndDate $EndUtc `
  -UserIds "user@tenant.example" `
  -ResultSize 5000
05 · CORRELATE

Normalize the evidence into one timeline.

Convert timestamps to UTC and correlate Entra sign-ins, UAL records, Hawk exports, mailbox actions, application activity, source IPs, correlation IDs, user agents, objects, and session context. Separate confirmed evidence from inference.

Authentication→Session→M365 action→Persistence→Cloud pivot
06 · AZURE & AWS SCOPE

Expand only when a pivot supports it.

For Azure, review resource changes, role assignments, service principals, virtual-machine operations, network security groups, and diagnostic data. For AWS, review CloudTrail event history, console sign-ins, IAM changes, access-key activity, EC2 actions, and security-group modifications. AWS is a separate evidence source unless an actual identity, IP, application, or timeline relationship is demonstrated.

AzureActivity
| where TimeGenerated between (datetime(START_TIME) .. datetime(END_TIME))
| where Caller has "user@tenant.example" or CallerIpAddress == "SOURCE_IP"
| project TimeGenerated, OperationNameValue, ActivityStatusValue,
          Caller, CallerIpAddress, ResourceGroup, ResourceId
aws cloudtrail lookup-events \
  --lookup-attributes AttributeKey=Username,AttributeValue=LAB_USER \
  --start-time START_TIME --end-time END_TIME --output json
07 · CONTAIN & RECOVER

Apply controls proportional to verified scope.

Revoke sessions, reset credentials, review MFA methods, remove malicious mailbox rules, delegates or application consent, and disable affected identities when required. If cloud impact is confirmed, rotate exposed keys, remove unauthorized role assignments, restrict network access, preserve affected resources, and validate recovery.

08 · REPORT

Produce a defensible investigation record.

Document incident details, executive summary, scope, evidence sources, timeline, findings, indicators, affected identities and resources, containment, eradication, recovery, root cause, limitations, and final status. Attach hashes or filenames for exported evidence and distinguish observed facts from analyst assessment.

Evidence standard: screenshots, exports, timestamps, IPs, users, resources, and conclusions are added only when produced and verified in the authorized lab.
Technical Review

Questions this project is designed to answer.

Identity compromise

Which sign-in or account change established unauthorized access, and what authentication controls were involved?

Post-authentication activity

What mailbox, file, collaboration, application, or administrator actions occurred after the suspicious session?

Cross-cloud exposure

Was related Azure or AWS activity actually observed, or did evidence support keeping the incident limited to Microsoft 365?