Office 365 Archives -

Microsoft 365 Departed User Archiving: The Complete Guide for Enterprise IT

by Mark | Apr 6, 2026 | Office 365

Microsoft 365 Departed User Archiving

When an employee leaves your organisation, a clock starts ticking. Microsoft begins deleting their data — OneDrive files, Exchange Online emails, Teams conversations — within days of their account being disabled. For most large enterprises this is happening continuously, quietly, and without IT teams necessarily knowing until someone asks for data that no longer exists.

This guide covers everything IT leaders and administrators at large enterprises need to know about Microsoft 365 departed user archiving: what data is at risk, how long you have before it is deleted, what Microsoft’s native tools can and cannot do, how to automate the entire archiving process, and how to make a decision that satisfies your compliance team.

What Is Microsoft 365 Departed User Archiving?

Microsoft 365 departed user archiving is the process of capturing and preserving an employee’s OneDrive, Exchange Online, and Teams data when they leave your organisation — before Microsoft’s deletion timelines expire and that data is permanently lost.

Unlike standard document archiving, departed user archiving is triggered by a people event rather than a content policy. The moment an employee’s account is disabled in Microsoft Entra ID, the clock starts. Without an archiving solution in place, your organisation has a narrow window to capture that data before it is gone forever.

For large enterprises with ongoing staff turnover, this is not a one-time exercise. It is a continuous operational requirement that affects every departure — resignations, redundancies, retirements, and contract endings alike.

What Data Is at Risk When an Employee Leaves?

OneDrive for Business

OneDrive files belonging to a departed user are retained for 93 days after their account is disabled. After that Microsoft permanently deletes them. During the 93-day window an administrator can access and copy the files, but this requires manual intervention before the deadline.

Exchange Online

Exchange Online mailboxes follow a different timeline. If no licence or retention policy is in place, the mailbox is typically soft-deleted 30 days after the account is disabled and permanently deleted 30 days after that. Emails, calendar items, contacts, and tasks are all at risk.

Microsoft Teams

Teams channels the departed user participated in remain accessible to other team members. However, private chat messages and files stored in the departed user’s personal OneDrive are subject to the same deletion timelines as their OneDrive content. Once those timelines expire, the chat history and associated files cannot be recovered.

Microsoft’s Default Deletion Timelines

Data Type	Default Retention After Account Disabled	Permanently Deleted
OneDrive files	93 days	Day 93
Exchange Online mailbox	Soft-deleted at 30 days	Permanently deleted at 60 days
Teams private chat history	Tied to OneDrive deletion	Day 93
Teams channel content	Retained while channel exists	When channel or site is deleted

Why Manual Departed User Data Management Fails at Scale

Most organisations handle departed user data in one of three ways, all of which carry significant cost or risk.

Keeping licences active

Keeping a Microsoft 365 licence active after an employee leaves preserves all their data indefinitely. The problem is cost. At $36 per user per month for Microsoft 365 E3, retaining 100 departed users on active licences for an average of three months while IT handles manual data management costs over $10,000 per year in unnecessary licence spend — and that is before accounting for the IT time involved.

Manual data export

IT teams can manually export OneDrive files, Exchange mailboxes, and Teams data before an account is disabled. The problem is scale and consistency. For enterprises processing dozens of departures per month, manual export is time consuming, error prone, and relies entirely on IT remembering to do it before the account is disabled or the deletion window closes. One missed departure can mean permanently lost data.

Microsoft retention policies

Microsoft Purview retention policies can prevent data from being deleted after an account is disabled. However they require careful configuration, add complexity to your Purview environment, do not necessarily allow you to remove the licence, and do not provide a searchable, organised archive of departed user data that HR, legal, or management teams can easily access.

What a Proper Departed User Archiving Solution Does

A purpose-built Microsoft 365 departed user archiving solution automates the entire process — detecting departures, capturing data, organising it into a searchable archive, and confirming completion so licences can be safely removed. Here is what it should deliver:

Automatic detection of disabled accounts in Microsoft Entra ID with no manual trigger required
Archiving of OneDrive, Exchange Online, and Teams data in a single automated workflow
Storage of archived data in your own Azure Blob Storage — not a third-party vendor’s infrastructure
Searchable, organised archive accessible to authorised HR, legal, and IT staff
Confirmation notification when archiving is complete so licences can be removed immediately
Full audit trail of every archiving action for compliance and governance purposes
Scalability to handle high volumes of departures without additional IT workload
Compatibility with Microsoft Purview legal holds and eDiscovery

How Chipmunk Automates Microsoft 365 Departed User Archiving

Chipmunk is SmiKar’s purpose-built Microsoft 365 departed user archiving solution. It monitors your Microsoft Entra ID continuously and automates the entire archiving workflow the moment an account is disabled.

Automatic departure detection

Chipmunk monitors your Entra ID for accounts that have been disabled or deactivated. The moment a departure event is detected, Chipmunk creates an archiving job automatically. No manual trigger is required from your IT team.

Complete data capture

Chipmunk captures the full contents of the departed user’s OneDrive, their complete Exchange Online mailbox including sent items, calendar, and contacts, and their Microsoft Teams chat history and associated files. All three data sources are captured in a single automated workflow.

Data written to your own Azure Blob Storage

Captured data is processed through SmiKar’s secure Chipmunk appliance and written directly into your own Azure Blob Storage account in your own Azure tenant. Your data never sits in SmiKar infrastructure — it goes straight into storage you own and control. Chipmunk organises archived data by user, making it straightforward to locate a specific user’s data when needed.

Licence removal confirmation

