Controlling settings, permissions, and membership within Teams and channels
There’s no specific known bug in the context that matches this exact behavior, but there are a few supported behaviors and limitations in Teams channels that can explain or work around similar “channel not visible” issues:
- Confirm the channel isn’t just hidden in the new client
- In the desktop client, scroll to the bottom of the channel list and select See all your teams and channels.
- Locate the affected team, then select See all channels under that team.
- If the private channel is listed there, select Show next to it so it appears in the main list.
- Check for hidden or archived state at team/channel level
- If all channels in a team are hidden, the team itself can appear hidden. Use See all your teams and channels and ensure the team and channel are shown.
- If the team/channel has been archived or deleted and then restored, behavior in the desktop client can differ from the web client. Verify the channel is active (not archived/deleted) and, if needed, restore it, then re-check visibility in the desktop client.
- Re‑add the channel to the user’s view via “favorites”/pinning
- In the desktop client, find the channel via See all your teams and channels.
- Use More options on the channel and:
- Add it to Favorites (if available), or
- Pin the channel so it appears in the main list.
- Validate app/policy behavior if the section is app‑driven
- If the custom section is provided by an app or tab that interacts with channels, ensure the app is properly added to that specific channel and that any required permissions or policies are in place. For shared/private channels, apps must explicitly support those channel types and be added at the channel level.
- Use Teams on the web as a stable workaround
- Since the channel appears correctly in Teams Web, using the web client is a supported workaround while the desktop client behavior persists.
If the issue continues only in the new macOS client after confirming the channel is shown and not hidden/archived, and given that it works in Teams Web, the next step is to escalate via Microsoft support or community channels as a client‑specific rendering issue.
References: