Check the mailbox's deleted-item setting against deletion dates and quarter close before assuming a departed rep's mail can be recovered.
Key takeaways
- Record deletion dates before the rep leaves.
- Confirm the mailbox setting with your admin.
- Compare recovery dates with the close date.
- Check other company accounts for copies of needed threads.
A rep leaves, the mailbox gets handled, and a few weeks later someone needs a customer thread the rep deleted in their final days. Whether that thread can still be recovered depends on a setting most revenue leaders never look at: how long Exchange Online keeps items that have been permanently deleted.
This post follows one example from start to finish. An account executive is leaving the company partway through the quarter. In the last week, that rep permanently deleted several customer threads, and the team still has to answer two of them before the quarter closes. The rep's mailbox is hosted in Exchange Online.
The two periods to track are 14 days and 30 days. The first is the default that applies when nobody has changed anything. The second is the longest period you can set for an Exchange Online mailbox. Once both numbers are known, you can see how much room you have and where that room ends. Treat this post as a planning guide. Your IT team should make the actual decisions about retention and holds.
Why deleted mail has a clock on it
Microsoft's documentation describes what happens after someone permanently deletes an item. In Outlook or Outlook on the web, a permanently deleted item moves to a folder called Recoverable Items > Deletions and stays there for 14 days by default. After that period, the item is no longer kept in that folder.
For this rep's case, that clock is the core problem. The deletions happened close to the departure, and the quarter closes later. If the default is all that applies, the window to recover those threads could end before anyone asks for them. The question for a revenue leader is not whether the company keeps mail in principle. It is whether the kept period reaches the close date.
The 14-day figure is narrower than it first looks. Microsoft ties it to items permanently deleted in the Outlook apps and on the web, so it does not describe every message anyone has ever removed by other means. Anything outside that description should be confirmed with your admin rather than assumed to follow the same clock.
Deletion history is easy to lose track of when a rep leaves in a hurry. Start tracking on the day you learn the rep is leaving, not on the day someone asks for a thread. By then, the dates you need may already be hard to reconstruct.
Count the 14-day default
Use the default baseline only for items permanently deleted in Outlook or Outlook on the web, unless someone has confirmed that the mailbox is set to something else; confirm other deletions with your admin. The default is what the documentation describes, but the setting on the specific mailbox is the one that counts, so look at it before you run the numbers.
For the departing rep, the arithmetic is simple. Take the date each permanently deleted thread was removed, count 14 days forward, and compare the result with the date you need the mail. If the result falls after that date, the default covers the case. If it falls before, the default is not enough, and the 30-day ceiling becomes the question.
Here is how that looks in practice. Suppose the threads were deleted on the rep's last working day. Counting 14 days from that date gives the end of the default window. If the quarter closes after that point and the team still needs one of the threads, the default alone will not reach the close date. That gap is the reason for the exercise, because it turns a vague worry into a specific date someone can act on.
Keep the list in one place with three columns: the item, the deletion date, and the date the window ends. A spreadsheet is enough. What matters is that someone other than the rep can read it on the day the close review starts.
Put the close date at the top, not in a side note. Every line below depends on that one date, and a wrong close date makes every comparison wrong. If the date moves, update the top line first and rerun the comparisons before anyone relies on the old results. A close date change log can help keep the reason for that change beside the timeline.
Count the 30-day ceiling
The second number comes from the same documentation: "You can change how long items are kept, up to a maximum of 30 days." That sentence sets the ceiling for the deleted-item retention setting in Exchange Online mailboxes.
The gap between the two numbers is the extra room the ceiling adds over the default. It helps to keep that gap beside the 14-day figure, because it shows how far a change could stretch the window if one is needed.
| Setting | Period | What it does for the rep's threads |
|---|---|---|
| Default retention | 14 days | Applies to threads permanently deleted in Outlook or Outlook on the web |
| Ceiling for a mailbox | 30 days | The most room a single mailbox setting can give |
| Litigation hold | retention limit is ignored | Requires a separate decision about preservation |
The ceiling does not tell you everything. Confirm whether a change will reach items already past the default window. Do not assume it. Ask the admin how the setting treats items deleted before the change, and test it on the mailbox before relying on it. A setting that has not been tested is only a hope.
Apply the 30-day setting to the rep's mailbox
Microsoft's walkthrough includes a case that matches this situation closely: "Example 1: Set Emily Maier's mailbox to keep deleted items for 30 days." That is a single-mailbox change, which is the kind that fits one departing rep. Ask whoever manages your Exchange Online settings to make the same change for the rep's mailbox, and note the date it was made, who requested it, and why.
Decide early. A change made in the final days of the quarter leaves little time to confirm that it worked, and little time to act if it did not.
Find the current value before you need it. Some teams only look at mailbox settings when a thread goes missing, which is the worst time to learn what the setting was. Note the value you found, the date you looked, and whether anyone has changed it recently. If the mailbox is already at 30 days, count 30 days forward from each deletion instead of 14, and run the same comparison against the close date.
Illustrative example: compare the dates
Suppose the admin confirms a 30-day setting and a needed thread is permanently deleted in Outlook today. Record the dates and ask the admin to confirm recovery before relying on it.
Microsoft also shows a broader version: "Example 2: Set all user mailboxes in the organization to keep deleted items for 30 days." That is an organization-wide policy, not a fix for one rep. If departing reps regularly leave deleted mail at risk, take that pattern to the people who set company policy. Do not make the organization-wide change just to solve this one case, because it affects every user mailbox, including the ones with no close-date problem.
When a hold changes the math
The documentation includes a line that changes the whole calculation: "If you place a mailbox on litigation hold, the retention limit is ignored."
A hold is a different tool from a retention setting. It is a legal and compliance decision with its own consequences, and it should not be used as a quick way to keep one thread reachable. Holds can look like the easy answer when a deadline is close, which is exactly why they need a second look. If someone suggests a hold for the rep's mailbox, bring legal counsel into the conversation before anyone makes the change, and let them decide whether a hold is needed and why.
If a hold is placed, add it as a separate line for the rep's mailbox. The list should show which rule controlled each thread: the default, the ceiling, or the hold. That matters later, when someone asks why a thread could or could not be recovered, and the answer should not depend on who remembers the conversation.
Today, list the needed threads and their deletion dates, then ask your admin the questions below before comparing recovery dates with quarter close.
Questions to put to your admin
Before the close review, send your admin a short list of questions. The answers will show whether the two periods are enough or whether something else is needed.
- What is the rep's mailbox currently set to keep deleted items for? Your admin needs to check the specific mailbox's current value.
- Does a change apply to items that were already deleted before the change? Confirm this with your admin before relying on the change.
- Who approves a retention change for one mailbox, and how is that approval recorded? Ask your admin to identify the approver and the written record.
- Is there already a hold on the mailbox, and if so, who placed it? Have your admin check for an existing hold and identify who placed it.
- Can the admin confirm the result of any change before the close review starts? Request a mailbox check before the review, with the result recorded in writing.
Get the answers in writing. A verbal answer given on the day of the review leaves little to act on, and nobody can verify it later. If an answer is unclear, do not guess. Mark the item unresolved and keep it visible in the close review.
Look past the mailbox
Email is only one place where a departing rep's information lives. The UK National Cyber Security Centre makes the broader point in its guidance for small organisations: "Once you've secured your email, you should check all the other online accounts your business relies on, especially those that store customer or staff information, or would cause serious disruptions if stolen." The guidance is written for small organisations, but the principle carries over to a sales team of any size.
For the departing rep, that means listing every online account used for company work: the CRM, shared drives, quoting tools, file-sharing services, and any other system where customer threads or attachments might be stored. Some of those systems may hold a copy of a thread that no longer exists in the mailbox. A copy outside the mailbox can solve the problem faster than any retention setting, so look at these systems alongside the mailbox work rather than after it. For missing CRM records, use the separate guide to recovering deleted sales records.
Removal dates matter in other systems too. GitHub's documentation shows why with a time limit: "You can reinstate their access privileges and settings if they enable 2FA for their personal account within three months of their removal from your organization." (GitHub Docs) If your team keeps shared code or documentation there, record the removal date for the access-reinstatement check, rather than treating it as a content-recovery deadline.
For each account, note the system name, who administers it, and whether the rep used a personal login or a shared one. A shared login makes it harder to tell which thread came from which person, so flag it next to the account.
Put the two periods on the close calendar
Use this checklist for the departing rep and for the next one:
- Note the rep's last working day and the quarter close date.
- List each permanently deleted item the team still needs, with its deletion date.
- Calculate each window's end using the confirmed mailbox setting and deletion method, then compare it with the date you need the mail.
- For any item outside that window, ask the admin to review the setting and confirm whether a change can help.
- Refer any preservation requirement to the people responsible for that decision.
- Check the other accounts the rep used for company work, and note whether a copy of each thread exists there.
Keep the timeline useful after the close
Once the quarter closes, the list has a second job. It shows how the timeline played out for the rep: the last working day, the mailbox setting at the time, any change and its date, any hold and who placed it, and which threads were recovered. Keep it in a shared place where finance, sales operations, and IT can all read it, so the next departure does not start from memory.
Review the entries after close. If the same gap keeps appearing across departures, the question is no longer about one mailbox. It is a policy question about the organization-wide setting, and it belongs with the people who own that decision. Do not treat one departure as a policy, and do not treat one quarter's recovery as proof that the default is enough.
For the departing rep, the question is whether each thread can be answered on time, and the timeline will show which threads made it. Start early, ask the questions in writing, and keep the other accounts in view. The mailbox is only one place the answer might be.