Office 365 email monitoring
What left your company by email last month? Something did.
In a typical tenant, a month of outbound mail carries dozens of messages to external addresses with card numbers, IDs or contracts attached - and hundreds of delegate and send-as uses nobody reviews. 1Security reads mail flow across every mailbox and turns it into filters: direction, sending method, attachments, sensitive content, whole threads. It stores signals, not a copy of anyone's inbox.
- 5sending methods recorded on every message: direct, send as, send on behalf, shared mailbox, delegate
- 300+detectors run on attachments and bodies, so "sensitive content leaving" is a filter
- 0message bodies stored - metadata and detections only, no browsable mail archive
The problem
Mail security judges what arrives. Nothing judges what leaves.
Mail security is built for inbound verdicts. The two events that cost money are outbound.
A mail gateway asks three questions of every incoming message: is it spam, is it phishing, does it carry malware - and answers them well. The outbound questions are different: what left the tenant this month, how it was sent, whether an external sender who got past the filter is now getting internal replies, and what was actually inside the attachment. Those need a second view, kept longer than a trace.
The two expensive scenarios both hide in the shape of the exchange. A single outbound message with an attachment is unremarkable. The same message to an external address, carrying a spreadsheet with 2,000 customer records that exists nowhere in SharePoint or OneDrive, sent through delegate access on a director's mailbox, is a different object. 1Security puts those four facts on one row.
And the mailbox itself is a blind spot: a typical mid-size tenant has hundreds of shared mailboxes and thousands of delegate grants, reviewed by nobody, plus forwarding rules that stay in place long after the person who created them left.
What you get
Mail flow as filters, not as an export
Every signal below is a column on the Emails screen and a filter you combine - not a report you request and wait for.
Direction
Inbound, outbound or internal on every message. Exfiltration analysis starts with "outbound + external recipients"; phishing analysis with "inbound + two-way exchange".
Sending method
Direct, send as, send on behalf, shared mailbox or delegate access - the four delegated paths are the favourite disguises of business email compromise, and here they are filters.
Attachments, three ways
Classic attachments, cloud attachments that are really SharePoint or OneDrive links, and unique uploads - files sent by mail that exist nowhere in your tenant, the strongest single exfiltration signal.
Sensitive content on the row
The 1Security scan runs 300+ detectors and OCR on bodies and attachments, so "outbound + sensitive info" is a filter. Purview labels and protection status sit beside it.
Whole threads as rows
The Conversations tab rolls every thread into one line: participants, files across the exchange, accumulated detections, and whether an external sender is receiving internal replies.
Thread evidence that survives deletion
Every message is classified as root, reply or forward and linked across mailboxes. A reply whose parent is missing from every scanned mailbox is proof the original was removed.
How deep it goes
The exfiltration shortlist, in four filters
Outbound + external recipients + sensitive info + unique uploads. That list is usually short and always worth reading.
It means sensitive content leaving the organization inside files that never existed in SharePoint or OneDrive - a spreadsheet exported from a system of record, a photographed contract, a database dump. In a typical tenant the shortlist for a month is a few dozen messages. A five-minute review resolves each one - once the list exists.
The conversation-level equivalent is the successful-phish check: Conversations tab, two-way exchange, inbound, phishing flag. Not the attempts the gateway bounced - the external senders who got answers. A message-level view cannot ask this, because the signal only exists once a thread has both directions in it.
The third is the cover-up trace: missing parent plus a phishing or malware flag. Threads where the incriminating original is already gone, but a reply still references it - which is itself a record that something was removed, and where.
In practice
Four sweeps worth saving as views
Each is a filter set on the Emails screen. Save it once and the second run costs nothing.
- 01
BEC sweep
Sending method "send as" or "delegate access", outbound, external recipients. Every delegated identity use to an outside address, ready to confirm or challenge. Typical result: a handful a week, most expected, occasionally not.
- 02
Quiet forwarding
Type "forward", external recipients, sensitive info. Internal material being passed outside one forward at a time - the leaver preparing their exit is the classic find.
- 03
Living sensitive threads
Conversations tab, with sensitive info, sorted by last activity. The exchanges still accumulating regulated content today, not the ones that died last quarter.
- 04
Act on the selection
Select messages or a mailbox and stage an automation - quarantine, flag, revoke a forwarding rule - behind the 72-hour review window. Mailbox actions quarantine or flag; nothing is permanently deleted.


