Study guide

20.2 Investigate Activities with Microsoft Purview Audit

SC-401: Administering Information Security in Microsoft 365 Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current SC-401 Exam Facts 1.2 Scoring, Retakes, and Annual Renewal 1.3 Role, Blueprint, and Prep Path

2 Data Classification Foundations

2.1 Identify Sensitive Information Requirements 2.2 Translate Requirements into Sensitive Info Types 2.3 Create and Manage Custom Sensitive Info Types

3 Specialized Classification Methods

3.1 Document Fingerprinting 3.2 Exact Data Match Sensitive Info Types 3.3 Trainable Classifiers

4 Classification Monitoring and OCR

4.1 Monitor Classification with Data Explorer and Content Explorer 4.2 Configure OCR Support for Sensitive Info Types

5 Sensitivity Label Design

5.1 Roles and Permissions for Sensitivity Labels 5.2 Define and Create Sensitivity Labels for Items and Containers 5.3 Protection Settings and Content Marking

6 Label Policies, Containers, and Defender for Cloud Apps

6.1 Configure Publishing Policies for Sensitivity Labels 6.2 Configure Auto-Labeling Policies 6.3 Apply Sensitivity Labels to Containers 6.4 Apply Sensitivity Labels with Microsoft Defender for Cloud Apps

7 Information Protection Client and Scanner

7.1 Plan and Implement the Microsoft Purview Information Protection Client 7.2 Manage Files with the Information Protection Client 7.3 Bulk Classification with the Information Protection Scanner

8 Microsoft Purview Message Encryption

8.1 Design and Implement Microsoft Purview Message Encryption 8.2 Design and Implement Advanced Message Encryption

9 DLP Policy Design

9.1 Design Data Loss Prevention Policies 9.2 Roles and Permissions for Data Loss Prevention 9.3 Create and Manage DLP Policies

10 Adaptive Protection, DLP Precedence, and MDCA File Policies

10.1 Configure DLP Policies for Adaptive Protection 10.2 Interpret DLP Policy and Rule Precedence 10.3 Create File Policies in Defender for Cloud Apps Using DLP

11 Endpoint DLP Configuration

11.1 Device Requirements for Endpoint DLP Including Extensions 11.2 Configure Advanced DLP Rules for Devices 11.3 Configure Endpoint DLP Settings

12 Just-in-Time Protection and Endpoint Monitoring

12.1 Configure Just-in-Time Protection 12.2 Monitor Endpoint Activities

13 Retention Labels and Adaptive Scopes

13.1 Plan Information Retention and Disposition with Retention Labels 13.2 Create and Manage Adaptive Policy Scopes 13.3 Create Retention Labels for Data Lifecycle Management

14 Publishing, Auto-Apply, and Retention Precedence

14.1 Publish Retention Labels 14.2 Auto-Apply Retention Labels 14.3 Retention Precedence and Policy Lookup

15 Retention Policies and Recovering Retained Content

15.1 Create and Configure Retention Policies 15.2 Recover Retained Content in Microsoft 365

16 Insider Risk Management Foundation

16.1 Roles and Permissions for Insider Risk Management 16.2 Plan and Implement Insider Risk Management Connectors 16.3 Integrate Insider Risk Management with Microsoft Defender for Endpoint

17 IRM Settings, Indicators, and Templates

17.1 Configure Insider Risk Management Settings 17.2 Configure Policy Indicators 17.3 Select an Appropriate Policy Template

18 IRM Policies, Forensic Evidence, and Adaptive Protection

18.1 Create and Manage Insider Risk Management Policies 18.2 Manage Forensic Evidence Settings 18.3 Enable Insider Risk Levels for Adaptive Protection

19 IRM Alerts, Cases, and Workflow

19.1 Manage Insider Risk Alerts and Cases 19.2 Insider Risk Workflow and Notice Templates

20 Purview Audit and Activity Explorer

20.1 Assign Microsoft Purview Audit (Premium) User Licenses 20.2 Investigate Activities with Microsoft Purview Audit 20.3 Configure Audit Retention Policies 20.4 Analyze Purview Activities with Activity Explorer

21 DLP, Insider Risk, and Defender XDR Alert Response

21.1 Respond to DLP Alerts in the Microsoft Purview Portal 21.2 Investigate Insider Risk Activities in the Microsoft Purview Portal 21.3 Respond to Purview Alerts in Microsoft Defender XDR

22 MDCA File Policy Alerts and eDiscovery

22.1 Respond to Defender for Cloud Apps File Policy Alerts 22.2 Perform Searches by Using eDiscovery

23 Protecting Content Used by AI Services

23.1 Implement Purview Controls for AI Services 23.2 Implement Microsoft 365 Workload Controls for AI

