Johns Hopkins University is about to permanently delete massive amounts of Microsoft Teams chat history. On October 15, 2026, the institution will flip a switch that automatically removes any chat message older than 90 days—and as a one-time housecleaning, every chat sent before July 17, 2026, will vanish within days. For the thousands of faculty, staff, and students who rely on Teams, it’s a hard reset on how they think about digital conversation.

The New Retention Reality

The policy, announced July 15 via the university’s Hub portal, draws a hard line between fleeting chatter and institutional memory. Once active, any one-on-one, group, or unscheduled meeting chat will disappear 90 days after it’s posted. Meeting recordings and transcripts get a 180-day grace period, but anything older than April 18, 2026, also gets the axe on October 15.

Channels are the safe harbor. Standard and private Teams channels keep their full history, because the university views them as the proper place for official discussions, decisions, and records. The carve‑out is a deliberate nudge: if you need to keep it, put it in a channel.

What Vanishes and What Stays

The deletion scope is narrow but hits the core of day‑to‑day chatter:

  • Wiped: One‑to‑one chats, group chats, and chats attached to unscheduled (ad‑hoc) Teams meetings.
  • Untouched: All Team channels—both standard and private—plus any files shared inside a chat. Those files are automatically saved to OneDrive, so they survive even when the conversation thread does not.

Regulatory holds and legal preservation duties override the automation behind the scenes, so messages subject to litigation or compliance requirements won’t disappear. But for the average user, the rule is simple: treat direct chats as disposable.

Immediate Impact: A Shift in Workflow

For anyone inside Johns Hopkins, this change is more than a housekeeping task. It rewires daily routines. A quick chat about a syllabus, a staff decision, or a research note that once lingered indefinitely will now evaporate unless someone deliberately moves it to a permanent spot.

The policy also reinforces Teams as the only approved standalone messaging app for official business. Zoom chat is permitted during sanctioned meetings, but Slack, Discord, Google Chat, WhatsApp, and Signal are explicitly off‑limits without a formal exception. For students and employees, using an unapproved app for university work now carries extra weight—because nothing in those apps will be retained.

The Backstory: Why Chat History Became Ephemeral

Johns Hopkins isn’t operating in a vacuum. The move aligns with a broader enterprise shift toward intentional data governance. Microsoft 365 has long offered retention policies for Teams that let admins set automatic deletion rules. What’s notable here is the aggressive 90‑day window—shorter than many defaults—and the one‑time bulk purge.

The rationale, as the university explained, is that one‑on‑one and small group chats are “informal, transitional communications” akin to hallway conversations. They typically aren’t official records. By cleaning house, Hopkins aims to cut storage clutter, manage legal risk, and nudge users toward governed repositories like SharePoint and OneDrive.

This isn’t the first institution to impose chat lifecycles—law firms, financial services, and government agencies often set retention to meet compliance—but Hopkins’ size and academic setting make it a high‑profile case that could influence other universities and businesses.

How Retention Works Under the Hood

For IT professionals, the policy likely leverages Microsoft Purview retention policies—a set of controls that apply to specific locations (Teams chats, for example) and can automatically delete items after a defined period. Admins configure these in the Microsoft Purview compliance portal, targeting chat messages by user or group. When the retention period expires, the deletion is permanent; there is no recycle bin.

Microsoft also offers eDiscovery and legal hold capabilities that can override automated deletion when litigation or investigations require data preservation. Johns Hopkins has confirmed such holds will be honored, meaning users under a legal hold won’t see their chats vanish even if they’re older than 90 days.

Before the Deadline: Your Action Plan

The October 15 cutoff isn’t soft. If you’re affiliated with Hopkins, here’s what to do, broken down by role.

All users
- Open Teams and review your personal and group chats. Pin or save anything critical—decisions, project context, informal approvals—before the deletion date.
- Don’t worry about shared files; they’re already in OneDrive. Focus on the text itself.

Faculty
- Copy course agreements, grade discussions, or curriculum decisions from chats into the appropriate Teams channel or a OneDrive document.
- Remember: if it affects students or could be needed for accreditation or disputes, it belongs in a channel.

Staff and administrators
- Audit team workflows that rely on chat history for compliance, records management, or day‑to‑day operations. Transition those processes to dedicated Teams channels or SharePoint libraries.
- Consider creating channels explicitly for “chat‑style” quick updates that must be retained, making the behavior shift easier.

Students
- Chats may hold study notes, group project plans, or informal advisor guidance. Copy anything you’ll want later into a OneDrive doc or a channel you control.

There’s no magic “export my chats” button in the consumer Teams client, but you can copy‑and‑paste text or use the “Share to” function to send a conversation to OneDrive. The original announcement includes links to IT support for anyone stuck.

The Ripple Effect Beyond Baltimore

If you work outside Johns Hopkins, treat this as a prompt to ask your own IT team: What’s our Teams retention policy? Many organizations allow chats to linger indefinitely by default, but that doesn’t guarantee future immunity. A growing number of compliance and legal experts argue that ephemeral digital chatter should be treated as exactly that—ephemeral—to avoid discovery headaches and data sprawl.

Microsoft provides the controls to make this happen, and the Hopkins model demonstrates how a clear, centrally communicated policy—paired with training and an enforced deadline—can realign user behavior without breaking critical workflows. Windows users everywhere should take one simple lesson: never assume a chat message is permanent. Whether your organization follows suit or you’re just managing your own Microsoft account, treat Teams chat as a conversational medium, not a filing cabinet.