Connect to your first tenant
Enter your Azure App Registration details. Tenant ID and Client ID are not secrets — they identify your app registration. All authentication happens directly with Microsoft.
Cancel
⚠️ Redirect URI: Add detecting… as a Single-page application (SPA) redirect URI in your App Registration. Serve via npx serve . and open the localhost URL shown.
Required Delegated API Permissions SecurityEvents.Read.AllSecurityAlert.Read.AllPolicy.Read.All Directory.Read.AllAuditLog.Read.All IdentityRiskyUser.Read.AllIdentityRiskEvent.Read.All DeviceManagementManagedDevices.Read.AllApplication.Read.All User.Read.AllUserAuthenticationMethod.Read.All RoleManagement.Read.DirectoryReports.Read.All
Overview
ℹ️

Your tenant's security at a glance. Each card below summarizes one area — identity, threats, licensing, governance — using a simple green / amber / red signal. Skim the page in 30 seconds: green means healthy, amber means worth a look, red means someone should be working on it this week.

ℹ️

Microsoft scores your tenant against a checklist of security best practices — think of it like a credit score for your Microsoft 365 setup. Higher means fewer easy openings for attackers. The list below shows what's still open, grouped by area (Identity, Apps, Data…), with the biggest opportunities first. A score climbing over time means the team is closing real risks.

Loading security score…
ℹ️

Who can sign in to your company, how they prove it's really them, and who holds admin powers. People without multi-factor authentication are the single biggest risk in any tenant — one stolen password and the attacker is in. The admin lists below also matter: the more administrators you have, the larger the damage if one account is compromised.

Loading identity data…
ℹ️

The rules that decide who can sign in, from where, and under what conditions — for example "require MFA when signing in from a new device" or "block sign-ins from countries we don't do business in." This section highlights gaps: common attack patterns that aren't yet blocked. Each gap is a door we know how to close.

Loading CA policies…
ℹ️

What Microsoft Defender has actually seen attempting to attack your tenant — suspicious sign-ins, leaked passwords found on the dark web, malware on company devices. A clean list is the goal. Anything red or recent should be reviewed by whoever owns security incident response.

Loading threat intelligence…
ℹ️

How your email is protected against phishing, spoofing, and malicious attachments — and what's been caught recently. Email is the #1 way attackers get into companies, so this section answers two questions: are the standard protections turned on, and are they working?

Loading email security…
ℹ️

Who you're paying Microsoft for, what they're actually using, and where you might be over- or under-licensed. Each user is a recurring cost; this section helps you spot licences that aren't being used (recoverable spend) and users whose role would justify a security upgrade (e.g. moving a high-risk admin from E3 to Entra ID P2).

Loading licensing data…
ℹ️

Every app — both your internal tools and third-party services like DocuSign, Slack, or Salesforce — that has permission to read or write data in your tenant. A forgotten app with broad permissions is a quiet backdoor: nobody uses it, nobody is watching it, but an attacker who compromises that app gets access too. This section helps you spot what to retire.

Loading applications…
ℹ️

The big-picture hygiene settings: who is allowed to create groups, invite external guests, register new apps, or run automation. Loose defaults here mean any employee can quietly expand the company's attack surface without anyone noticing. Tight defaults keep change deliberate and auditable.

Loading governance checks…
ℹ️

Who's actually using Microsoft 365 day-to-day — last sign-in, mailbox activity, file usage. Two uses: licensing decisions (a paid account nobody logs into is waste), and risk (a long-dormant account, especially an admin one, is a door left unlocked).

Loading usage data…