Version 0.3.0
Scanned August 12, 2026 at 02:20 PM UTC
Mode dry_run
Organization Contoso Demo (dry-run)

Your security at a glance

3 of 4 still not fully working.

8
Licensed capabilities detectedacross all detected licenses
4
Prioritized capabilitiesidentity, endpoint priority packs
1
Fully working25% realized; of 4 prioritized capabilities
3
Need attentionof 4 prioritized capabilities
How to read this report

Microsoft licenses often include powerful protections with confusing product names. Below we translate those into everyday outcomes, then show where setup still looks incomplete. Product names and technical IDs are available in each finding's evidence and the technical section at the bottom.

7
Needs attention gap
3
Partly set up partial
1
Looking good ok
0
Not in your plan not_licensed
1
Check pending skipped
0
Could not verify error

What you already pay for

These are protections included in the licenses we detected — described by what they do for your business, with licensing details shown beneath each card.

Needs attention

Smarter sign-in rules

Microsoft name: Conditional Access

What it does. Decide who can sign in, from where, on which devices, and whether they must prove it is really them (for example with multi-factor authentication).

Why it matters. Passwords alone are not enough. Good sign-in rules stop many everyday account takeovers before damage is done.

If it is not set up. Your licenses include advanced sign-in rules, but they may still be loose or incomplete.

Included through license SKU(s). SPE_E5

Matching service plan(s). AAD_PREMIUM_P2

Needs attention

Deep protection and visibility on PCs and devices

Microsoft name: Microsoft Defender for Endpoint P2

What it does. See attacks on laptops and servers in more detail, find weak software, and respond before a single infected PC becomes a company-wide problem.

Why it matters. Devices are where people work. If they are not enrolled in advanced protection, you are flying partly blind.

If it is not set up. You may be paying for advanced device protection on seats that are not fully enrolled.

Included through license SKU(s). SPE_E5

Matching service plan(s). DEFENDER_ENDPOINT_P2

Partly set up

Watchdogs on your on-site directory (if you still have one)

Microsoft name: Microsoft Defender for Identity

What it does. Spot attackers moving through traditional office servers and Active Directory, not only cloud sign-ins.

Why it matters. Many organizations still rely on on-site domain controllers. Cloud-only tools cannot see every attack path there.

If it is not set up. Identity threat sensors may be missing or unhealthy, so on-site directory attacks stay invisible.

Included through license SKU(s). SPE_E5

Matching service plan(s). No matching service plan reported

Partly set up

Stronger email and file threat protection

Microsoft name: Microsoft Defender for Office 365 P2

What it does. Open risky attachments and links in a safe way, catch advanced phishing, and investigate email threats faster when something slips through.

Why it matters. Most business breaches still start with email. Better email protection reduces ransomware and invoice fraud.

If it is not set up. Extra email protections in your license may still be off, in test mode, or only covering a few people.

Included through license SKU(s). SPE_E5

Matching service plan(s). THREAT_INTELLIGENCE

Needs attention

Stronger control over admin accounts

Microsoft name: Microsoft Entra ID P2

What it does. Give people powerful admin rights only when they need them, and get better tools to catch risky sign-ins on high-value accounts.

Why it matters. Admin accounts are the keys to your email, files, and business apps. If one is stolen, an attacker can look like a trusted employee.

If it is not set up. You are paying for stronger admin protections that are not fully turned on yet.

Included through license SKU(s). SPE_E5

Matching service plan(s). AAD_PREMIUM_P2

Fully working

Alerts when a sign-in looks suspicious

Microsoft name: Microsoft Entra ID Protection

What it does. Automatically spot odd sign-in behavior (impossible travel, leaked passwords, unfamiliar locations) and require extra proof or block access.

Why it matters. Attackers often use valid passwords. Risk detection helps catch the session even when the password was correct.

If it is not set up. Suspicious-sign-in protection is included in your plan but may not be enforcing anything yet.

Included through license SKU(s). SPE_E5

Matching service plan(s). AAD_PREMIUM_P2

Needs attention

A central security command center in the cloud

Microsoft name: Microsoft Sentinel

What it does. Bring security signals together in one place, detect patterns humans miss, and automate parts of incident response.

Why it matters. Without a place that correlates events, teams drown in alerts from many products and miss the story that ties them together.

If it is not set up. A security workspace may exist, but few detections or smart analytics are turned on.

Included through license SKU(s). MICROSOFT_SENTINEL

Matching service plan(s). MICROSOFT_SENTINEL

Needs attention

Guardrails so sensitive data is harder to leak

Microsoft name: Microsoft Purview Data Loss Prevention

What it does. Warn or block people when they try to share credit cards, health data, or other sensitive information in the wrong place.

Why it matters. Accidental oversharing is common. Guardrails protect customers and reduce regulatory and reputational harm.

If it is not set up. Data-protection rules may be missing or still in "test only" mode, so nothing is enforced yet.

Included through license SKU(s). SPE_E5

Matching service plan(s). MIP_S_CLP2

Top things to do first

Ordered by what protects the most with the least effort. Each is written so you can hand it to IT.

  1. Require multi-factor authentication for admins and block legacy email sign-in methods that skip modern security prompts ~a few hours
    Some sign-in protections are present, but the full set is not enforced yet (multi-factor authentication and/or blocking outdated sign-in methods).
    Next step: Require multi-factor authentication for admins and block legacy email sign-in methods that skip modern security prompts.
  2. Create equivalent Conditional Access policies for MFA and legacy-authentication blocking in report-only mode ~a few hours
    Security Defaults already includes baseline MFA protection and blocks outdated sign-in methods. Your plan also includes smarter sign-in rules you can customize, but that paid capability remains unused.
    Next step: Create equivalent Conditional Access policies for MFA and legacy-authentication blocking in report-only mode. Validate coverage, exclusions, emergency access, and sign-in impact; then perform a controlled cutover from Security Defaults to the validated policies.
  3. Create an Access Review for your Global Administrators and guest users (monthly or quarterly), then review the first round of results ~a few hours
    Your plan can periodically confirm who still needs powerful access and clean up old guest accounts. That process does not look set up yet.
    Next step: Create an Access Review for your Global Administrators and guest users (monthly or quarterly), then review the first round of results.

Effort is a rough guide, not a quote.

Where you may not be getting the full benefit

Each item is written for owners and busy admins. Use the suggested next step in a conversation with your IT partner.

Filter: Workload: Showing 12 of 12
Needs attention

Admin accounts still have "always on" superpowers

● High severity ⏱ ~days 👥 admin Identity

Admin superpowers appear permanently on. Time-limited admin access (included in your stronger identity plan) does not look like it is being used.

Suggested next step: Ask IT to turn on time-limited admin access for your top admins first (Global Administrator and similar roles).

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-pim-unused

Needs attention

Move from Security Defaults to customizable sign-in rules

● High severity ⏱ ~a few hours 👥 all users Identity

Security Defaults already includes baseline MFA protection and blocks outdated sign-in methods. Your plan also includes smarter sign-in rules you can customize, but that paid capability remains unused.

Suggested next step: Create equivalent Conditional Access policies for MFA and legacy-authentication blocking in report-only mode. Validate coverage, exclusions, emergency access, and sign-in impact; then perform a controlled cutover from Security Defaults to the validated policies.

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-security-defaults-on

Needs attention

Some PCs may not be enrolled in advanced device protection

● High severity ⏱ ~days 👥 devices Endpoint

You appear to pay for advanced device protection on many seats, but relatively few devices are enrolled.

Suggested next step: Compare licensed seats to enrolled devices and enroll the missing ones (often through your device management tools).

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: mde.api.machines, graph.subscribedSkus

Limitations: None reported

Open Microsoft admin page

Technical ID: mde-onboard-gap

Needs attention

Set up periodic access reviews for admins and guests

● Medium severity ⏱ ~a few hours 👥 admin Identity

Your plan can periodically confirm who still needs powerful access and clean up old guest accounts. That process does not look set up yet.

Suggested next step: Create an Access Review for your Global Administrators and guest users (monthly or quarterly), then review the first round of results.

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-access-reviews-unused

Needs attention

Powerful accounts that nobody uses are still switched on

● Medium severity ⏱ ~days 👥 admin Identity

Some powerful accounts are still switched on but have not been used recently. Unused admin accounts are a favorite target for attackers.

Suggested next step: Review enabled admin accounts that have not signed in for a long time; disable or remove access you no longer need.

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-dormant-privileged

Needs attention

Guardrails against accidental data leaks may not be active

● Medium severity ⏱ ~a few hours 👥 data Purview

You appear to pay for data-leak protection that is not meaningfully enforced yet. Confirm in the Purview portal.

Suggested next step: Start with a simple policy for email and cloud files that detects obvious sensitive data, then move from "test" to "enforce" after a short tuning period.

Evidence and Microsoft admin page

Confidence: Low confidence — verify in portal

Data sources: secureScore.controlScores (proxy)

Limitations: Secure Score proxy — verify DLP enforce mode in Purview portal; Based on Microsoft Secure Score signals — confirm the real setting in the Microsoft 365 / security admin portal before treating this as definitive

Open Microsoft admin page

Technical ID: pur-dlp-not-enforced

Needs attention

Behavior-based detection may still be switched off

● Medium severity ⏱ ~a few hours 👥 all users Sentinel

Behavior analytics that learn normal patterns for people and devices still looks switched off.

Suggested next step: Ask your security admin to turn on behavior analytics (UEBA) in the security workspace and connect the main data sources it needs.

