Microsoft Defender false positives
This alert is probably nothing. How long will it take to prove it?
Defender is doing its job: it flags what looks wrong. In a typical tenant the large majority of alerts close as benign - after someone has spent an hour collecting the context to prove it. 1Security links every Defender alert to the account behind it, what that account can reach, whether today is normal for it, and what it actually touched. Close the false positive with proof in minutes. Escalate the real one with evidence attached.
The problem
Every Defender alert costs an investigation. Most deserve a glance.
A high-severity Defender alert names an account. Now the real work starts: what is this account, what can it reach, is this activity unusual for it, and did anything sensitive actually move? Collecting the answers by hand means permissions in one place, sign-ins in another, mailbox access in a third and activity history in a fourth. An hour later you have a shrug and a closed ticket.
Because that hour is expensive, teams triage by instinct. Familiar account, working hours, probably fine - dismissed. In a tenant that gets dozens of Defender alerts a week, the one that mattered gets the same instinct treatment, because nothing on the alert itself separates it from the noise.
Tuning Defender rules does not fix this. Fewer alerts still cost an hour each. What fixes it is making one alert cheap to judge: the account, its reach, its baseline and its history one click from the alert, so a false positive closes in two minutes with evidence, and a real one is escalated in five.
In practice
Triage in four questions, each one click.
The same Defender alert, worked in 1Security with everything on one screen.
- 01
Open the alert and see who this is
Defender and Sentinel alerts land in 1Security's Microsoft alerts list already linked to the user, group, mailbox or app they concern. One click opens the account: its groups, licenses, MFA registration, sign-in state, admin roles, and a 30-day trend of what it does on a normal day.
- 02
Check whether today is normal for it
Anomaly baselines compare today with the median of the account's own trailing 30 days. A finance clerk downloading 40 files reads as routine when their baseline is 38 - and as an incident when it is 3. If an anomaly episode is open for this account, it is right there next to the alert.
- 03
See what it could reach
The permission graph resolves the account's effective access: every site, file and mailbox, through direct grants, sharing links, nested groups and inheritance. It is common for an ordinary account to reach hundreds of thousands of files. A blast-radius question that used to take half a day takes ten minutes.
- 04
See what it actually touched, then decide
Up to three years of Activity logs filtered to the account, with device and location on every event - the downloads, the shares, the mailbox reads, the sign-in from a hosting network. Real threat: escalate with the rows attached, or stage a fix (revoke links, remove access, disable) behind a review window. False positive: close with proof instead of a shrug.


What makes it work
Context is a platform feature, not an analyst habit.
Three parts of the platform do the heavy lifting behind this workflow. Each is documented in depth.
Alerts with entities attached
Defender and Sentinel alerts land linked to the users, groups, emails and apps they concern - the pivot to investigation is one click, not a search.
Explore the alerts tool →Effective access, resolved
The permission graph answers what the flagged account could actually reach - nested groups, sharing links, mailbox delegates and inheritance included.
Explore access management →Three years of memory
What the account did before and after the alert, with device and origin on every event - three years of history instead of 180 days, on standard licenses.
Explore the audit tool →
FAQ
Common questions.
Does 1Security replace Microsoft Defender?
No. Defender keeps detecting; 1Security makes its alerts cheap to judge. Your Defender and Sentinel alerts appear inside 1Security linked to the entities they concern, and the triage context - reach, baseline, history - lives around them.
Do I have to tune Defender rules to see fewer false positives?
No rule changes are needed. The alerts stay as they are; what changes is the cost of judging one. When a verdict takes two minutes with evidence, false positives stop consuming shifts even if their count never moves. Once you see which accounts and behaviours generate the benign ones, tuning becomes an informed choice rather than a guess.
What licenses does this require?
Security alert ingestion uses your existing Defender setup. Everything 1Security adds - the permission graph, baselines, three years of history - runs on standard Microsoft 365 licenses from Business Basic upward, with read-only consent. No E5, no Entra P2, no agent to install.
How fast is the context available after we connect?
Alerts, accounts and effective access appear as soon as the first scan completes - the same day for most tenants. Activity history builds from the day you connect and is kept for up to three years; behavioural baselines stay quiet for the first 14 days on purpose, then compare every alert against a real normal.
The 1Security platform
Defender Alert Triage is just the beginning
Defender Alert Triage is one screen of the 1Security platform for Microsoft 365. Locations, devices, apps, AI agents, logs, permissions, sensitive data, compliance, reports and actions run on the same read-only connection, on the licence you already have.
- Permissions and sharingWho can reach what, through which group, link or guest, and whether anyone meant it. The sharing map every audit asks for.


- Sensitive dataPersonal data, credentials, financial and health records found by our own classifiers, with a Microsoft second opinion where the client has it.


- Sensitivity labelsLabel coverage and gaps across sites and files, so the protection the client paid for is actually applied.


