Skip down to the research record

Microsoft 365 audit log retention: 5 rules to check

Quota Forecast Editorial Team · Published · 11 min read

Microsoft audit log retention depends on the activity user's license, the log's generation date and the retention policy.

Key takeaways

  • Confirm each editor's license.
  • Check log generation dates.
  • Count existing retention policies.

Why the person who made the change matters

Revenue leaders often assume that the account of the business owner, or the setup chosen by the IT administrator, decides how long those records stay. Microsoft's documentation describes something more specific. Retention depends on the license held by the person who performed the activity.

The rules in this post come from Microsoft's page on audit log retention policies in Microsoft Purview. We cover Microsoft only. Check your deal software's own documentation before you assume its records are covered.

Deal records matter to revenue leaders for everyday reasons. A pipeline review may depend on knowing who moved a deal and when. A commission question may depend on whether an amount was changed after a signature. A forecast may be questioned months later. In each case, the question is whether the record still exists when someone asks for it.

Nothing in this post is legal or accounting advice. How long your firm must keep deal records depends on where you operate and on your industry. Ask your accountant or lawyer for that answer. This post will help you see which settings and which licenses control what Microsoft's audit logs keep, so that you can ask better questions.

Reading the license names

Microsoft uses several license names that look alike. Knowing what each one is saves confusion later.

The first is Office 365 E5, and the second is Microsoft 365 E5. The page lists both in the same sentences, so they are treated the same way in these rules.

The third is the Microsoft Purview Suite. The page says it was formerly known as Microsoft 365 E5 Compliance. If an older name appears on an invoice or a license list, check whether it refers to this suite.

The fourth is the E5 eDiscovery and Audit add-on. The page names it as an alternative to a full E5 license in the rules for longer retention, so it can qualify a user for the one-year period described below.

The fifth is the 10-year audit log retention add-on. It appears only in the ten-year rule, and the page requires it to be held in addition to an E5 license.

Keep these names in front of you when you read the rules. A license that looks similar to another may not qualify.

Rule 1: The default policy covers only licensed users

The first rule decides who is covered at all. Microsoft says that the default audit log retention policy "only applies to audit records for activity performed by users who are assigned an Office 365 or Microsoft 365 E5 license or have a Microsoft Purview Suite (formerly known as Microsoft 365 E5 Compliance) or E5 eDiscovery and Audit add-on license."

In plain words, the built-in default is tied to a short list of licenses. Activity by a user outside that list does not fall under the default policy. Ask your administrator how that activity is kept before relying on its availability.

For a revenue leader, this changes the question. It is no longer "Do we have audit logs?" It becomes "Whose activity is covered by the default?" Deal changes are usually made by several people, such as sellers, sales managers, and sometimes finance staff. Each one may hold a different license, and that license determines whether the default covers that person's activity.

Start with a list. Write down every person who edits deal records in your deal tool or in Microsoft 365, along with the license each one holds. Your administrator is the person most likely to know those licenses, so ask them to confirm each entry. A list that is wrong on the day you need it is worse than no list at all, because it gives false comfort.

Rule two: The creation date sets the default period

The second rule is about time. For Audit (Standard) logs, Microsoft gives two default periods, and the one that applies depends on when the log was generated. The page says that "Audit (Standard) logs generated before October 17, 2023 are retained for 90 days." It also says that "Audit (Standard) logs generated on or after October 17, 2023 follow the new default retention of 180 days."

This matters when you look back at old deal changes. A change made before October 17, 2023 and a change made after that date do not share the same default window. If you need a particular record, look at the date it was generated, not the date you first noticed the problem. A record you noticed last week may have been generated much earlier.

The page's 90-day and 180-day periods refer to Audit (Standard) logs. Do not apply those numbers to other types of log without checking the page for that log type. A mistake here is easy to make, because the numbers look like general facts about every log.

Put the cutoff date in your records calendar, so your team knows which default period applies to which group of changes. A simple note next to your list of users is enough.

Rule 3: Keeping logs past 180 days needs a qualifying user license

The default period is not always enough for a revenue team. Microsoft says: "To retain an audit log for longer than 180 days (and up to 1 year), the user who generates the audit log (by performing an audited activity) must have an Office 365 E5 or Microsoft 365 E5 license or a Microsoft Purview Suite (formerly known as Microsoft 365 E5 Compliance) or E5 eDiscovery and Audit add-on license."

Three points stand out. First, the extended period runs up to one year, and this rule does not go further. Second, the license belongs to the user who performed the activity. It is not the license of the administrator who sets up the policy. Third, the list of qualifying licenses is wider than a full E5 license alone. The Purview Suite and the E5 eDiscovery and Audit add-on also qualify.

For a sales manager who wants a full year of records on deals changed by a rep, the question is whether that rep holds one of those licenses. Setting a longer policy is not enough by itself, because the rule attaches to the person who made the change.

This also means the rule can change over time. When someone changes roles, or when your firm buys or drops a license, the people covered by the one-year period may change too. Review the list when staffing or licensing changes, not only once a year.