24 Data Security Posture Management for AI

24.1 Prerequisites for DSPM for AI 24.2 Manage Roles and Permissions for DSPM for AI 24.3 Configure DSPM for AI Policies 24.4 Monitor Activities in DSPM for AI

20.2 Investigate Activities with Microsoft Purview Audit

Key Takeaways Explain This Topic AI

Search the unified audit log in the Purview portal Audit solution; you need the Audit Logs or View-Only Audit Logs role via Audit Manager or Audit Reader

The Search form accepts a maximum 180-day UTC date range even when Premium retention is longer; run sequential searches for older Premium data

Search jobs keep running after you close the browser, remain listed for 30 days, cap at 10 concurrent jobs per admin (one unfiltered), and can take up to 48 hours in large tenants

Export supports up to 50,000 rows for Audit (Standard) and up to 1,000,000 rows for Audit (Premium); script with Search-UnifiedAuditLog in Exchange Online PowerShell

  • Microsoft does not guarantee audit-record latency; core services typically appear in 60 to 90 minutes
  • Last updated: August 2026

Investigate Activities with Microsoft Purview Audit

Quick Answer: Search the unified audit log in the Microsoft Purview portal under Audit . You need the Audit Logs or View-Only Audit Logs role (Audit Manager or Audit Reader). Scope by UTC date (maximum 180 days per search), activities, record types, users, workloads, and locations. Jobs keep running after you close the browser, remain listed for 30 days, and can take up to 48 hours in large tenants. Script with Search-UnifiedAuditLog in Exchange Online PowerShell.

Purview Audit is the investigation surface for who did what, when, and from where across Microsoft 365. It records thousands of user and admin operations. It does not place a legal hold on mailbox or site content, and it is not Activity explorer's 30-day classification timeline. Use Audit when the question is an activity record: a sharing event, a mailbox access, a directory change, an eDiscovery cmdlet, or a Copilot interaction.

Permissions before you search

Assign least privilege in the Microsoft Purview portal:

Audit Reader can search and export the audit log. It grants View-Only Audit Logs . It cannot enable or disable tenant auditing.

Audit Manager can search, export, and manage tenant audit settings (including turning auditing on or off). It grants View-Only Audit Logs and Audit Logs .

You can add those roles to a custom Purview role group. Microsoft still requires the same Audit Logs / View-Only Audit Logs roles in the Exchange admin center to run audit cmdlets and to enable or disable auditing. Microsoft Graph Audit Search APIs need additional Graph permissions; do not assume Purview role-group membership is enough for Graph.

Do not grant Global Administrator just to run an audit search. Microsoft recommends the fewest privileges that still complete the investigation.

Administrative units restrict portal search. A restricted admin can search and export only user-generated logs in assigned units. An unrestricted admin can search all logs, including non-user and system accounts. Microsoft publishes a list of operations that restricted admins still cannot retrieve in the portal (including several Endpoint DLP file events and some Exchange cmdlets). Use an unrestricted admin or Search-UnifiedAuditLog when you must see those activities.

Confirm that ingestion is on

Audit log search is turned on by default for Microsoft 365 and Office 365 enterprise organizations. Verify the setting in Exchange Online PowerShell :

Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled

True means ingestion is on. The same cmdlet exists in Security & Compliance PowerShell, but the UnifiedAuditLogIngestionEnabled property is always False there even when auditing is on. That mismatch is documented; it is a favorite false-negative.

Turn ingestion off or on with Set-AdminAuditLogConfig -UnifiedAuditLogIngestionEnabled $false or $true in Exchange Online PowerShell. If you turn auditing off, Purview search, Search-UnifiedAuditLog , the Office 365 Management Activity API, and Microsoft Sentinel lose audit data for the organization. Small-business and unmanaged trial tenants must turn auditing on manually before any search returns results.

Run a search in the Purview portal

Sign in to the Microsoft Purview portal .

Open the Audit solution card (or View all solutions > Audit from Core).

On the Search page, set criteria, then select Search .

Classic Search retired on 30 November 2023. New Search is the current UI: faster jobs, additional filters, saved searches, and a job dashboard.

Criteria that matter on the exam

Date and time range (UTC). The last seven days are selected by default. The maximum range you can specify is 180 days . A longer range returns an error. If you use the full 180 days, set the start time to the current time so start is not after end. If auditing was enabled inside the last 180 days, the range cannot start before the enable date.

Keyword Search. Matches indexed content in the audit common schema , not the full AuditData payload. Replace special characters with * . For example, search test*search*document rather than test_search_document .

Activities - friendly names. Grouped names such as sharing and access request activities. You can select a group or individual activities.

