Microsoft will begin automatically storing AI-generated meeting archives in Teams that persist for five years by default—long after the original transcript is gone. The rollout, estimated for August 2026 under Roadmap ID 558933, forces a deliberate governance choice on every organization: accept a half-decade of AI memory or disable the feature entirely before it becomes the new normal.

What’s Changing

The feature introduces a new .meeting file for eligible Teams meetings. When a Copilot-licensed participant is invited, a transcript is created, and the meeting option “Allow Copilot and Facilitator” is set to “During and after the meeting,” Teams will generate an AI archive. This artifact condenses the meeting’s key insights and metadata into a summary, without storing raw transcript excerpts or user content, according to Microsoft’s documentation.

The file lives in a tenant-owned SharePoint Embedded container—not any user’s OneDrive or a conventional document library—and remains invisible to end users. Copilot, Facilitator, and other Microsoft AI tools use it to answer questions about past meetings, even after the source recording and transcript have been deleted.

Two settings in the Teams Admin Center govern the behavior: a tenant-wide toggle to enable or disable archive generation, and an expiration period that defaults to 1,825 days (five years). An admin can shorten that window or shut off archiving altogether, but the control cannot be scoped to specific users, groups, or departments. Microsoft’s roadmap lists the rollout start as August 2026, with targeted release first, although dates are subject to change.

What It Means for Your Organization

For IT Administrators

This is a record-keeping decision masquerading as an AI feature. The five-year retention is a product default, not a regulatory requirement or a best practice. If your organization has deliberately short retention for transcripts—30 days, 90 days, or similar—you must now ask whether an AI-generated summary that outlasts the raw recording by years aligns with your data-handling obligations.

The archive is durable, tenant-owned, and discoverable through eDiscovery when you have the container URL. Microsoft says retention policies in Purview can target these archives just like SharePoint content, but only if you’ve properly identified the containers. Compliance teams will need to map these new artifacts into existing data lifecycle workflows, understand the deletion process (meeting organizer or PowerShell), and confirm what happens when an organizer’s account is deactivated. Microsoft states the archive survives account deactivation and persists until its expiration date.

For End Users and Meeting Organizers

Employees often assume that when a meeting transcript expires, Copilot forgets the conversation. After this rollout, that assumption may be wrong. Copilot can still reference the AI archive, and its answers will cite the meeting recap or invite. Organizers retain the ability to delete the archive by removing the meeting recap, but many won’t know that. Privacy notices and internal guidance should clarify that AI memory of a meeting has a separate lifecycle.

The .meeting file isn’t a simple duplicate of the transcript. It’s an AI-generated condensation. That raises thorny questions: if a decision or statement captured in the summary is disputed, can you retrieve the original context? Microsoft maintains that no raw user data is stored, but the archive still grounds AI responses about the meeting’s substance. Before treating these files as evidentiary records, validate that your eDiscovery, hold, and export workflows actually work with SharePoint Embedded containers—and that your legal hold notices cover them.

How We Got Here

Microsoft has been steadily expanding Copilot’s memory in Teams. Intelligent recaps, AI-generated notes, and the “Facilitator” agent all build on the idea that AI should be able to reason over meeting context across time. Until now, the transcript retention policy has served as a natural boundary: when the transcript expired, the searchable textual record disappeared, and Copilot’s ability to answer detailed questions about that meeting faded.

Roadmap ID 558933 breaks that bond. The AI archive is designed to persist independently, giving Copilot a durable knowledge base that doesn’t depend on the existence of the raw recording. Microsoft positions this as a boon for project continuity and institutional memory, but it also introduces a records-management gap that many organizations haven’t yet recognized. WindowsForum users have been tracking related concerns for months, noting that Copilot can already produce meeting recaps without retaining the original transcript, and that the compliance implications of AI-derived artifacts are still poorly understood.

What to Do Now

August 2026 may feel distant, but the time to act is before the rollout reaches your tenant. Here’s a practical checklist:

  1. Inventory your meeting lifecycles. Document current retention settings for Teams transcripts, recordings, meeting chat, and recaps. Know why each was chosen.
  2. Identify the rationale behind short retention. Is it regulatory (personal data, sensitive content) or operational (storage, clutter)? The answer dictates whether a five-year AI archive is acceptable.
  3. Make an explicit archive generation decision. In the Teams Admin Center under Meetings > Meeting settings > AI meeting archives, either disable “Generate AI meeting archives” or set a custom expiration period. Do not passively accept 1,825 days.
  4. Document ownership and escalation. Assign responsibility for the policy, user communications, and periodic review. Ensure legal and privacy stakeholders are part of the decision.
  5. Update privacy notices and user guidance. Explain that transcript expiration no longer means AI forgets the meeting. Provide clear instructions on how organizers can delete their meeting recap if that’s an option your policy allows.
  6. Run a controlled validation. Hold test meetings with a licensed Copilot user, verify recap behavior, and practice archive deletion procedures. Treat this as operational validation, not direct file inspection—the .meeting file itself isn’t directly accessible.

Outlook

The AI archives feature is currently in preview for the Teams Technology Adoption Program (TAP) and may still evolve before general availability. Watch for updated documentation on Purview integration, container visibility, and any changes to the tenant-wide scope limitation. Also monitor the Roadmap (ID 558933) for date shifts. Most critically, treat this as a distinct records class from day one: the question isn’t just whether Copilot can remember a meeting, but whether your organization is prepared for exactly what it remembers, and for how long.