Once archiving is complete, Chipmunk sends a confirmation notification to your nominated IT administrators. The Microsoft 365 licence can then be safely removed — typically on the same day the account is disabled — with complete confidence that nothing has been lost.

Searchable, restorable archive

Archived data is stored in a structured, searchable format. Authorised HR teams, legal teams, and IT administrators can search across completed archives, export specific items for compliance or legal purposes, and restore data to another active user or a secure destination when needed.

Microsoft 365 Departed User Archiving for Compliance

For organisations in regulated industries, retaining departed user data is not optional. A range of regulatory frameworks create scenarios where access to former employee data is essential months or years after their departure.

GDPR — organisations must be able to respond to data subject access requests for former employees and demonstrate lawful basis for retention
Financial services — FCA, MiFID II, and similar frameworks require retention of communications for specified periods
Healthcare — clinical and administrative communications must be retained in line with applicable regulations
Employment law — records relevant to disputes, redundancies, and tribunal proceedings must be accessible
eDiscovery — legal proceedings may require access to former employee emails and files at any time

Chipmunk addresses all of these requirements. Archived data is stored with full integrity in your own Azure tenant, with a complete audit trail of every archiving action. Data can be exported in standard formats for legal proceedings, regulatory audits, and eDiscovery requests. Because all data resides in your own Azure tenant, data residency requirements are met by design.

The Cost of Getting Departed User Archiving Wrong

The financial risk extends well beyond unnecessary licence costs. Consider these scenarios:

A financial services firm is asked by the FCA to produce all communications from a specific employee over an 18-month period. If that employee left two years ago and their Exchange data was not retained, the firm cannot comply — and faces regulatory consequences that dwarf any licence savings.

A legal dispute arises involving a project managed by a former employee. The opposing party requests all emails and files related to the project. If the data was not archived before the deletion window closed, it cannot be produced — potentially undermining the organisation’s legal position.

An HR team needs to review a former employee’s communications as part of a grievance or tribunal proceeding. If the data was not preserved at departure, the investigation is compromised before it begins.

Chipmunk prevents all of these scenarios by archiving data automatically the moment the departure is detected — before any of these risks have time to materialise.

Frequently Asked Questions About Microsoft 365 Departed User Archiving

Q: What happens to Microsoft 365 data when an employee leaves? A: Microsoft begins deleting departed user data within days of an account being disabled. OneDrive files are retained for 93 days before permanent deletion. Exchange Online mailboxes are typically soft-deleted within 30 days and permanently deleted within 60 days. Teams chat history tied to the user’s OneDrive follows the same 93-day timeline. Without an archiving solution in place this data is permanently lost once the window closes.

Q: How do I archive a departed user’s Microsoft 365 data? A: The most reliable approach is an automated archiving solution like Chipmunk that detects account disablement in Microsoft Entra ID and automatically captures OneDrive, Exchange Online, and Teams data without any manual IT intervention. Manual approaches work but are time consuming, error prone, and do not scale for enterprises with ongoing staff turnover.

Q: Do I need to keep a Microsoft 365 licence active after an employee leaves? A: Not if you archive the data first. Chipmunk archives all OneDrive, Exchange Online, and Teams data before the licence is removed. Once archiving is confirmed complete the licence can be safely removed with no risk of data loss. For enterprises processing hundreds of departures per year, this licence saving alone typically covers the cost of Chipmunk many times over.

Q: Where is archived departed user data stored with Chipmunk? A: Archived data is written directly into your own Azure Blob Storage account in your own Azure tenant. Data is processed through SmiKar’s secure Chipmunk appliance but never stored in SmiKar infrastructure. You retain full ownership and control of all archived data.

Q: How long does it take to archive a departed user’s Microsoft 365 data with Chipmunk? A: Archiving typically completes within hours of the departure being detected, depending on the volume of data in the user’s account. Chipmunk sends a confirmation notification when archiving is complete so your IT team knows when it is safe to remove the licence.

Q: Can we search and access archived departed user data? A: Yes. Chipmunk stores archived data in a structured, searchable format organised by user. Authorised administrators can search across all archived user data, export specific items for legal or compliance purposes, and restore data to another active user or a secure destination. Access is controlled by role-based permissions.

Q: Is Chipmunk compatible with Microsoft Purview eDiscovery? A: Yes. Archived data is stored in your own Azure tenant and can be included in eDiscovery processes. Chipmunk maintains a full audit trail of every archiving action that supports legal hold and eDiscovery requirements.

Q: What is the difference between Chipmunk and Microsoft retention policies for departed users? A: Microsoft retention policies prevent data from being deleted but do not remove the requirement to maintain an active licence and add complexity to your Purview configuration. Chipmunk archives the data automatically, allows you to remove the licence immediately, and stores the data in your own Azure Blob Storage at a fraction of the ongoing licence cost. The two approaches can also be used together.

Automate Microsoft 365 Departed User Archiving with Chipmunk

Chipmunk monitors your Microsoft Entra ID and automatically archives OneDrive, Exchange Online, and Teams data the moment an employee account is disabled. Your IT team receives a confirmation and can remove the licence immediately. No manual work, no deletion risk, no ongoing licence costs.

See how Chipmunk can save you on your Microsoft Licensing Today

See how Chipmunk Works

Mastering the User Off-Boarding Process

by Mark | Sep 16, 2025 | Office 365, SharePoint

How to Protect Your Data When Employees Leave

When someone leaves your organisation — whether they resign, retire, or are let go — it’s easy to think the hard work is over. But the moment an employee’s last day arrives, a new risk window opens. If their access isn’t revoked properly or their data isn’t captured, organisations face security breaches, data loss, compliance issues, and rising costs.

