In-call "Notes" tab and the meeting agenda in Teams calendar not syncing

Question

This is similar to a previous post here: https://learn.microsoft.com/en-us/answers/questions/4413818/why-are-the-in-call-notes-tab-and-the-meeting-agen

There's a couple things wrong (bugs) happening with Notes from a Teams recurring event VS Loop:

1. I've noticed, for a new recurring meeting series, the "Agenda" notes from the calendar instance, did not sync to our Teams call:
2. In the Teams call, I started to take notes, but after the meeting, when I copied the Loop component link, and opened it on the web, it pointed back to the "unsynced" one (above) from the calendar! It also makes a duplicate with the same name, but adds a 2 at the end of it:
   1. 
   
3. The one from the meeting with the actual updated notes, ends up being an isolated Loop note.

There is a bug with syncing recurring meeting notes from the calendar in Teams, as you see.

Reproduce

Based on my experience...

1. Create a recurring meeting
2. Go to an instance of the series, and add Notes via Teams ahead of time
3. Join the call, and open the Notes panel.
4. See that those are not synced with the ones from the calendar that you added ahead of time.
5. Copy the Loop notes in the call, and see that it creates a duplicate.

Expected behavior

Meeting notes generated in Teams Calendar, sync with the Teams call notes, and vice versa. This has to be a bug.

Additional context

• Using macOS app, on macOS 15.6 (24G84)
• Updated to the latest version of Teams version 25212.2404.3875.1360.

Answer 1

Hi @Reony, 

Good day to you! Welcome to Microsoft Q&A forum. 

Thank you for sharing your experience with the recurring Microsoft Teams meeting notes issue. I’m really sorry for the inconvenience this behavior has caused and I truly appreciate the detailed information you’ve provided.

Let me explain why this happens and walk you through some workarounds that may help. 

In Microsoft Teams, each occurrence of a recurring meeting creates its own Loop notes file by default. This behavior leads to: 

• Pre-meeting agendas added in the calendar not appearing in the in-call Notes tab. 
• A new Loop file being created during the meeting (often with a “_2” suffix), while the original agenda remains untouched. 
• Duplicate or outdated notes across meeting instances. 

This is a known behavior caused by how Teams handles Loop components for recurring meetings treating each occurrence as a separate session. 

Work around options: 

1. Use a single notes file for the series (recommended) 

This ensures all meeting occurrences share the same notes file. 

Steps: 

1. Open the Meeting Series 
   In Teams Calendar, right-click the recurring meeting → Edit series (or click “View series” if you opened a single occurrence). 
2. Add Loop Agenda/Notes 
   Scroll to the bottom of the series details. 
   Click the Loop icon (or “Add agenda/notes”) to insert a Loop component. 
3. Share with Participants 
   Click Share on the Loop component. 
   Set permissions to “People in your organization with the link can edit”. 
4. Save and Use in Meetings 
   Save the updated series invite. 
   When each meeting starts, open the Notes tab—it will now display the shared Loop notes. 

Benefits: 

• Unified notes across all meetings 
• Pre-meeting agendas and in-meeting notes stay in sync 
• No duplicate or unsynced files 

2. Use separate notes for each occurrence (if preferred) 

If you want distinct notes per meeting or to avoid the bug entirely: 

• Create a Manual Template: 
  Maintain a Loop notes template and copy it into a new Loop page for each meeting. 
• Use OneNote or Wiki: 
  OneNote allows structured note-taking with a section for the series and a page per meeting. 
  It avoids the Loop sync bug and supports persistent access. 

Benefits: 

• Clean slate for each meeting 
• No risk of old content reappearing 

Drawbacks: 

• More manual effort 
• Pre-meeting notes won’t auto-appear in the in-call Notes tab 

3. Verify permissions and access 

Loop components are stored in the organizer’s OneDrive. 
Attendees joining via forwarded invites or external accounts may not have access. 

Solution: 

• Open the Loop file 
• Click Share and grant access to individuals or the entire organization 

4. Keep teams updated 

This behavior is on Microsoft’s backend, but keeping your Teams app updated ensures you benefit from any future fixes. 

• Using a single Loop notes file for the entire series keeps all notes unified and synced across meetings. It’s ideal for maintaining a consistent record, but may not suit teams that prefer separate notes per session. Sharing permissions must be managed carefully.
• Using separate notes for each occurrence allows for clean, isolated documentation tailored to each meeting. However, it requires manual setup and pre-meeting notes won’t automatically appear in the in-call Notes tab.
• Switching to tools like OneNote or Wiki offers structured and reliable note-taking that avoids known Loop sync issues. This method is effective but involves moving away from Loop components and adjusting workflows.

If you haven’t already, I also recommend submitting feedback to Microsoft Feedback Hub.  Each submission is reviewed by our product team and helps inform priorities for upcoming updates.  
I hope this message finds you well and if there’s anything else I can help with, just let me know. I’m happy to help.  

Wishing you a great day.