- Files, sites and the column browserBrowse the tenant like a file system: site, library, folder, file, with the permissions and sensitivity of each level beside it. A problem solved in itself.


- Users, groups and lifecycleDormant accounts, guests who never left, groups nested three deep, orphaned owners, admins without MFA. The review that is a spreadsheet everywhere else.


- External domainsEvery outside organization with a foothold in the tenant, its trust posture, its drift, and who it was invited by.


- Microsoft 365 Alerts ToolOne alert model across policies, activity and anomalies - with the evidence attached and the alert threshold in your hands.
- Microsoft 365 Monitoring ToolReal-time monitoring that catches a mass download while it is unfolding - across users, files, apps, AI agents and devices.
- Copilot Security ToolEvery AI agent's real blast radius - quantified before rollout, watched and constrained after.
- Shadow Device DetectionEvery device touching your data, reconstructed from real activity - including the machines that never enrolled anywhere.
- Impossible Travel DetectionLocations as identities, not IPs: country, city and network for every action, first-seen origins, travel timelines with verdicts - no E5, no P2.
- Conditional Access MonitoringDeclared Conditional Access compared against observed sign-ins: coverage verdicts, ungoverned traffic share, and the ranges your offices outgrew.
- Office 365 Access ManagementEffective access, resolved - who can reach what, through which grant, and one place to take it away.
- SharePoint Governance ToolEvery site ranked by exposure and abandonment - links, guests and Copilot access under control.
- Office 365 User ProvisioningLifecycle access from day one to offboarding - reach, dormant accounts and license reclaim in one flow.
- Microsoft 365 Audit ToolUp to three years of searchable activity history - every action tied to an actor, device and location.
- Microsoft 365 Inventory ToolEight live inventories on one permission graph - including the sites, devices and AI agents that were never registered anywhere.
- Office 365 ReportingAnswers, not exports - regulator-grade numbers, saved views and a read-only API for your SOC.
- Microsoft 365 File PermissionsWho has access to any file, and why - people, links, apps and AI agents on one map, with the fix in the same place.
- Sensitive Data DiscoveryWhere regulated data lives and everything that can reach it - two detection engines, no premium licence required.
- Office 365 Email MonitoringOutbound sensitive content, delegated-send abuse and whole-thread evidence that survives deletion.
- Purview Label CoverageWhat your sensitivity labels actually cover, and which of them protect anything at all.
- AI Agent InventoryEvery agent in the tenant with its real reach counted, its blueprint reviewed, and guardrails you can verify.
- AI Data RestrictionDeclare a data type off-limits to AI and every agent, app and user still reaching it becomes a live violation - recorded for the auditor.
- AI Spend TrackingInteractions, Copilot credits and Azure tokens in one ledger per agent - with the spend column next to what each agent can reach.
- Microsoft 365 User Access ReviewEvery identity with what it can reach, what it did, and whether it should still exist - including SharePoint-only guests that live outside the directory.
- Group Access AnalysisWhat membership in a group actually unlocks - nesting resolved, external members surfaced, blast radius counted.
- App and OAuth Consent GovernanceEvery app with a foothold in the tenant: how it got in, who let it in, and what it can actually read.
- Remediation AutomationFindings become fixes at tenant scale, counted before you enable them and staged behind a review window.
- Microsoft 365 Licence OptimizationThe seats you pay for and nobody uses - unassigned units, licences on guests, and dormant accounts still billing.
- Microsoft 365 Anomaly DetectionEvery policy, user, app and agent measured against its own baseline - with an alert line you move and see the answer to at once.
- Office 365 Sign-in LocationsEvery place your tenant is reached from, with your Conditional Access configuration laid over observed reality.
- Microsoft 365 Unified Audit LogWho did what, when, from where and on which device - retained up to three years on a standard licence.
- SharePoint Site InventoryEvery site, channel site and OneDrive in one list, ranked by external reach, abandonment and what Copilot can read.
- Microsoft 365 Activity AnalyticsThe extremes rather than the averages - a mass download inside the hour, and everything nobody has touched in a year.
- Microsoft 365 Trend TrackingAny number in the tenant followed over time, with the change and the deviation attached - and alerting on the same object.
- Microsoft 365 Compliance MonitoringReadiness for eleven regulations measured from live tenant data - with weekly snapshots and a dated evidence pack per framework.
- Microsoft 365 Security ScoreMicrosoft Secure Score beside the score measured from what actually happens - one worklist ranked by points still on the table.
- External Domain MonitoringEvery organisation your tenant exchanges data with, resolved to a real company - with drift flags and an enforceable verdict per domain.
- All featuresExplore everything
Give every Defender alert its context.
Connect read-only, and the next Defender alert arrives with the account's reach, baseline and history one click away - so it closes or escalates in minutes.
Or keep triaging severity strings by instinct.