Teams Meeting Notes Move to Organizer OneDrive in November 2026

Microsoft is now working to clean up that exact architectural quirk. According to Microsoft 365 Roadmap ID 576194, the company is developing an update for Microsoft Teams that changes where collaborative meeting notes are saved. Specifically, for non-channel Teams meetings, collaborative meeting notes—including both standard Loop-powered meeting notes and AI-generated Facilitator notes—will be stored in the meeting organizer's OneDrive for Business rather than the OneDrive of whichever participant happened to initiate the notes first.

Listed as "In development" for the Desktop platform across Worldwide (Standard Multi-Tenant) cloud instances, the update is slated for Targeted Release and General Availability in November 2026. As Microsoft notes on its AI at Work Roadmap portal, roadmap dates and descriptions represent current commercial estimates and remain subject to change as features move toward deployment.

The Problem With "First Click Owns the File"​

To appreciate why this backend change matters to Windows users and Microsoft 365 administrators, it helps to look at how Teams meeting notes evolved. When Microsoft retired the legacy Teams Wiki and replaced it with modern, Loop-powered collaborative meeting notes, it turned agendas, live notes, and follow-up task lists into .loop files (originally .fluid files in earlier releases).

Under Microsoft's existing behavior, documented across Microsoft Support, Microsoft Learn, and user discussions on Microsoft Q&A and the Microsoft Community Hub, any invited attendee or organizer can start taking notes before or during a meeting. However, for private (non-channel) meetings, the resulting .loop file was created in the OneDrive for Business Meetings folder of the person who first clicked to start the notes—or the user who initiated the Facilitator agent during a scheduled meeting.

In practice, that "first-click ownership" model created several operational headaches:

• Inconsistent File Custody: A project manager could organize and host a twelve-week recurring meeting series, yet the underlying .loop file containing the agendas and action items might reside in the OneDrive of a colleague from another department simply because that colleague opened the Notes pane first.
• Permission Friction: As administrators and users have reported on Microsoft Q&A, when a non-organizer initiates a Loop component ahead of or during a meeting, other participants—and occasionally even the meeting organizer—can run into access prompts if tenant sharing defaults or join order interfere with automatic permission provisioning.
• Offboarding and Lifecycle Traps: According to Microsoft Learn's Loop storage documentation, Loop components stored in a user's OneDrive follow standard OneDrive IT retention and deletion policies when that user leaves the organization. If a temporary contractor or departing team member happened to trigger the meeting notes for a long-running executive sync, their eventual account deletion would start the countdown timer on those meeting notes—even though the actual meeting organizer was still actively running the project.
• eDiscovery and Compliance Hunting: When legal or compliance teams need to run eDiscovery searches on a project manager's meetings, having recordings stored in one place and collaborative notes scattered across the OneDrive accounts of various attendees complicates data collection.

Section Summary: Previously, Loop-powered meeting notes and Facilitator notes in private Teams meetings were saved to the OneDrive of whichever participant initiated them first. Roadmap ID 576194 shifts that storage destination to the meeting organizer's OneDrive for Business, aligning file custody with the person who actually scheduled the meeting.

How Microsoft Teams Loop Storage Works Across the Ecosystem​

Not every Teams meeting or Loop component is affected by this update. Microsoft Learn's documentation on Loop storage and admin configuration makes a sharp distinction between different creation paths across Microsoft 365. Because storage location is determined by where content is originally created, IT pros and power users need to keep the boundaries clear.

As the table illustrates, the non-channel qualifier in Roadmap ID 576194 is critical. Channel meetings are tied to a Microsoft 365 Group, and their collaborative notes are stored inside a Meetings folder on the associated SharePoint site. That group-owned architecture already avoids the single-user OneDrive problem, so channel meetings remain untouched by this roadmap item.

What Changes for End Users (And What Stays the Same)​

From a day-to-day workflow standpoint, Microsoft emphasizes in the roadmap description that this update preserves the existing note-taking and collaboration experience for meeting participants. If you are joining a meeting from the Teams desktop client on Windows, the way you interact with agendas, notes, and action items will look identical.

According to Microsoft Support's guidance on taking meeting notes in Teams, participants will still be able to:

• Collaborate Before the Meeting: Open the Teams calendar, select a scheduled meeting, and populate the agenda, notes, or tasks before the call begins.
• Co-Author Live During the Call: Select Notes (or More actions > Notes) in the meeting controls to co-edit in real time, pop the notes pane out into a separate window for multitasking, and @mention colleagues to assign dated tasks.
• Review and Edit Afterward: Access automatic saves after the call via the Teams calendar details, the Recap > Notes tab, the meeting chat, or through Office.com and the Loop web app.

It is also worth noting what existing platform limitations remain in place. Microsoft Support documentation specifies that people who are not directly invited to a meeting may have limited access to its notes, and external attendees cannot access or edit Teams meeting notes. Nothing in Roadmap ID 576194 indicates any change to external guest access or participant editing rights.

A Word of Caution: Do Not Manually Move .loop Files​

