Hi @Ramirez, Jesus (Mizuho Americas Consultant),
Thank you for your patience and for sharing the detailed troubleshooting you have already completed.
Since the user has already signed out and back in, cleared the Teams cache, reinstalled the app, and toggled the relevant Chats and channels settings without any change, this looks less likely to be a simple local cache issue. Based on Microsoft’s current documentation, this may be related to the new chat and channels experience in Teams, which can behave differently depending on the client version, layout, and current service rollout.
In the article, it confirms that meeting chats are still part of the Teams chat experience, and that users can customize how chats and channels are displayed. It also confirms that meeting chats can still be accessed from Teams after a meeting.
A few checks are still worth doing to narrow this down further:
- Check the exact Teams version under Settings > About Teams. Different builds can behave differently in the newer chat and channels experience.
- Test the same account in Teams on the web to see whether the Meeting chats filter appears there. If web behaves differently, that points more to a desktop client issue than a tenant-wide setting.
- Check whether the issue affects only this user or also other users in the same tenant. If multiple users see the same behavior, that suggests a broader rollout or service-side behavior rather than something local to this device.
- Confirm whether the missing items are regular meeting chats or channel meeting chats, because channel meeting conversations stay in the channel Posts/Conversations thread rather than behaving like standard personal meeting chats.
As a temporary workaround, the user can still try opening the meeting chat from Calendar or from the meeting entry directly, since meeting chats can still be accessed before, during, and after meetings from the Teams meeting experience.
If the same behavior continues in both desktop and web, or if it affects multiple users, I recommend that the tenant admin opens a support case from the Microsoft 365 admin center so support can check whether this is related to the current Teams experience rollout or an account-side issue.
Since I do not have access to tenant-side configuration or backend diagnostics, that would be the best next step if the issue remains after the comparison tests above.
I hope this helps clarify the direction of troubleshooting. Should you have any further questions, please feel free to let me know.
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.