Forum Discussion
Bug? Teams thread permalink does not show the full thread history (Desktop + Web)
Hi everyone,
I believe I've found a bug in the new Teams threaded channel experience and I'm trying to determine whether others can reproduce it.
Scenario
I have a long-running thread in a Teams channel.
If I open the thread directly from the channel by clicking the reply count (e.g."340 replies"), I can see the complete conversation, including the most recent replies.
However, if I:
- Open the thread
- Use Copy link
- Open the generated link
Teams opens the thread, but only displays part of the conversation. Newer replies are missing even though they exist and are visible when opening the same thread directly from the channel.
Note:
I cannot share the permalink publicly because it points to content within my organisation. However, the link was generated by Teams itself using the thread's Copy link action. The issue is reproducible with any user who has access to the thread.
What I've tested
- Teams Desktop
- Teams Web
- Same behaviour in both clients
- Opening via the channel reply count shows all recent replies
- Opening via the permalink shows only a partial thread
Expected behaviour
A thread permalink generated by Teams should open the same live thread view as clicking the reply count from within the channel. The full conversation history should be available and the latest replies should be visible.
Ideally:
- The full thread history should be available.
- The latest replies should be visible.
- The link should open the current state of the thread, not an apparently truncated version.
Actual behaviour
The permalink opens the correct thread but appears to stop at an older point in the conversation, while newer replies remain accessible only when opening the thread from the channel itself.
Has anybody else seen this behaviour with threaded channels?
Screenshot 1 and 2: Correct behaviour
- Open thread via "340 replies"
- Show:
- Thread title
- Reply count (e.g. 340 replies)
- One or two recent messages (July 2026)
Screenshot 3: Incorrect behaviour
- Open the same thread via the permalink
- Show:
- Same thread title
- Same thread
- Conversation stopping much earlier
- Missing recent replies
3 Replies
I can no longer reproduce the original issue where the permalink appeared to truncate the thread.
However, I still observe a navigation inconsistency:
- Opening the thread from the channel (e.g. by clicking "340 replies") displays the most recent replies immediately.
- Opening the permalink generated by Teams opens the same thread, but positions me at the root message / beginning of the thread.
- To reach the latest activity I need to manually scroll through the entire thread.
Is there currently a way to generate a thread link that opens at the latest reply (or restores the last read position), similar to the behaviour of opening the thread from the channel or from the "Followed threads" view?
If not, I'd consider this a product improvement request.
I've just experienced this exact same issue on Ms Teams for Macos. Version 26183.1901.4874.5228. Restarted Teams just in case but it keeps doing the same. When I follow the link to the first message of a thread, it only shows 13 messages while it actually has 59 replies.
The screenshots make the difference clear: the 340-reply thread reaches the July 22 message when opened from the channel, while the Teams-generated permalink stops at an older message in both desktop and web. That points to a reproducible thread-navigation issue rather than permissions, because the same users can see the missing replies through the channel path.
Ask an admin to check Microsoft 365 Service health for a Teams advisory and use Report an issue if none matches. Reproduce once more, record the exact UTC time, then collect Teams support files with Ctrl+Alt+Shift+1. In Teams, choose Settings and more > Feedback > Report a problem and attach the screenshots. Include the permalink, tenant, team, channel, thread/message identifiers, affected users, and Teams versions. If no advisory appears, the admin should open Support > New service request. Meanwhile, use the channel reply count or Go to channel to reach the complete thread.