For users and administrators tempted to tidy up their existing OneDrive folders before this update arrives, Microsoft Learn's documentation and Microsoft Q&A troubleshooting threads offer a major warning: do not manually move .loop files to a different library or SharePoint site.

According to Microsoft Learn's overview of Loop components in Teams, moving a .loop file from a user's OneDrive to a SharePoint site—or across different document libraries—causes the interactive Loop component to fail to load inside the Teams chat, meeting recap, or Outlook email where it was originally shared. Furthermore, as documented on Microsoft Q&A, moving a file across libraries in SharePoint or OneDrive creates a new copy at the destination and deletes the original, severing the link between date-based meeting instances and the note file. While moving a .loop file into a different folder within the exact same library continues to work, cross-account or cross-library moves break the component.

What IT Administrators Need to Know​

For Microsoft 365 and SharePoint administrators, this roadmap item is primarily an operational and governance improvement rather than a configuration mandate. Based on general industry knowledge and Microsoft's standard Microsoft 365 service architecture, centralizing non-channel meeting artifacts—such as recordings, transcripts, and now collaborative Loop and Facilitator notes—under the meeting organizer's account simplifies data custody.

Here is how the administrative landscape currently works according to Microsoft Learn, along with the open questions IT teams should watch as November 2026 approaches:

1. Existing Tenant Controls Remain via SharePoint PowerShell and Cloud Policy​

Microsoft Learn documents that Loop functionality in Teams is managed differently depending on the calendar experience:

• For the Teams In-Meeting experience and Teams Classic Calendar, administrators control Loop components and collaborative meeting notes at the tenant level using the SharePoint Online PowerShell module:
• Set-SPOTenant -IsLoopEnabled $true (controls Loop component creation and integration in Teams)
• Set-SPOTenant -IsCollabMeetingNotesFluidEnabled $true (controls collaborative meeting notes in Teams)
• Both of these SharePoint tenant properties apply organization-wide and cannot be scoped to individual users.
• For the Teams New Calendar experience and Outlook, Loop file creation checks Cloud Policy settings configured at config.office.com (specifically Create and view Loop files in Microsoft apps that support Loop and Create and view Loop files in Outlook), which can be scoped to Microsoft 365 Groups, security groups, or dynamic Entra ID groups.

Microsoft has not stated that administrators need to change any of these PowerShell or Cloud Policy settings to receive the organizer-OneDrive storage update.

2. Unanswered Edge Cases to Monitor in the Message Center​

Because Roadmap ID 576194 is currently a brief roadmap entry, Microsoft has not yet published detailed technical documentation covering several edge cases:

• Existing Notes and Recurring Series: The roadmap entry does not specify whether existing meeting notes or active recurring meeting series created prior to the rollout will be migrated, or if the change applies strictly to net-new notes created after deployment.
• Organizers Without a Valid OneDrive: Microsoft Learn states that users must have a valid OneDrive account to create OneDrive-backed Loop components. In environments where meetings are scheduled by shared mailboxes or room/equipment resource accounts that lack an active OneDrive for Business license—a scenario that has already caused Loop access issues according to user reports on Microsoft Q&A —it remains to be seen whether Teams will fall back to the initiator's OneDrive or block note creation.

Section Summary: End users will keep the exact same live co-authoring experience in Teams, while IT administrators gain cleaner data governance without needing to flip new policy switches. Admins should watch the Microsoft 365 Message Center as the November 2026 Targeted Release window approaches for specifics on recurring series and unlicensed resource organizers.

Practical Checklist for Teams Admins and Power Users​

While waiting for Microsoft to push this update to Targeted Release and General Availability in November 2026, organizations can take a few practical steps to avoid meeting-note headaches today:

• Let the Organizer Initialize the Agenda: Until the update rolls out to your tenant, the cleanest way to ensure non-channel meeting notes land in the organizer's OneDrive is for the meeting organizer to click Add an agenda when scheduling the invite from the Teams desktop calendar.
• Use Channel Meetings for Long-Term Team Projects: If a meeting series belongs to a broader department or project rather than a single individual, schedule it as a Teams channel meeting so the .loop notes are stored in the team's SharePoint site Meetings folder rather than any single employee's OneDrive.
• Audit Offboarding Workflows: Remind project managers and HR/IT offboarding teams that collaborative .loop files in OneDrive follow standard OneDrive retention and deletion lifecycles when an employee leaves.
• Keep Hands Off the Underlying Files: Train users to access and share meeting notes through the Teams calendar, Meeting Recap, or the Loop app's built-in share controls rather than dragging and dropping .loop files across OneDrive and SharePoint folders.

Update: Additional details (October 15, 2026)​

Microsoft’s roadmap entry now lists Android, iOS, Mac, and the web alongside Desktop as supported platforms for this change. The planned November 2026 rollout remains in development for both Targeted Release and General Availability in Worldwide standard multi-tenant tenants.

Update: GCC tenants added to planned rollout (October 16, 2026)​

Microsoft’s roadmap entry now lists GCC alongside Worldwide standard multi-tenant tenants for the planned November 2026 deployment. The feature remains in development for Targeted Release and General Availability across Android, desktop, iOS, Mac, and web clients.