Microsoft 365 security log
The question arrives in month seven. Is the log still there?
The question usually arrives in month seven: a departing employee's activity from last quarter, a compromise found months after the first sign-in, an auditor sampling last year. 1Security ingests the audit stream continuously and keeps it as one searchable log for up to three years - files, mail, Teams, sign-ins, AI agents and third-party apps in a single timeline, every event already tied to the user, the file, the app, the device and the country it came from. On standard licenses, with no SIEM bill and no log forwarder.
The problem
A leaver, a late-found compromise, an auditor. None of them ask about last week.
A departing employee's activity from last quarter. A compromise found four months after the first sign-in. An auditor sampling a date range from last year. Security questions do not respect retention windows. With 1Security you go from 180 days of audit history on standard licenses to three years - retention that starts the day you connect, not the day after the incident.
Even inside the window, 'what did this account do that afternoon' spans sign-in, file, mailbox and device records that each speak their own language, and correlating them by hand is an afternoon of your own. One timeline, with every event already tied to its user, file, device and location, turns that question into a filter.
And the raw events do not name things. A typical tenant produces hundreds of thousands of audit records a week, keyed by GUIDs and site URLs, and requests often arrive through a datacenter egress rather than the user's real network. Shipping all of that to a SIEM makes it searchable and makes it expensive - most teams end up keeping 30 days and hoping.
In practice
From a vague question to an exact list of events.
How a typical search runs in Activity logs - one screen, one query, any date range up to three years.
- 01
Filter by anything that matters
Open Activity logs and narrow by user, file, site, app, AI agent, device, country, network type or action group - the same filters work across file, mail, Teams, sign-in and agent events. "Everything this contractor downloaded from the finance site in March" is three chips, and the answer is a list, typically a few dozen rows out of millions.
- 02
Read events as sentences, not GUIDs
Every row is a plain-language description with the actor, the resource, the app, the device (managed or unmanaged), the location and a severity. Datacenter egress is labelled for what it is instead of raising a false "foreign datacenter" alarm; VPN, Tor and hosting egress are flagged. The raw Microsoft record stays one click away for the skeptics.
- 03
Go back three years, not six months
Up to three years of history means last year's date range is a filter, not a lost cause. 7, 30 and 90-day questions are served from precomputed rollups and answer instantly even on tenants with tens of millions of files; long windows over hundreds of millions of events still return in seconds.
- 04
Save it, schedule it, or feed the SOC
Save the filter as a view, schedule it as a digest, export it, or let Sentinel, Splunk, QRadar or Elastic pull the same normalised log through the read-only REST API - polling on the discovered-at timestamp so late-arriving events are never lost. You keep the SIEM for correlation and stop paying it for storage.


What makes it work
A log is only as good as what each line carries.
Three parts of the platform turn raw audit events into a security log you can actually search.
Three years of audit history
From 180 days to three years of retention, searchable in place, with an explicit unclassified bucket instead of silently dropped events.
Explore the audit tool →Near real-time ingestion
New activity is visible in about ten minutes at any tenant size, so the log is a live surface you can watch during an incident, not a nightly batch.
Explore monitoring →Answers and exports
Saved views, scheduled digests and full exports on the same data - plus the REST API when the log belongs in your SIEM.
Explore reporting →
FAQ
Common questions.
Does this replace the Microsoft unified audit log?
It builds on it. 1Security reads the same audit stream, normalises it, attaches the user, device and location to every event, and keeps it for up to three years. The raw Microsoft record stays attached to each event, so nothing is lost in translation - and you can still run Search-UnifiedAuditLog whenever you want a second opinion.
Do we need a premium license or add-on for this?
No. Three-year retention, enrichment and search run on standard Microsoft 365 licenses - Business Basic upward - with a read-only connection and nothing to install. The audit history available at the moment you connect is backfilled; history accumulates from there.
How does the log get into our SIEM?
Pull-based, through the read-only REST API: per-tenant keys, 600 requests a minute, cursor pagination, and documented wiring for Sentinel, Splunk, QRadar and Elastic. Polling on the discovered-at timestamp keeps the drain deterministic even when events surface hours late.
How fast does new activity show up?
About ten minutes from the action to a searchable row, at any tenant size. During a live incident you can filter to the account and watch the log fill in.
The 1Security platform
Microsoft 365 Security Log is just the beginning
Microsoft 365 Security Log 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.
- 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.


- Email and mailboxesWho can read whose mailbox, forwarding rules, threads with sensitive content, inbound and outbound exposure.


- LicencesWhat is assigned, what is unused, and which bundle an action or feature still needs, so the upgrade you sell is the one the client needs.


- Security scoreThe score, its history, the controls behind it and the benchmarks, so the number on the board report means something.


- 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
Keep the answer past day 180.
Connect read-only and the log starts accumulating today - searchable, attributed, and yours for three years. Backfill covers the audit history available when you connect.
Or hope the next question is about something recent.