Rule 4: Ten years needs an add-on on top of E5

Some firms want records kept for a decade, perhaps because of contract questions, tax questions, or a dispute that could arise years later. Microsoft says: "To retain audit logs for 10 years, the user who generates the audit log must also have a 10-year audit log retention add-on license in addition to an E5 license."

This is the strictest of the five rules, and it has two parts. The user needs an E5 license, and the user also needs a separate 10-year audit log retention add-on. The words "in addition to" mean that one does not replace the other. Having E5 alone does not meet the ten-year rule, and having the add-on alone does not meet it either, because the page asks for both.

The rule also attaches to each person. If one seller has the add-on and another does not, the page ties the ten-year period to the first seller's license and not to the second. You cannot assume that the same period covers every seller on your team.

Before you buy add-ons for a whole team, decide which records truly need ten years. That decision is a business and legal question first and a software setting second. Ask your accountant or lawyer which records need that length before you pay for add-ons across the firm. Paying for ten-year coverage for every seller when only a few deals need it is an expensive way to answer an unclear question.

Rule 5: A firm can have up to 50 retention policies

The last rule is about structure, not licenses. Microsoft says: "Your organization can have up to 50 audit log retention policies."

Fifty is a ceiling for the whole organization, not for each team or each user. Nothing in the page requires a separate policy for every rep, so there is no need to create one for each person. A short list of well-named policies is easier to check and easier to explain to an auditor or a new hire.

A longer policy still depends on the license of each user, as Rules 3 and 4 explain. Creating a policy with a longer period does not give every user that period. The license check happens person by person.

Before adding a policy, count the ones you already have. Keep a simple sheet that lists each policy, the group of users it covers, and the period it sets. That sheet makes it easy to see how close you are to the limit of 50, and it shows whether any two policies overlap in a confusing way.

Illustrative example: Counting policies

An illustrative firm counts 40 existing policies against the limit of 50. It can add 10 before reaching the ceiling. Before creating another policy, it checks its sheet for an existing policy covering the intended users and period.

Common mistakes to avoid

Mistake 1: Assuming the administrator's license is what matters. Rules 3 and 4 tie the longer periods to the user who performed the activity, not to the person who set up the policy.

Mistake two: Treating E5 as the whole list. The page names several licenses that qualify for the one-year period, including the Purview Suite and the E5 eDiscovery and Audit add-on. It names a separate add-on for ten years, and that add-on must sit alongside E5.

Mistake 3: Assuming one date fits every record. For Audit (Standard) logs, the date a log was generated sets its default period, as Rule two explains. A change from before October 17, 2023 and a change from after it are not handled the same way by default.

Mistake 4: Assuming 180 days is the longest you can keep logs. Microsoft's page describes longer periods for licensed users. The one-year period and the ten-year period both exist, but each depends on the right license on the person who made the change.

Mistake 5: Forgetting the limit on policies. A firm can have up to 50 audit log retention policies. A firm that creates policies without writing them down may not know how many it already has, and that makes the limit hard to manage.

Mistake 6: Reading only a summary. The license details sit inside full sentences on the Microsoft page. Read the rule itself before you decide anything, and do not rely on a paraphrase, including this one.

Today, list everyone who edits deal records and ask your administrator to confirm their licenses.

Related guides: Log seller emails to the right deal: 4 CRM rules to check · Activity linking: 8 rules for deals and visibility · AI call scorecard checks: 5 rules before the forecast.

Questions to ask your administrator

Bring these questions to your administrator or your Microsoft partner. Write down the answers and keep them with your license list.

Which of our people hold a license that the default policy covers?

Check each person's assigned license against Rule 1.

For each person who edits deal records, is the one-year period available, and is the ten-year period available?

Compare their licenses with Rules 3 and 4.

How many audit log retention policies do we have now, and how many can we still add under the limit of 50?

Subtract your current policy count from 50.

Which of our deal changes were generated before October 17, 2023, and which default period applies to each group?

Check generation dates against Rule two's historical periods.

If someone who is not covered by the default policy edits a deal, how is that activity kept?

Ask your administrator to confirm the applicable retention arrangement in writing.

Does our deal software send its changes into Microsoft's audit log at all?

Check your deal software's own documentation before applying these rules.

The last question is easy to skip, and it is one of the most important. If a change never reaches the audit log, no retention rule can keep it.

What to do this week

Start small. You do not need to finish everything in one day.

  • List everyone who edits deal records, and the license each person holds.
  • Group those people by what the rules allow: covered by the default policy, eligible for the one-year period under Rule 3, or eligible for the ten-year period under Rule 4.
  • Decide which records you truly need to keep, and note their generation dates so you know which default period applies to each.
  • Count your current retention policies against the limit of 50.
  • Send the list to your administrator, and ask your accountant or lawyer which period your records require.

After this work, you will know which of your people are covered and for how long. That is a much better position than assuming the records are safe because a setting exists somewhere in the account.

Check these details before you need the records, not after. A revenue leader who learns the rules during a dispute is learning them too late.

Sources