Skip ahead to the main page
Partner Huddle
Pages

Employee data retention: 5 tools to check when staff leave

Partner Huddle Editorial Team · Published · 10 min read

When an employee leaves, check if a legal requirement or important need calls for saving their data, and coordinate that with securing access. Microsoft Learn notes that firms must decide how to secure data and prevent unauthorized access during departures.

Key takeaways

  • Check whether a legal requirement or important need calls for saving the former employee's data.
  • Identify whether a successor will take over the work and need access to its files, then coordinate that access with securing the departing employee's access.
  • Check retention policies or labels on SharePoint and OneDrive sites, not a notebook's Modified date.

Employee data retention: checks for a staff departure

The first step in managing a staff departure is determining whether the former employee’s information requires preservation. According to Microsoft Learn, you want to preserve the former employee's data if there is a legal requirement or important need to save it.

Simultaneously, identify if another team member will take over the departing person’s responsibilities. The same source states that if someone is taking over the work, it is helpful for them to access this information. You must balance these two needs: protecting sensitive records from unauthorized use while ensuring the successor has the files necessary to continue client work without interruption.

Do not assume that deleting an account automatically handles all retention obligations. The scope of what you must keep depends on your specific firm policies and applicable laws, which vary by jurisdiction. Your review should distinguish between data needed for ongoing operations and data required for compliance or audit purposes.

Start by documenting the reason for preserving any data as you change access rights. If no legal requirement exists, note that fact explicitly so future administrators understand why certain records were deleted rather than retained. This documentation supports consistent handling of similar departures later.

Before account changes, identify successor and preservation needs

Before you change any accounts or delete access, determine whether the departing employee's work has a designated successor or if specific legal obligations require keeping their data. These two factors drive which records stay active and which move to preservation status.

If no one is directly inheriting the workload, check for external drivers that mandate retention. This distinction separates routine offboarding from compliance-driven preservation. A firm might retain data not because a colleague needs it, but because regulatory guidelines or internal policy demand a record of past activities.

To apply this, ask two questions before touching the IT console. First, does another staff member need read or write access to ongoing projects? If yes, transfer ownership rather than deleting the user. Second, does any law, contract, or firm policy require keeping this person’s communications or files for a set period? If yes, arrange a hold or archive for those items without delaying the access change, and check the procedure for each tool. Documenting these answers creates a clear audit trail for why certain data remains accessible while other data is removed.

Illustrative example of a departure

Suppose a departing employee owned 20 project folders, and a successor will take over 10 of them. Give the successor access to those 10 folders, and secure the departing employee's account at the same time. For the other 10, check whether a legal requirement or important need calls for saving them. If one does, place those folders under a hold and record the reason beside each one. Then check the retention settings on each site, rather than the Modified date, before you close the review. Finally, note the successor's name and the date the access change was made.

During the review, distinguish retained documents from audit logs

Retained documents and audit logs follow different technical paths in Microsoft 365. When you review a departing employee's records, treat file retention and identity logging as separate systems. The following details clarify how each system handles data preservation.

SharePoint and OneDrive file retention All files stored in SharePoint (and SharePoint Embedded) or OneDrive sites can be retained by applying a retention policy or retention label, according to Microsoft Learn. This applies regardless of whether the site is active or archived. For administrators, there's very little change to how retention policies and retention labels work and are managed for sites that use Microsoft 365 Archive, which simplifies oversight when staff leave and their associated sites transition states.

A critical distinction exists for notebooks. Although you see a Modified date for each individual notebook, this date isn't used by Microsoft 365 retention. Do not use it to decide whether a notebook is under hold; check the applied retention policy or label directly.

When a document with versions is subject to retention settings to retain that content, and it's not marked as a record, how the versions are stored in the Preservation Hold library changed in July 2022 to improve performance. If your firm relies on version history for workpaper recovery or client engagement documentation, verify that your current environment reflects these storage behaviors.

Entra ID audit log separation Microsoft Entra ID audit and sign-in logs are separate from the Microsoft 365 Unified Audit Log (UAL), according to Microsoft Learn.

Extended retention for Entra ID audit logs requires specific licensing. Organizations with Microsoft 365 E5, Office 365 E5, Microsoft Purview Suite, or E5 eDiscovery and Audit add-on licenses can also use Microsoft Purview Audit (Premium) to retain Microsoft Entra ID audit logs beyond the default period, providing an alternative to exporting logs to Azure Storage.