Evidence and Microsoft admin page

Confidence: Medium confidence

Data sources: azure.arm.securityInsights

Limitations: None reported

Open Microsoft admin page

Technical ID: sen-ueba-not-enabled

Partly set up

Powerful accounts may sign in without strong extra checks

● High severity ⏱ ~a few hours 👥 all users Identity

Some sign-in protections are present, but the full set is not enforced yet (multi-factor authentication and/or blocking outdated sign-in methods).

Suggested next step: Require multi-factor authentication for admins and block legacy email sign-in methods that skip modern security prompts.

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-ca-priv-gaps

Partly set up

Your security command center may have few alarms turned on

● High severity ⏱ ~a few hours 👥 all users Sentinel

Some detection alarms are on, but coverage still looks light for a paid security command center.

Suggested next step: Enable a starter set of detection rules for sign-ins, email, and devices, then expand coverage with your IT or security partner.

Evidence and Microsoft admin page

Confidence: Medium confidence

Data sources: azure.arm.securityInsights

Limitations: None reported

Open Microsoft admin page

Technical ID: sen-analytics-rule-coverage

Partly set up

On-site directory servers may lack attack sensors

● Medium severity ⏱ ~days 👥 all users Defender

We could not confirm whether on-site directory attack sensors are installed. If you still run office domain controllers, ask IT to verify.

Suggested next step: Confirm whether you still use on-site directory servers; if yes, install and health-check the identity sensors on each one.

Evidence and Microsoft admin page

Confidence: Low confidence — verify in portal

Data sources: secureScore.controlScores (proxy)

Limitations: Secure Score proxy — verify MDI sensors in the Defender portal; Based on Microsoft Secure Score signals — confirm the real setting in the Microsoft 365 / security admin portal before treating this as definitive

Open Microsoft admin page

Technical ID: mdi-sensors-missing

Check pending

Turn on Safe Links and Safe Attachments for everyone

● High severity ⏱ ~a few hours 👥 all users Defender

We cannot automatically confirm whether extra email protections (Safe Links and Safe Attachments) cover everyone. Ask IT to check Preset security policies in the Microsoft Defender portal, or run Exchange Online PowerShell (Get-ATPProtectionPolicyRule).

Suggested next step: Open Preset security policies in the Defender portal and turn on Standard protection for all users, or confirm with Exchange Online PowerShell.

Evidence and Microsoft admin page

Confidence: Low confidence — verify in portal

Data sources: Not reported

Limitations: Email policy config is PowerShell-only; not verified automatically

Open Microsoft admin page

Technical ID: mdo-p2-policies-default

Looking good

Risk-based sign-in protection

● High severity ⏱ ~a few hours 👥 all users Identity

Suspicious sign-ins and risky accounts appear to trigger automatic extra checks or blocks.

Suggested next step: Turn on risk-based sign-in protection in stages — start by requiring extra verification when Microsoft marks a sign-in as risky.

Evidence and Microsoft admin page

Confidence: High confidence

Data sources: microsoft.graph

Limitations: None reported

Open Microsoft admin page

Technical ID: id-idprotect-off

Technical details (product names, SKUs, check IDs)

Subscribed SKUs

Part number Status Units Service plans
SPE_E5 Enabled 87 / 100 AAD_PREMIUM_P2, MFA_PREMIUM, ADALLOM_S_O365, EQUIVIO_ANALYTICS, LOCKBOX_ENTERPRISE, MIP_S_CLP2, THREAT_INTELLIGENCE, DEFENDER_ENDPOINT_P2
MICROSOFT_SENTINEL Enabled 1 / 1 MICROSOFT_SENTINEL

Finding reference table

Status Check ID Technical title Workload Severity
gap id-pim-unused PIM licensed but privileged access not operationalized identity high
gap id-security-defaults-on Security defaults enabled instead of Conditional Access identity high
gap mde-onboard-gap Defender for Endpoint licensed seats vs onboarded devices gap endpoint high
gap id-access-reviews-unused Access Reviews licensed but not configured identity medium
gap id-dormant-privileged Dormant privileged identities still enabled identity medium
gap pur-dlp-not-enforced Purview DLP licensed but not enforced in production purview medium
gap sen-ueba-not-enabled Sentinel UEBA / entity analytics not enabled sentinel medium
partial id-ca-priv-gaps Privileged sign-ins not strongly gated by Conditional Access identity high
partial sen-analytics-rule-coverage Sentinel workspace with thin analytics rule coverage sentinel high
partial mdi-sensors-missing Defender for Identity licensed but sensors missing or unhealthy defender medium
skipped mdo-p2-policies-default Defender for Office 365 P2 policies not broadly enforced defender high
ok id-idprotect-off Identity Protection policies off or report-only identity high