Loop pages not discoverable via @ mention and not sticking to a Teams workspace

Hi @Messersmith, Mike (RC-US SI S&OP VM FED), 

I hope you’re having a great day. Thank you for the detailed write‑up and clear scenario steps; I really appreciate the thorough context you shared. 

Based on your description, what you’re experiencing is most consistent with page discoverability/indexing and client‑side caching behavior, rather than a permissions issue. This is because the pages clearly exist, are accessible via direct links, and share the same permission model within the workspace. 

1/ Is @ mention discoverability affected when pages are created simultaneously? 

Yes, it can be. When multiple Loop pages are created around the same time, they may not all appear immediately in the @ mention picker. Newly created pages can vary require a short period for background indexing to complete before they become fully searchable or mention‑discoverable.  

2/ Is this a known issue with Loop + the new Teams experience, or expected behavior? 

At this time, there isn’t a published service‑health incident that directly maps to “Loop pages missing from the @ picker” or “Master Summary not staying anchored.”. So the behavior is more likely due to background indexing for new Loop content, caching/sync in the new Teams client, and differences in context/recency between Teams and the Loop app.

3/ Recommended pattern to keep “Master Summary” reliably attached and linkable 

For an operational workspace where stable navigation is important, the most reliable pattern is: 

• Pin the “Master Summary” page as a Loop tab in the relevant Teams channel. This provides a durable entry point that isn’t dependent on “recent” or “last opened” behavior. 
• Within “Master Summary,” maintain a small Quick Links / Table of Contents section with direct links to your core pages (Capture Plan & Strategy, Action & Decision Log, Artifacts & Inputs). This ensures consistent navigation when suggestions are incomplete. 
• After creating pages (especially in bulk), you might open each page at least once and optionally make a small edit. This may help the pages become discoverable sooner in search and @ pickers. 

For additional information, you can refer to these articles: 

• Loop Workspaces in Teams Channels - Microsoft Support 
• Overview of Loop components and Loop workspaces permissions | Microsoft Learn 
• Overview of Loop storage | Microsoft Learn 

4/ Contact support 

If the issue persists even after these steps, it may stem from a deeper system-level cause. In this case, I recommend contacting your organization's IT administrator, who can submit a support request to Microsoft through the Microsoft Admin Center. They’ll be able to access system-level information to investigate the issue thoroughly and provide assistance. At the very least, they can offer the most effective workaround to ensure your experience remains smooth and secure.      

As community moderators, we appreciate your understanding that we do not have access to the administrative tools or permissions required to investigate or modify these configurations. We also do not have the capability to initiate remote sessions for direct assistance. Our role is to guide users to the appropriate resources and support channels.  

I hope this information is helpful. Should you have any further questions or need additional assistance, feel free to reach out.   

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".  

Note: Follow the steps in our documentation to enable email notifications if you want to receive email notifications related to this topic.