An audit log retention policy lets you specify how long to retain audit logs in your organization, according to Microsoft Learn. Before you change any policy, review four settings: the 90-day period for older Audit (Standard) logs, the retention options from 7 Days to 7 Years, the priority value, and the removal delay of up to 30 minutes.
Key takeaways: the 4 settings
- older Standard logs: according to Microsoft Learn, Audit (Standard) logs generated before October 17, 2023 are retained for 90 days, so write that period at the top of your review sheet before you edit any policy.
- retention options: according to Microsoft Learn, the available options are 7 Days, 30 Days, 6 Months, 9 Months, 1 Year, 3 Years, 5 Years, and 7 Years, so match each policy to the period your firm has written down.
- priority value: according to Microsoft Learn, a policy with a value of 5 takes priority over a policy with a value of 10, so sort the list by value before you change anything.
- removal delay: according to Microsoft Learn, it might take up to 30 minutes for a removed policy to be removed from your organization, so recheck after that window before you mark the removal finished.
Why a small firm reviews audit log retention
Retention settings are easy to leave untouched, so a review gives you a fixed time to read each one and write down what you find. A short review repeated on a schedule suits these settings better than a single setup session, and it is worth repeating whenever the people who administer the tenant change.
A reviewer who opens the portal with the four settings already written down can compare what is in place against what the firm expects, instead of deciding both at once. That separation keeps the discussion of what the firm needs apart from the work of reading the current configuration.
The period comes first among the four settings, because the other checks depend on knowing how long the logs are meant to stay. Decide who approves a change to that period before anyone opens the portal, so the decision is written down first.
The checks in this article follow four questions in order: how long the older logs stay, which options exist, which policy wins when values differ, and how long removal takes. Reading them in that order keeps the review tied to the questions a reviewer will ask. For the wider systems review these settings belong to, read the Tax firm security checklist alongside this one.
Before: where policies are managed
Your review begins in the Microsoft Purview portal, where, according to Microsoft Learn, you can create and manage audit log retention policies.
A list of every policy you find there, including any that someone else created, becomes the working sheet for the rest of the review. Beside each entry, record the policy's name, the retention option it uses, and its priority value. The list belongs in a shared location that the next reviewer can open without asking you first.
Once the list is complete, check that each entry has all three details filled in. An entry with a missing detail is one you have not finished reviewing, so mark it before the later checks begin. A simple mark beside the name is enough to keep it from being overlooked.
If you find a policy that nobody on the team recognises, record it in the list anyway and flag it for the person who owns the tenant. The list is a record of what exists, not a record of what you expect to exist. Add a second column for the date you last looked at each policy, so the sheet shows how current it is.
Keep the sheet in the same order from one review to the next. That consistency lets you compare two sheets line by line instead of searching for each policy name again.
Before: how long the options run
Write the older-log period next to the list of retention options on your sheet, so the comparison is visible. The 90-day period for Audit (Standard) logs generated before October 17, 2023, according to Microsoft Learn, does not match any of the options listed above, so compare the two with care before you choose.
The option that fits your firm is the one that matches what the firm needs to keep, not automatically the longest one on the list. A chosen option is a setting in the portal, so confirm the period with whoever owns the firm's records before you commit to it. When the choice differs from the older-log period, write the reason on the sheet so the next reviewer can follow it.
When you write the firm's own period on the sheet, use the same wording as the options list, such as 1 Year or 6 Months, so the two can be compared directly. A period written in different words is harder to match against the list during the review.
Write the chosen option for each policy beside its current value, so the difference between the two is visible during the review.
During: policy priority values
Sorting the list by priority value before you edit anything lets the review follow the order those values set. A sorted sheet is also easier to scan than a list of policy names in the order they were created.
Work down the sorted list one entry at a time, rather than jumping between policies as they come to mind. Each change needs a short note: which policy moved, the value it had before, and the value it has now.
When two values are close, the note should record which policy has priority under the rule in the key takeaways, so the reasoning stays visible later. If two policies have values you cannot explain, stop and ask whoever created them before you edit either one.
The priority example in the key takeaways shows which value wins in one pair, so record each pair of close values on its own line instead of assuming the same pattern holds for every pair on your list.
Copy each policy's current value into its note before you change it, so you can show what changed if someone asks later. Those notes belong beside the list from the earlier stage, so each entry can be traced from the first check to the last.
During: removal delay
A removed policy is not finished the moment it leaves the dashboard. The source separates two moments, the policy leaving the dashboard and the policy leaving your organization, according to Microsoft Learn.
After removing a policy, record the time and check again once up to 30 minutes have passed. The removal is not finished until that check confirms it. If the check does not yet confirm the removal, leave the policy on the list with its status marked, so the next reviewer can see the removal was still open.
Write the time of each removal beside the policy name, then the time of the recheck. Two timestamps make it possible to see whether the removal finished within the up to 30 minutes the source describes, and to note the person who ran the check.
After: records to keep on file
One file can hold the policy list, the priority notes and the removal times. Date each entry, so the change history can be read in order, and add the name of the person who approved each change. Store the file where the next reviewer can read it without help.
At the end of each review, write one line that says when the review took place and who carried it out. That line turns the file from a set of notes into a record that someone can check later.
If the firm keeps the sheet in a shared location, limit edits to the person who owns the tenant, so each change has one named author. Two people editing the same entry at once make the change history harder to follow.
Property records are a separate question, and according to Internal Revenue Service, you must keep these records to figure your basis for computing gain or loss when you sell or otherwise dispose of the property. An audit log retention period does not answer that question, so check property records with whoever handles the firm's tax files.
Keeping the audit log file and the property records file separate lets each one answer its own question. When staff leave, read Employee data retention: 5 tools to check when staff leave alongside this review. Before removing any account, read Account deletion for firm records.
The table below pairs each publisher with one quoted sentence from its page.
| Publisher | Source page | Quoted sentence |
|---|---|---|
| Microsoft Learn | Manage audit log retention policies | The available options are 7 Days, 30 Days, 6 Months, 9 Months, 1 Year, 3 Years, 5 Years, and 7 Years. |
| Internal Revenue Service | Recordkeeping | You must keep these records to figure your basis for computing gain or loss when you sell or otherwise dispose of the property. |
Illustrative example: one removal check
Suppose a reviewer lists 10 policies and sorts them by priority value. Two of them have values of 5 and 10, the same pair as the priority example in the key takeaways, so the note records that the policy with value 5 takes priority over the policy with value 10. The reviewer removes one policy at 9 a.m., writes that time beside its name, and rechecks 30 minutes later. The policy is still listed at the recheck, so the reviewer leaves it open on the sheet and marks its status. This example is illustrative and describes no real firm.
Next step: list your current policies
Your next step is to open the Microsoft Purview portal, list your current retention policies and note each priority value.
Use this layout to start the list, with one row for each policy. Once the sheet is complete, you can compare it with the option list before you change a single setting.
| Policy | Retention option | Priority value | Removal check |
|---|---|---|---|
| Example | A listed option | A numeric value | A recheck note |
FAQ: audit log retention questions
Where do I manage audit log retention policies?
According to Microsoft Learn, you can create and manage audit log retention policies in the Microsoft Purview portal. Start your review there, with the list described above.
How long are older Standard logs kept?
According to Microsoft Learn, Audit (Standard) logs generated before October 17, 2023 are retained for 90 days.
Which retention options are available?
According to Microsoft Learn, the options run from 7 Days to 7 Years. Choose the one that matches the period your firm has written down, and record the reason beside it.
How long does removing a policy take?
According to Microsoft Learn, it might take up to 30 minutes for a removed policy to be removed from your organization. Recheck after that window before you treat the removal as finished.