Action step Confirm which license tier covers your firm’s Entra ID subscriptions before assuming extended audit-log retention is active. Verify separately that retention policies or labels are applied to the specific SharePoint and OneDrive sites where the departing employee worked.

During the review, inspect Slack, Atlassian and Box content

When reviewing workspace content for a departing staff member, check three specific tools where file visibility and ownership rules differ. Each tool handles unshared files, deleted accounts, and trash items in distinct ways that require separate inspection steps.

Slack unshared files Check for files that have no shares. According to Slack, these files have a 30-day grace period. After this period ends, they are hidden from the organization. Identify any critical work products in this state before the deadline passes, as they will not be visible to remaining team members once hidden.

Atlassian account deletion records Review the records associated with deleting a managed account. The documentation for Delete a managed account | Atlassian Support lists four categories of information to consider. First, information related to purchases is kept for financial reporting purposes. Second, records showing that an account was deleted may need to be provided to regulators. Third, content the user created in Atlassian account services, such as pages, issues, and comments, is part of the review. Fourth, any personal data in content created by the user or someone else, such as names or email addresses typed into a page or issue, must be accounted for. Ensure your firm’s preservation strategy covers all four categories before proceeding with account deletion.

Box trash filters Use the trash management features to locate deleted items owned by the departing employee. According to Managing Trash – Box Support, two different filters serve distinct purposes. The "Items I own" filter displays all deleted items you own, regardless of who deleted the item. Run this filter from the account whose trash you are viewing, so you see the deleted items that account owns. Do not confuse this with the "Items I deleted" filter, which displays all items you have deleted, regardless of who created or owns the item.

Record which filter results contain client-sensitive data or active project files. Move these items to a secure location or restore them according to your firm’s retention policy. If no files appear in the ownership filter, confirm that the employee did not own any deleted items in Box.

Related guides: Client data access controls: 4 tools for a firm WISP · Client payroll employee file: 4 checks before pay.

After the review, record unresolved preservation questions

Write the specific reason for preserving data beside each retained item. If no such need exists, do not retain the data beyond standard account closure procedures. This documentation creates a clear record of why certain files were saved while others were deleted. Keep the entry brief, naming only the legal obligation or business necessity identified during your initial review. Do not speculate about future uses; state the current requirement as it applies to this specific departure. This practice supports consistent handling across different staff departures without inventing new retention rules for each case.

Employee departure reference table

The table below maps each publisher’s documented retention behavior to the specific tool context where it applies. Use this as your quick-reference during the review, noting that each row reflects only the rule stated by that source.

PublisherTool ContextRetention Behavior
Microsoft LearnSharePoint and OneDrive sites All files stored in these sites can be retained by applying a retention policy or label
Microsoft Learn Microsoft Entra ID audit and sign-in logsThese logs are separate from the Microsoft 365 Unified Audit Log (UAL)
SlackFiles with no shares A 30-day grace period applies before they are hidden from the organization
Atlassian SupportPurchase information Information related to purchases is kept for financial reporting requirements
BoxItems I own filter Displays all deleted items you own, regardless of who deleted the item
Microsoft LearnExtended audit log retention Verify whether listed licenses support extended retention through Audit Premium

Apply these checks to one departing employee today, starting with the successor's access needs and the documented reason for preserving data.

Employee records across the firm's tools: FAQ

What should employee data retention checks cover when someone leaves?

Checks should address the need to secure data and prevent unauthorized access. You also want to complete the step if there is a legal requirement or important need to save the former employee's data, according to Microsoft Learn.

Does my firm's Microsoft license support extended Entra audit-log retention?

Organizations with Microsoft 365 E5, Office 365 E5, Microsoft Purview Suite, or E5 eDiscovery and Audit add-on licenses can use Microsoft Purview Audit (Premium) to retain Microsoft Entra ID audit logs beyond the default period, according to Microsoft Learn. This provides an alternative to exporting logs to Azure Storage.

Is a notebook's Modified date used by Microsoft 365 retention?

No, the Modified date shown for an individual notebook is not used by Microsoft 365 retention, as noted in Microsoft Learn.

When are Slack files with no shares hidden from the organization?

Files with no shares have a 30-day grace period and then they are hidden from the organization, according to Slack.

Which Box filter finds deleted files an employee owns regardless of who deleted them?

The Items I own filter, according to Box, displays all deleted items you own, regardless of who deleted the item.

Sources