This is why a well-designed user off-boarding process is just as important as onboarding. And it’s where Chipmunk can dramatically simplify and secure your operations.

The Risks of Poor Off-Boarding

Many organisations underestimate how much business knowledge is locked inside user accounts. When those accounts are deleted or licenses are removed without planning, it can create significant problems. Former users may still have access to email, Teams, or shared documents if access isn’t revoked cleanly. Microsoft 365 automatically purges inactive accounts after a short grace period, which can permanently erase critical business records.

This lack of planning also creates compliance risks. Without a record of former employees’ data, you may fail audits or be unable to respond to legal discovery requests. Beyond legal and security issues, poor off-boarding also impacts day-to-day operations. When user accounts disappear, managers lose visibility into projects, conversations, and files, which disrupts workflows and knowledge continuity.

The Best-Practice Off-Boarding Process

A robust off-boarding process should follow a structured sequence to ensure no step is missed. While the exact tasks may vary between organisations, these core stages are widely recognised as best practice:

HR Initiation and Communication. HR formally notifies IT and relevant managers of the employee’s departure, confirms the exit date, and collects any company-owned equipment. This communication triggers the technical off-boarding workflow.
Pre-Exit Access Planning. IT reviews all accounts, licenses, and roles the user holds, including Microsoft 365 services, line-of-business apps, VPN, and administrative privileges. A plan is made to disable these systematically to avoid disruptions.
Data Capture and Archiving. Before the account is disabled, all user data must be preserved — OneDrive, Exchange mailbox, and Teams chats. This protects business knowledge and ensures compliance.
This is where Chipmunk comes in. With a single action, Chipmunk captures and archives the user’s entire digital footprint inside your own Azure tenant, creating a secure and immutable record that remains accessible to authorised teams.
License Recovery and Account Deactivation. Once data is captured, IT can safely disable the account, revoke MFA, remove from groups, and free up Microsoft 365 licenses for reuse. This step immediately reduces costs and closes security gaps.
Content Ownership Reassignment. Shared content such as Teams channels, SharePoint sites, or shared mailboxes should be reassigned to other users or managers to maintain project continuity.
Audit and Compliance Logging. All actions taken should be logged for audit purposes. Chipmunk automatically generates a complete record of the archived data and the actions taken, supporting legal and governance needs.
Retention and Eventual Deletion.Archived user data should be retained according to your organisation’s policy or industry regulations. After the retention period expires, it can be securely deleted to reduce storage costs.

Following these steps ensures every departure is handled consistently, securely, and in full compliance — protecting both your data and your reputation.

User Off-Boarding Checklist

Secure Every Departure — Step by Step

1. HR Initiation

Notify IT and line managers of departure
Confirm final working day
Begin collection of company devices

2. Access Planning

Inventory all user accounts and admin roles
Document MFA status, group memberships, shared mailboxes
Prepare account disablement sequence – Disable User Account

3. Data Capture & Archiving

Chipmunk detects disbled account and starts the archiving process of the users data
Capture user’s OneDrive, Exchange mailbox, and Teams data
Store securely inside your Azure tenant

4. License Recovery & Account Deactivation

Disable sign-ins and revoke MFA
Remove from all security groups
Reclaim Microsoft 365 licenses

5. Content Ownership Reassignment

Reassign Teams channels to managers
Transfer shared mailboxes or delegated access
Ensure project continuity for remaining staff

6. Audit & Compliance Logging

Record every off-boarding action
Capture evidence of data archiving
Maintain logs for governance and legal needs

7. Retention & Eventual Deletion

Apply retention policy for archived data
Schedule secure deletion after policy expiry
Validate removal and update records

Where Most Organisations Struggle

Despite having good intentions, off-boarding is often messy and manual. Different IT staff follow different steps, with little visibility into all the places a user’s data lives. Exporting content from OneDrive or Teams can be clumsy and error-prone, and often ties up IT resources for days.

Because there’s no single repository of archived user data, information gets lost, and managers have no easy way to recover it. This creates a gap between what organisations want — secure, compliant off-boarding — and what they can realistically deliver with limited time and tools.

Introducing Chipmunk: Automated Microsoft 365 Off-Boarding

Chipmunk was built to solve this problem. It automates the most critical and time-consuming part of off-boarding: capturing and preserving departing users’ data. Chipmunk collects OneDrive files, Exchange mailboxes, and Teams chats, automatically.

Once captured, the data is stored securely in your own Azure tenant, under your full control. It’s compliant, and easily searchable by authorised staff such as managers, HR, or legal teams. Chipmunk’s approach frees up costly Microsoft 365 licenses immediately after off-boarding and maintains a full audit trail of every action taken, which is critical for compliance. Most importantly, because Chipmunk operates inside your Azure environment, your data never leaves your control.

How Chipmunk Fits Into Your Off-Boarding Workflow

With Chipmunk in place, the process becomes seamless. HR notifies IT when a user is leaving. IT disables the user account then Chipmunk, which automatically captures all the user’s data across Microsoft 365 — OneDrive, Exchange, and Teams. That content is stored securely in Azure, where it can be searched and retrieved if needed later.

Once the archive is complete, IT receives an email from Chipmunk saying the users data has been archived and can then disable the user’s account, reclaim the licenses, and revoke all access. What previously took days of manual work can now be completed in a fraction of the time, with complete confidence and zero data loss.

Make Off-Boarding a Strength, Not a Weakness

