Study guide

20.3 Configure Audit Retention Policies

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.3 Configure Audit Retention Policies

Key Takeaways Explain This Topic AI

Audit log retention policies are an Audit (Premium) feature; Standard-only tenants keep records for 180 days and cannot create these policies

The default Premium policy cannot be modified and keeps Entra ID, Exchange, OneDrive, and SharePoint records for one year for Premium-licensed users

Custom policies always outrank the default policy; a 6-month Exchange policy shortens Exchange retention below one year for scoped users

You can create up to 50 custom policies with priority 1 (highest) through 10000; creating or editing them requires the Organization Configuration role

Ten-year duration needs the 10-Year Audit Log Retention add-on, is not retroactive, and does not apply to non-user service-principal records

Last updated: August 2026

Configure Audit Retention Policies

Quick Answer: Audit log retention policies are an Audit (Premium) feature. A default, unmodifiable policy keeps Microsoft Entra ID, Exchange, OneDrive, and SharePoint records for one year for Premium-licensed users. Everything else defaults to 180 days unless you create a custom policy. You can create up to 50 custom policies, ranked by priority 1 (highest) through 10000 . Ten-year retention needs the 10-Year Audit Log Retention add-on and is not retroactive.

These policies retain audit records , not user content. They are not retention labels, not eDiscovery holds, and not Activity explorer's 30-day window. If the exam stem is about keeping messages or files , you are in Data Lifecycle Management or eDiscovery. If the stem is about keeping who accessed what , you are here.

Why custom policies exist

Audit (Standard) keeps records for 180 days. Many investigations, regulators, and insider-risk reviews need a longer trail for mailbox access, sharing, and directory changes. Premium's default policy covers the four high-volume workloads for one year. Custom policies cover other record types (Teams, DLP, Power BI, and the rest of the catalog), target high-risk users, or shorten retention when a workload must not keep logs for a full year.

Lifetime is stamped when the record enters the auditing pipeline . Changing a license or policy updates expiration for records ingested after the change. It does not rewrite already committed items. A 10-year policy created today does not resurrect logs that already aged out, and Microsoft states that 10-year retention is not retroactive .

Default Premium policy

Microsoft's retention-policy article (updated 2026-06-19) describes a default policy that:

Applies to records whose Workload value is AzureActiveDirectory , Exchange , OneDrive , or SharePoint .

Retains those records for one year .

Cannot be modified .

Applies only to activity performed by users with an Office 365 or Microsoft 365 E5 license, Microsoft Purview Suite (formerly Microsoft 365 E5 Compliance), or an E5 eDiscovery and Audit add-on license.

Leaves non-E5 users and guest users on 180 days even for those workloads.

The Purview dashboard does not list this default policy. Get-UnifiedAuditLogRetentionPolicy does not return it either. If you open Audit retention policies and the list is empty, the default policy can still be in effect.

All other activities default to 180 days unless a custom policy matches them.

License gates for duration

To keep a user's audit log longer than 180 days (and up to 1 year), that user must have an eligible Premium license. To keep logs for 10 years, assign the 10-Year Audit Log Retention add-on and create a matching policy.

Published duration options when you create a policy:

  • Duration shown in the portal Extra requirement Microsoft publishes
  • 7 days, 30 days Microsoft 365 Enterprise E5
  • 6 months, 9 months, 1 year Audit (Premium) user license
  • 3 years, 5 years, 7 years 10-Year Audit Log Retention add-on plus E5
  • 10 years 10-Year add-on plus E5; choose the 10 Years option

If the acting user lacks the license for the duration you picked, Microsoft retains the record using the highest-priority policy that still matches that user and record type — often the license default (180 days or 1 year). Do not assume the UI duration you selected is what an unlicensed mailbox actually receives.

Audit records generated by non-user entities (service principals, system events, application activities) stay at a fixed one year . Custom policies do not apply to those records. Microsoft does not publish a way to keep service-principal audit records for 10 years inside Purview Audit.

Create a custom policy in the portal

You need the Organization Configuration role on Roles & scopes.

Sign in to the Purview portal and open the Audit solution.

Select Create audit retention policy .

Policy name: unique in the organization; you cannot rename it later.

Description: optional, but useful for record type, users, and duration.

Users: one or more users, or leave blank to apply to all users.

Record type: one type, multiple types, or blank for all types. Selecting one record type unlocks Activities so you can target specific operations. Selecting multiple record types applies to all activities of those types — you cannot pick individual operations.

Duration: one of the published options in the table above.

Priority: a number from 1 to 10000 . Lower value = higher priority. Priority 5 beats priority 10 . Every custom policy beats the default policy , even at priority 10000.

Save. The policy appears on the Audit retention policies dashboard.

That last rule is the exam trap. A custom Exchange policy of 6 months shortens Exchange mailbox audit retention below the default one year for the scoped users. Custom policies are overrides, not only extensions.

Your organization can have up to 50 audit log retention policies.

The dashboard lists custom policies. Sort by Priority to see evaluation order. You can edit most UI-created policies from the flyout. Policies created with New-UnifiedAuditLogRetentionPolicy for record types or activities the UI does not expose can only be viewed or deleted in the portal; edit them with Set-UnifiedAuditLogRetentionPolicy in Security & Compliance PowerShell. A banner on the flyout tells you when PowerShell is required. Deletion can take up to 30 minutes to take effect.

PowerShell

Connect to Security & Compliance PowerShell, then create policies the UI cannot express.

This example keeps all Microsoft Teams activities for 10 years at priority 100:

New-UnifiedAuditLogRetentionPolicy -Name "Microsoft Teams Audit Policy" -Description "One year retention policy for all Microsoft Teams activities" -RecordTypes MicrosoftTeams -RetentionDuration TenYears -Priority 100

This example keeps UserLoggedIn for one admin for six months at a higher priority (25):

New-UnifiedAuditLogRetentionPolicy -Name "SixMonth retention for admin logons" -RecordTypes AzureActiveDirectoryStsLogon -Operations UserLoggedIn -UserIds admin@contoso.onmicrosoft.com -RetentionDuration SixMonths -Priority 25

View policies with Get-UnifiedAuditLogRetentionPolicy (sort by Priority). The cmdlet does not return the default policy. Edit with Set-UnifiedAuditLogRetentionPolicy . Remove with Remove-UnifiedAuditLogRetentionPolicy (allow up to 30 minutes).

A practical design pattern

Confirm Premium licenses on the users whose records you must keep beyond 180 days.

Leave the default 1-year policy in place for Entra, Exchange, OneDrive, and SharePoint unless you have a documented reason to shorten it.

Add high-priority (low number) custom policies for high-risk users or high-value record types such as Teams or DLP.

If a regulation requires 10 years, buy the add-on, assign it, then create the 10-year policy before you need the evidence.

Export to a SIEM if you need retention beyond what Purview will store, or for non-user records custom policies cannot cover.

Exam traps

Creating a 10-year policy without the add-on does not keep logs for 10 years.

Guests and E3 users do not inherit the default 1-year policy.

Priority 1 outranks priority 100; custom always outranks default.

Audit retention is not a content hold: deleting a mailbox still requires eDiscovery or litigation hold if you need the messages themselves.

Organization Configuration, not Audit Reader, is the role that creates these policies.

Official resources

Manage audit log retention policies — default policy, 50-policy cap, durations, priority, PowerShell (updated 2026-06-19)

Learn about auditing solutions in Microsoft Purview — Premium retention and non-user record limits

Loading diagram... How audit log retention policies are evaluated