Activities - operations names. Exact operation names, comma-separated, with no typos ( SPOIBIsEnabled,SPOIBIsDisabled ). Incorrect names return zero results.

Record types. Map to services. Information Protection examples include MIPLabel , MipAutoLabelExchangeItem , MipAutoLabelSharePointItem , and MipAutoLabelSharePointPolicyLocation .

Users. Leave blank for all users and service accounts. For mailbox work, searching a mailbox owner does not return delegate activity ( SendAs , SendOnBehalf ) performed in that mailbox.

File, folder, or site. Partial names or URLs; a * wildcard is supported at the end of a URL.

Workloads and Admin Units further scope the query.

Search name. Optional; otherwise the job is named from timestamp and criteria.

Microsoft does not guarantee a latency SLA. Core services (Exchange, SharePoint, OneDrive, and Teams) typically show records 60 to 90 minutes after the event. Other services can take longer. Outages outside the audit pipeline can delay records. Treat "it is not in the log yet" as a timing issue before you treat it as a product failure.

Power BI activities appear in the unified audit log only after you enable auditing in the Power BI admin portal.

Search job dashboard, export, and PowerShell

Microsoft publishes these operational limits for New Search. Memorize them as search-tool limits, not as audit-retention limits.

  • Limit Published value
  • Concurrent search jobs per admin 10, including at most one unfiltered job
  • Completed job history 30 days
  • Maximum Search form date range 180 days
  • Large-tenant job duration up to 48 hours
  • CSV export 50,000 rows for Audit (Standard); 1,000,000 rows for Audit (Premium)
  • Typical core-service record availability 60 to 90 minutes (not an SLA)

Jobs continue after you close the browser. Each admin can run up to 10 search jobs at once, with a limit of one unfiltered job. Completed jobs remain for 30 days . Deleting a job deletes the job definition and result set, not the underlying audit data. Copy this search clones criteria into a new query.

The dashboard shows search name, job status (Queued, In Progress, Completed), progress, search time, total results (an approximate count when a query returns more than 100,000 results), creation time, and who ran the search. The details view may show fewer items than the dashboard total because it removes duplicates.

Results include Date (UTC), IP address, User, Record type, Activity, Item, Admin Units, and Details. Open a row for the flyout. Export to CSV supports up to 50,000 rows for Audit (Standard) and up to 1,000,000 rows for Audit (Premium). Split the AuditData JSON column in Excel with Power Query so you can filter on nested properties.

Search-UnifiedAuditLog in Exchange Online PowerShell is the cmdlet behind the portal. Use it for automation. For continuous SIEM ingest, use the Office 365 Management Activity API rather than a looping PowerShell download. Premium tenants get higher API bandwidth (baseline 2,000 requests per minute, then scaled; E5 about twice non-E5).

Compromised-mailbox investigation with MailItemsAccessed

After you evict an attacker, identify compromised mailboxes and the access window, then search the MailItemsAccessed operation.

Sync (Outlook for Windows or Mac downloading a folder): treat the whole folder as exposed. Filter AuditData for MailAccessType = Sync . Compare ClientIPAddress , ClientInfoString , and SessionId to attacker context.

Bind (individual message access): records aggregate bind operations in a 2-minute window; InternetMessageId identifies messages; OperationCount shows how many binds were rolled up.

Duplicate bind records for the same message within an hour are filtered unless key properties change (IP, client, folder, logon type, access type, mailbox, user, or session). Sync operations are also filtered on a one-hour interval. MailItemsAccessed covers POP, IMAP, MAPI, EWS, Exchange ActiveSync, and REST. It is Audit (Standard) for E3/E5 mailboxes; Premium adds intelligent properties such as SensitivityLabel on those events.

Example unified-audit search shape:

Search-UnifiedAuditLog -StartDate 01/06/2026 -EndDate 01/20/2026 -UserIds user@contoso.com -Operations MailItemsAccessed -ResultSize 1000

Exam traps

A 180-day search window is not the same as Premium retention . Premium-licensed Entra, Exchange, and SharePoint records can still exist for a year, but the portal search form rejects a date range longer than 180 days — run sequential 180-day searches.

Keyword search does not scan every JSON property in AuditData.

Operation names must match Microsoft's published names exactly.

Closing the browser does not cancel a search job.

Get-AdminAuditLogConfig in Security & Compliance PowerShell is the wrong place to verify ingestion.

  • Official resources
  • Search the audit log — search criteria, job limits, export caps, admin units (updated 2026-06-19)
  • Search the audit log to investigate common support issues — permissions and investigation patterns
  • Use MailItemsAccessed to investigate compromised accounts — sync versus bind forensics (updated 2026-06-24)

Loading diagram... Purview Audit search workflow