User off-boarding is a critical moment in the employee lifecycle — and often the most neglected. Without a clear process, organisations risk losing valuable knowledge, breaching compliance rules, or leaving security gaps that can be exploited.

With Chipmunk, you can turn off-boarding from a risky manual chore into a fast, secure, and automated process that protects your organisation every time someone leaves.

How Chipmunk Automates the Offboarding Data Step

The most time-consuming and risk-prone part of the offboarding process is capturing departed user data before Microsoft’s deletion clock starts. Done manually this requires IT teams to identify the account, export OneDrive files, export the Exchange mailbox, capture Teams data, verify everything is saved correctly, and only then remove the licence. For an enterprise processing dozens of departures per month this is unsustainable.

Chipmunk automates this entire step. The moment a user account is disabled in Microsoft Entra ID, Chipmunk detects the departure and begins archiving OneDrive, Exchange Online, and Teams data automatically. No manual trigger is required. When archiving is complete your IT team receives a confirmation notification and can immediately remove the Microsoft 365 licence.

Every archive is consistent, complete, and logged with a full audit trail. For enterprises dealing with high volumes of departures or mergers and acquisitions involving large-scale account closures, Chipmunk scales without any additional IT overhead.

Microsoft 365 Offboarding Checklist

Use this checklist to ensure every departure is handled consistently and completely.

HR notifies IT of the departure date in advance
Identify all Microsoft 365 services the user has access to — OneDrive, Exchange, Teams, SharePoint sites, shared mailboxes
Archive OneDrive, Exchange Online, and Teams data before or immediately after account disable — Chipmunk does this automatically
Disable the account in Microsoft Entra ID
Revoke all active sessions and MFA devices
Remove the user from all Microsoft 365 groups, Teams, and distribution lists
Reassign shared content — Teams channels, SharePoint sites, shared mailboxes — to a manager or successor
Confirm archiving is complete — Chipmunk sends a confirmation notification
Remove the Microsoft 365 licence
Document the offboarding with a full audit trail for compliance purposes
Set a retention review date for archived data in line with your policy

Frequently Asked Questions About Microsoft 365 User Offboarding

Q: What is the correct order for Microsoft 365 user offboarding? A: Archive the user’s data first, then disable the account, revoke access, reassign shared content, confirm archiving is complete, and finally remove the licence. Removing the licence before archiving is the most common mistake and risks permanent data loss.

Q: How do you offboard a Microsoft 365 user without losing their data? A: Archive their OneDrive, Exchange Online, and Teams data before or immediately after disabling the account. Chipmunk automates this — the moment an account is disabled in Entra ID, Chipmunk captures all three data sources and writes them to your own Azure Blob Storage account.

Q: When should you remove a Microsoft 365 licence after an employee leaves? A: As soon as archiving is confirmed complete. With Chipmunk this can happen the same day the account is disabled — eliminating the weeks or months many enterprises spend keeping licences active while waiting for manual data exports to be completed.

Q: What happens if you delete a Microsoft 365 user without archiving their data? A: Microsoft begins deleting data immediately. OneDrive files are retained for 93 days then permanently deleted. Exchange Online mailboxes are typically deleted within 30 days. Teams data is subject to similar timelines. Once the retention window closes the data cannot be recovered.

Q: How do you handle offboarding when multiple employees leave at once? A: Chipmunk uses queue-based processing to handle spikes in departures without manual intervention. Whether it is one departure or a hundred during a restructure, every account is processed consistently and completely with no additional IT workload.

Q: Does Microsoft 365 offboarding need to comply with GDPR? A: Yes. GDPR requires organisations to have a lawful basis for retaining personal data after employment ends, and to be able to respond to data subject access requests. Chipmunk archives departed user data in a structured, searchable format in your own Azure tenant — satisfying both retention requirements and data subject access obligations.

Chipmunk: Automate Off-Boarding and Cut Costs

Free up Microsoft 365 licenses instantly while keeping all user data safely stored for compliance, audits, and future access.

Ensure no knowledge is lost by automatically capturing and archiving departing employees’ OneDrive, Exchange and Teams content before accounts are removed.

Secure Every Departing User’s Data

Search for Chipmunk in Microsoft Marketplace to get Started.

Stop paying for Microsoft 365 licenses

by Mark | Jul 2, 2025 | Office 365

How to Stop Paying for Microsoft 365 Licenses After an Employee Leaves

When someone leaves your company, the natural step is to disable their Microsoft 365 account. But what many businesses don’t realize is that they often continue paying for that user’s license — just to retain access to their OneDrive files, Teams chats, and emails.

Over time, this adds up to thousands in unnecessary costs.

In this article, we’ll explain:

Why Microsoft 365 makes it difficult to offboard users without data loss
What happens to a user’s data when their license is removed
How to stop paying for ex-employee licenses while retaining access to critical data
A simpler, automated solution using Chipmunk

The Problem: You’re Still Paying for Departed User Licenses

When an employee leaves, their account is typically:

Disabled in Entra ID (formerly Azure Active Directory)
But the Microsoft 365 license remains assigned

Why? Because once the license is removed, Microsoft begins deleting that user’s data.

That means IT teams often keep licenses active just to preserve data — even if that data may never be used again.

If you’re paying $30/month for each departed user’s license, that’s:

100 users = $3,000/month
100 users = $36,000/year

And this is just to hold onto data that should already be safely archived.

What Happens to Microsoft 365 Data When a License is Removed?

Unless you’ve set up retention policies or manually archived the data, Microsoft will begin deleting user data after a license is removed.

Here’s what typically happens:

Service	Retention After License Removal	Outcome
OneDrive	30 days	Files permanently deleted
Exchange Email	30–60 days	Mailbox content deleted
Teams Chats	Up to 93 days	Chats and message history deleted

If you remove a license and haven’t backed up the data, you could permanently lose important files, emails, or conversations needed for handovers, audits, or legal compliance.

Why This Is a Costly Problem?

Microsoft offers tools like retention policies and inactive mailboxes, but they are:

Difficult to configure correctly
Don’t cover everything (Teams chat is a common gap)
Often still require the license to remain in place

This means many organizations choose to keep paying for the license instead of risking data loss.

Over time, this becomes a hidden cost — one that can run into tens or hundreds of thousands of dollars per year, depending on your organization size and turnover rate.

The Right Way to Handle Offboarding: Archive Then Delete

The best solution is simple:

Archive all of the user’s data when they leave, then safely remove their license.

That means:

Downloading and saving their OneDrive data
Exporting all Exchange emails
Capturing Teams conversations
Storing the data securely for future reference

Doing this manually is time-consuming and error-prone. It also requires different tools for each data type, making it difficult to maintain consistency or ensure compliance.

Introducing Chipmunk: Automated Offboarding for Microsoft 365

Chipmunk is a purpose-built solution to solve this problem.

It automates the entire offboarding process by:

Detecting when a Microsoft 365 user is disabled in Entra ID
Automatically backing up their:
- OneDrive files (with full folder structure)
- Exchange emails (saved in .eml format)
- Microsoft Teams messages (including private chats and attachments)
Uploading the data to your own Azure Blob Storage
Logging every action for full auditability

Once Chipmunk completes the archive, you can safely remove the license — no risk of data loss, no ongoing Microsoft billing.

How It Works (Step by Step)

A user is disabled in Microsoft Entra ID
Chipmunk automatically detects the change
It backs up OneDrive, Email, and Teams data
The archive is securely stored in your Azure Blob Storage
You delete the Microsoft license with confidence that nothing has been lost

No scripts. No retention policies. No risk.

Built for Compliance and Peace of Mind

Chipmunk helps your organization meet data retention and compliance requirements across multiple regulatory frameworks, including:

ISO 27001
GDPR
HIPAA
SEC 17a-4
Microsoft Purview compatibility

By automatically archiving all content from disabled Microsoft 365 users and storing it securely in your own Azure tenant, Chipmunk ensures your data is fully retained, auditable, and under your control — without reliance on ongoing Microsoft licensing or complex configurations.

Summary: Don’t Let Data Loss or Licensing Waste Sneak Up on You

Without Chipmunk	With Chipmunk
Continue paying $30+/user/month	Remove license immediately after archiving
Manual exports or retention policies	Fully automated archiving
Data gaps in Teams, OneDrive, Exchange	All covered automatically
Compliance risk, audit blind spots	Secure, logged, and audit-ready archives

What Chipmunk Does That Manual Offboarding Cannot

Manual offboarding requires IT teams to identify departed users, download their OneDrive files, export their Exchange mailbox, capture their Teams data, verify everything has been saved correctly, and only then remove the licence. For enterprises processing dozens or hundreds of departures per year this is time consuming, error prone, and inconsistent.

Chipmunk replaces this entire process with a single automated workflow. The moment a user account is disabled in Microsoft Entra ID, Chipmunk detects the departure event and begins archiving their OneDrive, Exchange Online mailbox, and Teams data automatically. When archiving is complete your IT team receives a confirmation notification and can immediately remove the Microsoft 365 licence — with complete confidence that nothing has been lost.

For large enterprises processing high volumes of departures, Chipmunk scales without any additional IT effort. Every departure is handled consistently, every archive is complete, and every licence removal is safe.

The Cost of Delayed Licence Removal

For a 1,000 person enterprise with 10% annual staff turnover, that is 100 departures per year. If each departed user’s licence is kept active for an average of three months while IT manually handles offboarding, the unnecessary licence cost for a Microsoft 365 E3 plan is over $10,000 per year — just from the delay.

Chipmunk reduces that delay from weeks to hours. The archiving completes automatically and IT is notified to remove the licence the same day the account is disabled.

Ready to Save on Microsoft 365 Licensing?

If your organization is still paying for ex-employee licenses just to preserve their data — it’s time to stop.

Chipmunk gives you a fully automated, secure, and cost-effective way to archive departed user data across OneDrive, Teams, and Exchange — and safely delete the license.

Frequently Asked Questions About Microsoft 365 Licence Removal

Q: What happens to OneDrive data when a Microsoft 365 licence is removed? A: Microsoft retains OneDrive data for 93 days after an account is disabled. After that it is permanently deleted. If the licence is removed before that period ends and no retention policy is in place, the data may be deleted sooner. Chipmunk archives all OneDrive data before the licence is removed so nothing is at risk.

Q: Can I remove a Microsoft 365 licence without losing the employee’s emails? A: Yes, if you archive the Exchange Online mailbox first. Chipmunk automatically captures the full Exchange Online mailbox including sent items, calendar, and contacts before the licence is removed, so all email history is preserved in your own Azure Blob Storage.

Q: How long do I need to keep a departed employee’s Microsoft 365 data? A: This depends on your regulatory obligations and internal policy. GDPR requires data to be kept only as long as necessary. Financial services regulations may require seven years for certain communications. Employment law varies by jurisdiction. Chipmunk stores archived data for as long as your policy requires at a fraction of the cost of keeping an active Microsoft 365 licence.

