Share via

URGENT: Issue with Loop Notes from Previously Scheduled Meeting Invites

JA 0 Reputation points
2026-06-04T16:26:45.03+00:00

Description: We are experiencing an issue with Microsoft Loop notes associated with meeting invites. The problem appears to be isolated to previously scheduled meeting invites.

Current Observations:

  • Issue impacts previously created meeting-invite Loop notes (users receive errors when accessing them)
  • New Loop notes from meetings created starting today (June 4, 2026) forward appear to function correctly
  • Loop Workspaces and chat-created Loop pages are working as expected
  • Attempting to create a Loop note from a previously scheduled meeting invite also results in an error

Impact: Users are unable to access or create Loop notes tied to existing meetings scheduled prior to today, which is affecting meeting collaboration and documentation.

Request: Please investigate and escalate this issue urgently, as it is impacting multiple users.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Schedule meetings
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Jay Tr 12,615 Reputation points Microsoft External Staff Moderator
    2026-06-04T17:20:45.01+00:00

    Hi @JA, 

    I hope you are doing well. 

    I appreciate your time trying to reproduce the issue and raising it in a detailed outline. I have tested the behavior in my testing environment and I was not able to recreate the behavior. Since the behavior is impacting multiple users, it appears to require a deeper investigation at the backend level. While I would be happy to assist further, my current scope and resource limitations do not provide access to the internal systems required for this type of troubleshooting.  

    As a next step, I recommend that your IT administrator submit a support ticket through the Microsoft 365 Admin Center. When a support ticket is submitted through the Microsoft 365 Admin Center, the issue is handled directly by a Microsoft technical support engineer, who has access to internal tools and telemetry not available in community forums or standard troubleshooting workflows.   

    A technical support engineer can run diagnostic checks, analyze logs, and compare your tenant’s behavior against known service baselines. If the investigation indicates a potential product defect, service regression, or configuration anomaly, the engineer may escalate the case to the Microsoft 365 engineering team for further analysis. This escalation path allows the issue to be reviewed by the teams responsible for the service design and implementation, ensuring that any underlying problems are addressed appropriately. 

    As community moderators, our role is to provide guidance and general troubleshooting support. Although we do not have access to the administrative tools necessary for backend fixes, we appreciate your understanding of these limitations. We hope the information provided helps point you in the right direction, and please know that we remain available to assist as much as possible within our scope. 

    In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support  

    For guidance on how to request support in the admin center, please refer to: Get support - Microsoft 365 admin.      

    I hope you found this response helpful, and I greatly appreciate it if you could mark it as accepted. Doing so helps others in the community quickly identify relevant guidance and contributes to making the forum a more helpful and collaborative space. 

    Thank you for your kindness and for your continued contributions to the forum. 

    If you have extra questions about this answer, please click "Comment". 

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.     

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-06-04T16:27:20.9733333+00:00

    Based on the provided information, this behavior matches a service-side or client-side regression affecting Loop components tied to meetings, while other Loop experiences (Loop workspaces, chat-created Loop pages, and newly created meeting Loop notes) continue to work.

    From the available context, the closest comparable issues are:

    • Outlook desktop crashes when sending a meeting invite that includes a Loop component, fixed in later builds.
    • Admin policy interactions that control where and how Loop components for meetings are created and stored.

    Use the following steps to troubleshoot and prepare for escalation:

    1. Confirm affected creation paths and storage
      • For Teams meetings and Outlook invites, Loop components are stored based on the creation path and admin policies:
        • Teams channel meetings (New Calendar): Loop components are stored in the associated SharePoint site under the Meetings folder when the cloud policy Create and view Loop files in Microsoft apps that support Loop or Create and view Loop files in Outlook is enabled.
        • Teams private meetings (classic calendar or in-meeting experience): Loop components are stored in the organizer’s OneDrive Meetings folder when Set-SPOTenant -IsLoopEnabled $true is configured.
        • Teams private meetings (New Calendar) and Outlook meeting invites: Loop components are stored in the organizer’s OneDrive Meetings or Attachments folder, depending on the path, when the relevant cloud policies are enabled.
      • Verify that these storage locations (SharePoint site and OneDrive) are accessible and that no recent changes (permissions, retention, or blocking of specific folders) were applied specifically to content created before June 4, 2026.
    2. Verify Loop admin policies have not changed
      • Check the following cloud policies for the affected users:
        • Create Loop workspaces in Loop
        • Create and view Loop files in Microsoft apps that support Loop
        • Create and view Loop files in Outlook
      • Ensure they are not set to Disabled for the users experiencing issues. When all Loop creations are disabled, users cannot create new Loop files, but existing Loop content remains accessible. If users cannot access existing meeting Loop notes, confirm that no conditional access or OneDrive restrictions are blocking the underlying storage.
    3. Check for known client issues and update Office/Teams
      • There is a known issue where Outlook crashes when sending a meeting invite that includes a Loop component, which was fixed in later builds (starting with build 16904.10000). Ensure Outlook for Microsoft 365 clients are updated to a build that includes the fix, especially for users who created or access Loop notes via Outlook.
      • If users are on older builds, update them to the latest Current Channel or applicable channel build as per the Office update history.
    4. Network and endpoint checks
      • From similar Loop issues, ensure that required Loop and Microsoft 365 endpoints are not blocked. In one reported case, blocking substrate.office.com prevented Loop from working at all. Confirm that this and other Microsoft 365 collaboration endpoints are allowed from affected clients.
    5. Scope and pattern validation
      • Confirm whether the issue is:
        • Tenant-wide or limited to specific users/groups.
        • Limited to a specific client (e.g., Outlook desktop vs. Teams vs. web).
        • Reproducible only for meetings created before a specific date (as described) and not for those created after.
      • Document examples of:
        • Affected meetings (organizer, date, client used to create the meeting, and whether the Loop note was created originally in Teams or Outlook).
        • Error messages/screenshots when accessing or creating Loop notes for those meetings.
    6. Prepare for escalation to Microsoft support
      • Since this is impacting multiple users and appears to be time-bound (older meetings vs. new ones), collect the following before opening a support case:
        • Tenant ID and affected user UPNs (sanitized in any shared documentation).
        • Example meeting IDs/Join URLs and timestamps.
        • Client versions (Teams, Outlook, Microsoft 365 Apps) for affected users.
        • Confirmation of current Loop admin policy settings and any recent changes.
        • Confirmation that storage locations (SharePoint sites/OneDrive) are accessible and not subject to recent permission or retention changes.
      • Open a support ticket through the Microsoft 365 admin center and provide the above details so the issue can be investigated and escalated as a potential service regression affecting legacy meeting-associated Loop notes.

    Until a fix is confirmed, advise users to:

    • Use Loop workspaces or chat-created Loop pages as a workaround for meeting collaboration.
    • For critical meetings, create new meeting invites (where feasible) and attach new Loop components, which are currently working as observed.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.