DemoContoso Ltd is a fictional company. The grade, the findings and the attack paths came from Tenant Strike’s engine reading made-up data.

Run it on your own tenant →

Logging & Alerting

Whether you would notice

Audit logs and alerts

Measured score

96

Partial assessment · 2 left out of the score

4Total
1Need attention
1In good shape
2Not verified
0Suppressed

Needs attention (1)

  • Should fixNeeds fixingWhether you would notice

    Use a monitored notification mailbox

    What this means

    Tenant notification contact gaps: No 'Technical contact' email(s) configured — service health incidents and major change announcements go to the tenant's original sign-up contact only; No Security & Compliance notification contact configured — security advisories from Microsoft (including breach notifications) may not reach your security team. Use monitored shared mailboxes ([email protected], alerts@) so notifications survive personnel changes.

    What to do

    Set the technical and security notification addresses to monitored shared mailboxes (or distribution lists) that survive individual personnel changes. Also: in each admin's personal Message Center preferences, ensure they're subscribed to relevant categories.

    Who does it
    Your IT person or provider
    How long
    About 15 minutes
    Before you change it
    If you change the technical contact to a shared mailbox that no one watches, you've moved the problem rather than fixed it. The shared mailbox needs an owner who reviews it (or it forwards to a SIEM that does).
    3 evidence rows
    Technical detailssetting, steps, evidence

    The setting

    Tenant technical & security notification contacts

    Microsoft 365 admin center → Settings → Org settings → Organization profile → Data location and contact information

    Now: Technical: (none); Security & Compliance: (none)→Should be: Both technical and security/compliance contacts set to monitored shared mailboxes on a corporate domain

    Open in the admin portal ↗

    Steps

    1. admin.microsoft.com → Settings → Org settings → Organization profile → Data location and contact information
    2. Set 'Technology contact' to a monitored shared mailbox (e.g. [email protected])
    3. Set 'Security and Compliance' contact
    4. Then: admin.microsoft.com → Health → Message center → Edit preferences
    5. Subscribe a shared mailbox to weekly digest + critical change notifications
    6. Then (for each admin): admin.microsoft.com → Health → Service health → 'Preferences' → 'Email me when incidents/advisories occur' → On

    PowerShell

    Connect-MgGraph
    Update-MgOrganization -OrganizationId (Get-MgOrganization).Id -TechnicalNotificationMails @('[email protected]') -SecurityComplianceNotificationMails @('[email protected]')

    Evidence · 3 recorded items

    • Technical notification recipients — (none)
    • Security/compliance notification recipients — (none)
    • Privacy contact — (none)

    How an attacker would use it

    Microsoft detects unusual sign-ins to your tenant and sends an alert to the on-file security contact. The address is the original signup admin's personal Gmail from 2019 — they left the company in 2021 and that mailbox is unread. The notification is sent. No one ever sees it.

    Learn more ↗

Not verified (2)

  • Not verifiedWhether you would notice

    Enable the unified audit log

    What this means

    Whether the unified audit log is ingesting can't be read with our read-only Graph access — it's an Exchange/Purview setting. Confirm it in about a minute with the PowerShell command below; if it returns False you have no forensic trail and should enable it immediately.

    How to check it

    Confirm the unified audit log is ingesting. This is an Exchange/Purview setting, so it's read (and fixed) from Exchange Online PowerShell — one command.

    Technical detailssetting, steps, evidence

    The setting

    Unified audit log ingestion (UnifiedAuditLogIngestionEnabled)

    Microsoft Purview → Audit · (state readable only via Exchange Online PowerShell)

    Now: Not readable via Microsoft Graph→Should be: UnifiedAuditLogIngestionEnabled = True

    Open in the admin portal ↗

    Steps

    1. Connect-ExchangeOnline (as a tenant admin)
    2. (Get-AdminAuditLogConfig).UnifiedAuditLogIngestionEnabled
    3. If False → Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true
    4. Or in Microsoft Purview → Audit, click 'Start recording user and admin activity' if the banner is shown

    PowerShell

    # Connect-ExchangeOnline
    (Get-AdminAuditLogConfig).UnifiedAuditLogIngestionEnabled
    # If it returns False:
    Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $true

    Evidence · 1 recorded item

    • Why we can't auto-check this — UnifiedAuditLogIngestionEnabled lives in Exchange Online, exposed only via PowerShell / the Management Activity API — not Microsoft Graph. Entra sign-in and directory logs are a separate, always-on stream and do NOT indicate the UAL's state.

    How an attacker would use it

    If the UAL is disabled, a breach leaves no trail — you can't determine what was accessed, when, or by whom. Attackers actively seek this; a tenant that left it off has pre-evaded its own future investigation. Worth the one-minute check.

    Learn more ↗
  • Not verifiedWhether you would notice

    Set security alert recipients

    What this means

    Whether the high-severity Defender alert policies have email notifications enabled with monitored recipients — but Microsoft only exposes this setting through PowerShell, or through a preview API we don't yet depend on. Verify with Exchange Online PowerShell using the command below — it takes about a minute.

    How to check it

    Run the PowerShell command below to review the current setting.

    Technical detailssetting, steps, evidence

    The setting

    Set security alert recipients

    Not exposed via Microsoft Graph as of 2026. Available only via Exchange Online PowerShell.

    Now: Not readable via Graph→Should be: For each High-severity policy: NotificationEnabled = True AND NotifyUser points at a monitored shared mailbox/DL (not empty, not a personal email). Critical policies to verify: Creation of forwarding/redirect rule; Suspicious email forwarding activity; Elevation of Microsoft Entra role; Elevation of Exchange admin privilege; Phish delivered due to an ETR override; User restricted from sending email.

    Open in the admin portal ↗

    Steps

    1. 1. Open PowerShell as your tenant admin
    2. 2. Connect-ExchangeOnline
    3. 3. Connect-IPPSSession # connects to Security & Compliance, separate from regular ExchangeOnline Get-ProtectionAlert | Where-Object Severity -eq 'High' | Select-Object Name, NotificationEnabled, NotifyUser | Format-Table -AutoSize
    4. 4. Review: For each High-severity policy: NotificationEnabled = True AND NotifyUser points at a monitored shared mailbox/DL (not empty, not a personal email). Critical policies to verify: Creation of forwarding/redirect rule; Suspicious email forwarding activity; Elevation of Microsoft Entra role; Elevation of Exchange admin privilege; Phish delivered due to an ETR override; User restricted from sending email.

    PowerShell

    Connect-ExchangeOnline
    Connect-IPPSSession  # connects to Security & Compliance, separate from regular ExchangeOnline
    Get-ProtectionAlert | Where-Object Severity -eq 'High' | Select-Object Name, NotificationEnabled, NotifyUser | Format-Table -AutoSize

    Evidence · 1 recorded item

    • How to verify — Connect-ExchangeOnline → Connect-IPPSSession # connects to Security & Compliance, separate from regular ExchangeOnline Get-ProtectionAlert | Where-Object Severity -eq 'High' | Select-Object Name, NotificationEnabled, NotifyUser | Format-Table -AutoSize
In good shape (1)
  • In good shapeWhether you would notice

    Enable mailbox auditing

    Judged: Organization configuration. Mailbox auditing is on by default for the organization. Whether individual mailboxes bypass it is not read.

    Technical detailssetting, steps

    The setting

    Organization mailbox auditing

    Exchange Online PowerShell: Set-OrganizationConfig

    Now: Meets the standard→Should be: AuditDisabled = false

    Open in the admin portal ↗

    PowerShell

    Connect-ExchangeOnline
    Set-OrganizationConfig -AuditDisabled $false