Q: What happens to Microsoft Teams data when an employee leaves? A: Teams channels the departed user participated in continue to exist for other team members. However, the departed user’s personal Teams chats and any files they uploaded to their own OneDrive are at risk once their account is disabled. Chipmunk captures Teams chat history and associated files as part of the automated archiving workflow.

Q: Is there a way to automatically archive departed user data without manual IT work? A: Yes. Chipmunk monitors your Microsoft Entra ID continuously and automatically starts the archiving workflow the moment a user account is disabled. OneDrive, Exchange Online, and Teams data are all captured without any manual trigger from your IT team. You receive a confirmation notification when archiving is complete and the licence can be safely removed.

Q: How much does it cost to keep a Microsoft 365 licence just to retain data? A: Microsoft 365 E3 costs $36 per user per month. For 100 departed users kept on licence for three months while IT handles manual offboarding, that is $10,800 in unnecessary licence costs. Chipmunk archives the data automatically so licences can be removed the same day the account is disabled.

Departed M365 Users

by Mark | Jul 1, 2025 | Office 365, Onedrive, Risk

Microsoft’s Countdown to Data Deletion

When someone leaves your organization, the first step IT usually takes is to disable their Microsoft 365 account. But have you ever stopped to ask:

“What happens to all their data — their files, emails, and chats — after that?”

The answer might surprise you.

If you’re not actively managing this, Microsoft will automatically delete that data — often in as little as 30 days.

This post explains exactly what gets deleted (and when), why this is a problem, and what you can do to protect that data — without paying for unnecessary licenses.

Microsoft’s Countdown to Data Deletion

Let’s start with a simple truth:

Disabling a user in Microsoft 365 doesn’t save their data forever.

Instead, Microsoft starts a ticking clock. Unless you take action, data begins disappearing — fast.

Here’s what typically happens:

Service	Default Retention	What’s Deleted	Can You Recover It?
OneDrive	30 days	All files and folders	Maybe, but not always
Exchange	30–60 days	Mailbox content	Sometimes
Teams Chat	Up to 93 days	All chat history and attachments	Usually not

So if an employee leaves on January 1st, by April their Teams messages, OneDrive files, and mailbox may be completely gone.

Why This Matters — And Who Should Care

Most people assume Microsoft keeps this data for legal or security reasons. But that’s not how it works.

Microsoft isn’t your backup provider. Its job is to deliver service, not long-term data retention.

This creates big risks for:

IT teams, who might need to retrieve a user’s files later
Legal and compliance officers, who must retain emails and chat records
HR and management, who need access to handover materials, customer comms, etc.

And unless you assign a license to the user’s account forever, that data is eventually lost.

A Real-World Scenario

Let’s say you’re offboarding an employee named Sarah. She’s been with the company for 5 years.

She has:

200 GB of OneDrive files
50,000 emails in Exchange
Years of chats with project teams in Microsoft Teams

You disable her Microsoft 365 account. Now what?

30 days later, her OneDrive starts purging
60 days later, her mailbox may be gone
By day 93, her Teams chat history is unrecoverable

Now legal asks for chat logs from a project she was on 6 months ago… and it’s too late.

Can’t I Just Use Microsoft Retention Policies?

Yes — but it’s not as easy as it sounds.

You’d need to:

Set up custom retention policies in Microsoft Purview
Create inactive mailboxes (which still require licenses)
Use PowerShell scripts to export OneDrive manually
Deal with Teams data that isn’t easily exportable

And even then, you’re not guaranteed to retain everything — especially chat data.

It’s complex, time-consuming, and risky.

The Simpler Option: Use Chipmunk

Chipmunk is a tool built specifically to solve this exact problem.

It watches for when you disable a user and automatically backs up their:

OneDrive files and folder structure
Exchange emails
Teams chats (including private and group chats)

All the data is stored in your own Azure Blob Storage, so:

You own the data
You don’t need to keep paying Microsoft licenses
You can access it anytime — for audits, legal cases, or handovers

No scripts. No licenses. No data loss.

How It Works — In Plain English

Here’s how Chipmunk fits into your offboarding process:

User is disabled in Microsoft Entra ID (formerly Azure AD)
Chipmunk detects it automatically
It downloads all key data — OneDrive, Email, and Teams
It uploads the data into organized folders in your Azure storage
It updates your central dashboard with status and logs
It emails you the results of the archive activity for each user.
You don’t have to remember to do anything. It just works in the background.

Bonus: Save on Microsoft Licenses

Did you know keeping a disabled user’s data often requires a paid Microsoft 365 license?

That could mean paying $20–$40/month per user just to retain inactive data.

With Chipmunk, you can archive it once — and delete the user safely.

For companies with hundreds of staff turnover each year, that’s tens of thousands in savings.

Compliant. Secure. Yours.

Chipmunk is built for:

Data compliance (GDPR, ISO, HIPAA-ready)
Cost reduction (free up licenses without losing data)
IT simplicity (no need to learn Microsoft Purview or eDiscovery)

And because all archived data is stored in your own Azure tenant, you stay in control at all times.

TL;DR

What Happens by Default	What Chipmunk Does
Microsoft deletes data after 30–93 days	Chipmunk backs it up automatically
You must set complex retention rules	No configuration needed
Teams chat is hard to retain	Chipmunk grabs it for you
Ongoing license may be required	Chipmunk lets you delete users safely
Risk of permanent data loss	Permanent backup in Azure

Ready to Never Lose Ex-Employee Data Again?

Don’t wait for day 93.

If you want peace of mind, predictable offboarding, and full control of your M365 user data — Chipmunk can help.