The difference
What the outbound view adds
This sits beside your mail gateway rather than replacing it. The questions are different.
- Outbound sensitive content as a filter, live - not reconstructed after the fact
- How a message was actually sent - send as, on behalf, delegate - not just who it claims to be from
- Files sent by mail that exist nowhere in your SharePoint or OneDrive
- Whole threads as single rows, with participants and files summed across the exchange
- External senders who received internal replies
- Replies whose parent is missing from every scanned mailbox
- The riskiest sending method used anywhere in a thread, marked on the thread
- History kept up to three years - from a 90-day trace to three years of mail signals
Approach
Signals, not surveillance
The platform stores communication metadata and security detections - directions, participants, flags, sending method, sensitive-information matches. Bodies and attachments are analysed in a transient process and discarded. There is no browsable archive of message bodies, and it is not designed to become one.
- 0message bodies stored - metadata and detections only
- 3attachment kinds told apart: classic, cloud link, unique upload
- 3 yearsof mail signals kept on standard licenses - from 90 days to three years
Related
Where this fits
Mail is one exit route. Sharing links are another, and sensitive data discovery is what makes both worth watching. Investigations tend to cross all three.
Sensitive data discovery
The 300+ detectors behind "sensitive info" on a message, and where else in the tenant that data lives.
See sensitive data →File permissions
The other exit route: the thousands of anyone links and grants on the files themselves.
See files →Unified audit log
Up to three years of activity an email investigation usually continues into.
See audit logs →
The 1Security platform
Email Monitoring is just the beginning
Email Monitoring 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.
- AlertingInstant and digest channels per client, routed to the right people, themed under your brand or theirs.


- Trends and the daily briefWhat moved this month, what needs a decision today, ranked, for the client meeting and for your own morning.


- LocationsWhere every sign-in and every action really comes from, on a map, per tenant. Breaches by location, impossible travel, allow lists per person. Works without premium sign-in logs.


- DevicesRegistered, unregistered and shadow devices, attributed from activity rather than from an agent. The device nobody enrolled still shows up.


- Apps and consentEvery app with access to the tenant, what it can reach, who consented, and whether it still needs to.


- AI agents and CopilotThe agent registry: owners, reach, who each agent acts as, what Copilot will see. The EU AI Act checks per agent, accountable owner, instruction transparency and impact assessment, measured from the tenant. Readiness before the licences, governance after.


- 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.
- 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
FAQ
Questions teams ask first
Does this read employees' email?
It analyses messages to record signals - direction, sending method, participants, attachments, sensitive-information detections - and discards the content. There is no browsable archive of anyone's mail, deliberately: this is a security signal layer, not an inbox viewer.
How does it know a message was deleted?
By the gap it leaves. A reply carries header references to its parent. If that parent is absent from every scanned mailbox, the reply is evidence the original was removed or never passed through your tenant. The trace survives the deletion.
What is a unique upload?
A file that arrived or left by email and exists nowhere in your SharePoint or OneDrive. On outbound mail it is the strongest single exfiltration signal, because normal collaboration leaves a copy behind.
Does it need a premium license or Defender for Office 365?
No. Email monitoring runs on standard Microsoft 365 licenses through a separately consented email module on the read-only app. Defender keeps judging messages at the perimeter; this answers what left, how it was sent and what an exchange became.
Can it act, or only show?
Both. Selected messages and mailboxes can be handed to automations behind the review window - quarantine, flag, forwarding-rule removal. Mailbox actions never permanently delete, and every action is logged with who approved it.
See what left through email last month.
Connect read-only, enable the email module, and the exfiltration shortlist is four filters away the same day. Most teams find at least one thread they wish they had seen earlier.
Or keep answering outbound questions from a 90-day trace.