Microsoft Purview offers eight audit log retention durations, plus a licensed 10-year option; choose a window that covers your review timeline.
Key takeaways
- Match retention to when reviewers may need the history.
- Confirm subscription and add-on requirements before choosing a duration.
- Check policy scope and priority.
- Test a known change and save the records your review needs.
Why deal history matters at quarter-end
A quarter-end review often comes down to three questions. Who changed this deal? What did they change? When did it happen? The answers sit in your audit log. If the log has already aged out when someone asks, you cannot show the history, no matter how careful the team was when the changes were made.
Retention is the setting that decides how long those records stay available. For a revenue leader, the useful question is not how auditing works in general. It is whether the record will still exist when the review happens, and whether you can show it in a form the reviewers will accept.
This post uses Microsoft Purview audit log retention policies as the example, because Microsoft publishes a clear list of retention durations and the licenses behind some of them. If your deal records sit in a different system, check that system's retention settings and apply the same planning steps. For related record checks, see deal change records.
The eight retention options
Microsoft's audit log retention policies offer eight durations: 7 Days, 30 Days, 6 Months, 9 Months, 1 Year, 3 Years, 5 Years, and 7 Years. You can read the full guidance in Manage audit log retention policies. These eight are the standard choices. One longer option exists for some licensed users, and it is covered in its own section below.
Here is how to think about each one for a quarter-end review.
7 Days only helps with a check on very recent activity. A review that looks back over a full quarter will not be served by it. Use it for short-term monitoring, not for a deal history you may need later.
30 Days is still short. It can help confirm a change made in the past few weeks, but it will not cover a full quarter's activity. If a deal was changed early in a quarter and the review comes after the quarter closes, this window may already have passed.
6 Months can cover a full quarter of deal activity, plus preparation time, depending on when the review happens. Check the oldest change you need against the review date before choosing it.
9 Months adds room if the review comes well after the quarter closes, or if the same deal is revisited in more than one review cycle.
1 Year can cover the quarter and leave room for later questions. It gives room for a year-end audit, a dispute about terms, or a follow-up question about the same deal long after the close.
3 Years, 5 Years, and 7 Years fit deals that may be questioned long after they close. The right length is set by your company's records policy and, where it applies, by your legal or finance advisers. The tool does not decide that for you. It only determines what it keeps.
Each longer option has a licensing condition, and that condition matters as much as the label. The next sections cover it.
The 10-year option and who can select it
Microsoft states that users with the 10-year Audit Log Retention add-on license can select a 10 Years option. See Manage audit log retention policies for the current wording.
If your organization needs history beyond seven years, confirm eligibility before building that duration into your plan.
Ask your admin to confirm which retention options are available for your intended use.
Which licenses the longer options need
Some options depend on which Microsoft 365 subscription and add-on licenses your organization has. The requirements Microsoft states are these:
- 7 Days and 30 Days require a Microsoft 365 Enterprise E5 subscription. Source
- 3 Years, 5 Years, and 7 Years require the 10-Year Audit Log Retention add-on license assigned to you in addition to your Microsoft 365 Enterprise E5 subscription. Source
For the 6 Months, 9 Months, and 1 Year options, confirm licensing with your Microsoft licensing contact or your admin before you depend on them.
How policy priority works
Each audit log retention policy has a priority value. Microsoft's guidance says a value of 1 is the highest priority, and a value of 10000 is the lowest priority. See Manage audit log retention policies.
This matters when more than one policy could apply to the same records. Do not assume the longer policy wins. Check the priority numbers of every policy that might touch your deal records, and confirm which one you expect to govern them.
Before quarter-end, write down a short list of every active retention policy. For each one, record its scope, its duration, and its priority value. This list is what you will show a reviewer if they ask how the history was kept, so keep it current.
Changes take time to apply
Removing a policy is not instant. Microsoft notes that a policy is removed from the dashboard first, and it might take up to 30 minutes for the policy to be removed from your organization. See Manage audit log retention policies.
That matters if you plan to swap a short policy for a longer one just before a review. A last-minute change may not take effect in time. Make policy changes well ahead of the review, then check that the setting you expect is the one in force.
The goal is a setup that is already correct, so no one has to rely on timing.
Where to set up the policies
Microsoft says you can create and manage audit log retention policies in the Microsoft Purview portal. See Manage audit log retention policies. Microsoft also describes these policies as part of the new Microsoft Purview Audit (Premium) capabilities. Check with your admin that your organization has those capabilities before you plan around them.
Make sure the person who will manage the portal has access to the policy settings. A policy that only one unavailable person can change is a risk in a tight review cycle. Name a backup owner and write that name down with the policy list.
Illustrative example: a delayed review
Imagine a deal that closed in the last weeks of a quarter. Early in the quarter, a discount was changed. More than 30 days later, a finance partner asks who approved that change and when it was made.
Work through the options. A 30-day window would have expired before the question arrived, so that is out for this purpose. A longer window might still hold the change, but only if the question comes within that window and nobody waits too long to ask. Choose a window that also leaves room for follow-up questions that come later, such as a renewal dispute or a year-end audit.
Take the next step today
Ask your admin for the active policy list today, then use the questions below to check the duration, licensing and ownership before your review.
Related guides: Microsoft 365 audit log retention: 5 rules to check · Access log checks: 4 steps after a shared login changes.
Questions to ask your admin
Before you rely on any retention option, ask your admin these questions. Write the answers down.
- Do we have Microsoft 365 Enterprise E5 for the accounts that will set and check the policies?
Confirm your subscription with your admin before choosing a duration.
- Which accounts hold the 10-Year Audit Log Retention add-on license, if any?
Ask your admin to identify the relevant license assignments.
- Which retention policies are active now, and what is the priority value of each?
Use the active policy list to check for overlapping scope.
- Who can change or remove those policies, and how long does a removal take to apply across the organization?
Identify the policy owner and allow time to check the result after removal.
- Does our Microsoft Purview setup include the Audit (Premium) capabilities that hold the retention policies?
Have your admin confirm access to the policy settings in your setup.
If the answers are unclear, do not guess. Ask the licensing contact or the admin who manages the tenant. A short written answer now is far cheaper than a failed search during a review.
What a review usually asks for
Reviewers tend to ask for the same few things. They want to know who made each change, what the change was, when it was made, and whether it was approved. They may also want to see the state of the deal before and after the change.
An audit log can answer some of these questions, but only if the record still exists and is searchable. The retention policy decides the first part. Your own process decides the rest. Keep deal names and identifiers consistent across your CRM, your finance system, and any spreadsheets, so that a search for one deal returns the records for that same deal. For date changes, use the close date change log guide alongside your review.
Reviewers also respond well to clarity. A short written note that explains how the history was kept is often more useful than a large export with no explanation.
Working with finance and legal
The retention choice is not only an IT decision. Finance and legal often have a view on how long deal records should be kept. Involve them early, especially for deals with long payment terms, contract renewals, or disputes that may come up after the quarter closes.
Ask finance which records the quarter-end review needs, and ask legal whether any records must be kept for a set period. Then match the audit log retention to those answers. Where your company's records policy sets a period, that period should guide your choice, not simply the shortest option that is easiest to set.
Keep a record of who agreed to the retention choice and when. That record is useful evidence that the decision was made deliberately.
A plan for quarter-end
Here is a simple order of work. Each step is general practice, not a Microsoft requirement.
- Decide the longest question you might face. Ask how long after a quarter closes someone might want the history for a deal. Pick the duration that covers that window, not just the quarter itself.
- Confirm the license. Use the licensing section above. Check the subscription and any required add-on assignment before you commit.
- Set the policy scope. Scope the policy to the activity that touches your deal records, and write down exactly what it covers. A policy that does not reach the right activity will not help the review.
- Check priority. Compare the new policy's priority with any existing policy that could apply to the same records.
- Test with a known change. Make a small, known change to a test deal, then search the audit log for it. Confirm you can find it and that the details look right.
- Keep your own copy. Export the change records the review will need, and store them under your business records rules. Do not treat the audit tool as your only archive.
- Set a reminder. Put the end of the retention window on your calendar, well ahead of the review, so you can act before anything expires.
Work through these steps in the quarter before the review, not during it. A test that runs the week of a review leaves no room to fix what it finds.
Common mistakes
Assuming the longest option is always on. The option you choose has to be set, licensed, and verified. A long duration on paper does not help if the license is missing.
Waiting for the review to check. By the time someone asks for the history, a short window may already have passed. Check the policy while there is still time to change it.
Changing policies at the last minute. Overlapping policies can make the result harder to predict.
Forgetting the explanation. A reviewer who sees a long history with no context may still have questions. Write a short note on the policy and how the records were kept.
What to give the review team
Prepare a short note for the reviewers. Include the name of the policy that covered the deal records, its duration, the date it was set, the person who set it, and where any exported copies are stored. Add the priority value and any other policy that might have applied.
With that note, reviewers can see that the history was kept on purpose, not by luck. It also shows that the retention setting was checked before the review, which tends to shorten the questions that follow.
Keep the note with the exported records, and update it if the policy changes. An old note that describes a policy no longer in force creates confusion of its own.