The Four Options Enterprises Have — and Which One Actually Works

When an employee leaves, most organisations fall into one of four approaches to handling their Microsoft 365 data.

Option 1 — Keep the licence active

Keeping the Microsoft 365 licence active after the employee leaves preserves all their data indefinitely. The problem is cost. At $36 per user per month for Microsoft 365 E3, retaining 100 departed users on active licences costs $43,200 per year — for accounts that nobody is using.

Option 2 — Apply a Microsoft retention policy

Microsoft Purview retention policies can prevent data from being deleted after an account is disabled. This avoids the immediate deletion risk but still requires careful configuration, adds to your Microsoft Purview complexity, and does not necessarily allow you to remove the licence.

Option 3 — Manually export and save the data

IT teams can manually export OneDrive files, Exchange mailboxes, and Teams data before an account is disabled. The problem is scale and consistency. For enterprises processing dozens of departures per year, manual export is time consuming, error prone, and relies on IT remembering to do it before the account is disabled.

Option 4 — Automated archiving with Chipmunk

Chipmunk monitors your Microsoft Entra ID continuously. The moment an account is disabled, Chipmunk automatically captures OneDrive, Exchange Online, and Teams data and writes it to your own Azure Blob Storage account. Your IT team receives a confirmation notification and can remove the licence immediately. No manual work, no risk of data loss, no ongoing licence costs.

Why Getting This Wrong Is More Expensive Than It Looks

The financial risk of unmanaged departed user data goes beyond the licence cost. Consider these scenarios:

A former employee was the only person who worked on a key client contract. Six months after they left, a dispute arises and legal needs the email correspondence. If the data was not archived before the 30 day deletion window closed, it is gone permanently.

A financial services organisation is audited and asked to produce all communications from a specific employee over a two year period. If those Exchange mailboxes were not retained after the employee left, the organisation cannot comply — and faces regulatory consequences.

An HR team needs to review a former employee’s files as part of a tribunal proceeding. If OneDrive data was deleted after the 93 day window, the files cannot be recovered.

Chipmunk prevents all three scenarios by archiving data automatically the moment the departure is detected — before any of these risks materialise.

Frequently Asked Questions About Departed Microsoft 365 Users

Q: How long does Microsoft keep OneDrive data after an employee leaves? A: Microsoft retains OneDrive data for 93 days after an account is disabled before permanently deleting it. During this period an administrator can restore the data. After 93 days it cannot be recovered.

Q: What happens to Exchange Online emails when an employee leaves? A: If no licence or retention policy is in place, the Exchange Online mailbox is typically deleted 30 days after the account is disabled. The mailbox can be converted to a shared mailbox to retain it without a licence, but this still requires manual action and management.

Q: What happens to Microsoft Teams data when an employee leaves? A: Teams channels the departed user participated in remain accessible to other team members. However, private chats and files stored in the departed user’s personal OneDrive are subject to the standard deletion timelines. Chipmunk captures Teams chat history and associated files as part of the automated archiving workflow.

Q: Can I recover Microsoft 365 data after the deletion window closes? A: No. Once Microsoft’s retention window closes and data is permanently deleted, it cannot be recovered. This is why it is critical to archive departed user data before disabling the account or as soon as possible after.

Q: Do I need to keep a Microsoft 365 licence active to retain a departed employee’s data? A: No — if you archive the data first. Chipmunk archives OneDrive, Exchange Online, and Teams data to your own Azure Blob Storage account before the licence is removed. Once archiving is confirmed complete the licence can be safely removed with no risk of data loss.

Q: What is the cheapest way to retain departed employee data long term? A: Archiving to Azure Blob Storage is significantly cheaper than maintaining active Microsoft 365 licences. Azure Blob Cool tier costs approximately $0.01 per GB per month. For a departed employee with 10 GB of data across OneDrive, Exchange, and Teams, the annual retention cost in Azure Blob Storage is approximately $1.20 — compared to $432 per year for a Microsoft 365 E3 licence.

Microsoft 365 Backup

by Mark | Mar 27, 2025 | Microsoft Teams, Office 365, Onedrive, SharePoint

Understanding Microsoft 365’s Native Data Protection

Protecting your organization’s data within Microsoft 365 is crucial to ensure business continuity, compliance, and resilience against threats like accidental deletions, cyberattacks, and data corruption. Implementing a comprehensive backup strategy safeguards your critical information and facilitates rapid recovery when needed.

Microsoft 365 offers built-in data protection features designed to maintain high availability and disaster recovery:

High Availability and Disaster Recovery (HADR): Microsoft 365 services are architected for resilience, with replicated data copies to ensure seamless failover during service disruptions.

Data Retention Policies: Tools like Microsoft Purview provide long-term retention capabilities, ensuring critical data remains preserved and compliant with organizational policies.

Versioning and Recycle Bin: Features such as file versioning and a two-stage recycle bin allow users to recover previous versions or deleted items within specific timeframes.

While these features offer a foundational level of data protection, they may not fully address all recovery scenarios, particularly those involving extensive data loss or corruption.

Why Implement Additional Backup Solutions?

Relying solely on native Microsoft 365 protections might leave gaps in your data recovery strategy. Consider the following scenarios:

Accidental or Malicious Deletions: Users might inadvertently delete important emails or documents, or malicious actors could remove critical data. Once retention periods expire, recovery becomes challenging.

Cybersecurity Threats: Ransomware attacks can encrypt or corrupt data, necessitating restoration from clean backups to resume normal operations.

Regulatory Compliance: Certain industries require data to be stored for extended periods or in specific formats, which may exceed Microsoft 365’s native retention capabilities.

To address these challenges, integrating a dedicated backup solution ensures comprehensive data protection and swift recovery options.

Best Practices for Microsoft 365 Backup

Assess Business Requirements and Risks: Identify which Microsoft 365 data—such as emails, documents, and calendars—are critical to your operations and determine the potential impact of data loss.

Select an Appropriate Backup Solution: Consider utilizing Microsoft’s own backup offerings or reputable third-party solutions that integrate seamlessly with Microsoft 365. These solutions should provide features like granular recovery, automated backups, and compliance support.

Define Backup Frequency and Retention Policies: Establish how often backups should occur and the duration for retaining backup data, aligning with your organization’s data recovery objectives and compliance requirements.

Implement Security Measures: Ensure backup data is encrypted both in transit and at rest to protect against unauthorized access. Utilize features like multi-factor authentication (MFA) and role-based access controls to enhance security.

Regularly Test Backup and Restore Processes: Conduct periodic tests to verify the integrity of backups and the effectiveness of restoration procedures. This practice helps identify and address potential issues before a real data loss event occurs.

Monitor and Audit Backup Activities: Implement monitoring tools to oversee backup operations and generate alerts for failures or unusual activities. Regular audits ensure compliance with internal policies and external regulations.

Educate Employees: Train staff on data protection policies and the importance of backups. Awareness reduces the risk of accidental deletions and encourages adherence to best practices.

Conclusion

Implementing a robust backup strategy for Microsoft 365 is essential to protect your organization’s data assets. By understanding the limitations of native protections and adopting comprehensive backup solutions, you can safeguard against data loss, ensure regulatory compliance, and maintain business continuity.

2025 OneDrive Licensing Changes

by Mark | Mar 20, 2025 | Office 365

Navigating Recent Microsoft OneDrive Licensing Changes

Microsoft recently announced significant changes to its OneDrive licensing and storage policies, affecting organizations that heavily rely on cloud storage solutions. Starting January 27, 2025, unlicensed OneDrive accounts—those without assigned user licenses—will be automatically archived after 93 days, rendering them inaccessible unless covered by retention policies or legal holds.

Key Takeaways

Change	Impact on Businesses	Recommended Action
Automatic archiving after 93 days	Risk of losing access to important data	Assign licenses timely; audit accounts regularly
Reactivation and storage fees	Unexpected operational costs	Set up billing proactively
Retention policies and legal holds	Essential for compliance and access	Verify and update policies regularly
Admin notifications and reporting	Increased administrative oversight	Utilize Microsoft 365 Message Center reports

What’s Changing for OneDrive Licensing?

Here’s a detailed breakdown of the changes:

Archiving of Unlicensed Accounts: After 93 days, unlicensed OneDrive accounts will be automatically archived.
Inaccessibility: Archived accounts become inaccessible to both users and administrators, except when protected by retention policies or legal holds.
Retention Policies and Legal Holds: Content under these policies remains accessible via specific mechanisms, despite archiving.
New Fees: Reactivating archived accounts incurs fees ($0.60 per GB), as does storing archived accounts ($0.05 per GB per month).
OneDrive Sync Warning: Users without assigned licenses will see warnings, and accounts will initially enter read-only mode prior to archiving.

Microsoft cites safety and security concerns as the motivation, highlighting risks such as security vulnerabilities, compliance issues, and file duplication associated with unmanaged accounts.

Impacts on Businesses

These licensing changes can significantly affect businesses by:

Increased Operational Complexity: Organizations must proactively monitor account statuses and manage licenses to prevent unexpected charges.
Escalating Costs: Reactivation fees and ongoing storage costs for archived data could rapidly escalate organizational expenses.
Heightened Compliance Risks: Premature archiving of data could lead to inadvertent violations of regulatory compliance.
Operational Disruptions: Loss of access to important data from archived accounts could disrupt workflows and business continuity.

Preparation is Key

Organizations can mitigate these impacts by:

Regularly auditing unlicensed accounts.
Promptly assigning licenses or removing unnecessary accounts.
Configuring Microsoft 365 Archive billing proactively to manage and predict costs effectively.

Enter Chipmunk

Automated OneDrive Data Protection

To address these challenges proactively, we’ve developed Chipmunk, our innovative solution designed to help organizations navigate these licensing changes seamlessly. Chipmunk automatically monitors Microsoft Entra ID (formerly Azure AD) and initiates backups of OneDrive files from disabled or inactive accounts before they become archived, safeguarding your data.

How Chipmunk Helps Your Organization

Automatic Backups: Prevents data loss by securely backing up OneDrive files before Microsoft archives accounts.
Cost Efficiency: Minimizes potential reactivation and storage fees associated with archived data.
Simplified Compliance: Provides straightforward access to backed-up data, ensuring compliance with regulatory and audit requirements.

FAQ

Q: When do these changes take effect?
A: Starting January 27, 2025, and will gradually roll out over a few months.

Q: Will archived accounts be completely inaccessible?
A: Archived accounts are inaccessible unless covered by retention policies or legal holds.

Q: How can I avoid unexpected fees from these changes?
A: Proactively audit accounts, assign licenses timely, and configure Microsoft 365 Archive billing.

Q: Can I reactivate an archived account?
A: Yes, but reactivation will incur fees ($0.60 per GB).

Stay Ahead of the Changes

As Microsoft’s licensing and storage policies evolve, staying ahead is essential. Chipmunk ensures your organization remains protected, compliant, and cost-efficient.

Don’t wait until it’s too late—get proactive with Chipmunk today.

« Older Entries