# Teams onboarding workflow: new staff in the right channels

> Teams onboarding workflow (MC1518033) adds new members to the right channels. What it does, what it may not cover, and what team owners can set up today.

[( Insights)](https://tenantcraft.ca/insights)

## Teams onboarding workflow: route new staff to the right channels

A new hire joins the team and sees one channel. The ones they need are hidden behind See all channels, or locked in private channels nobody added them to. Microsoft's onboarding workflow (MC1518033) lets team owners add new members to channels automatically. Here is what to set up before it lands in December.

Stage

Plan

Topic

General

Published

Oct 30, 2026

Written by

[Geri Crroj](https://tenantcraft.ca/about)

Tested in a live tenant, October 30, 2026

(Short version)

Pick three to five channels every new member needs and recommend them for everyone today. When the onboarding workflow reaches your tenant in December 2026, team owners can add new members to those channels automatically. Private channels still need their own owner to add people, so list who owns each one.

A new coordinator starts on Monday. IT adds her to the Operations team before she arrives. She opens Teams, finds Operations, and sees one channel: **General**.

The channel where shifts get swapped is there too. So is the one with the safety forms, and the one where her manager posts the weekly plan. She can’t see any of them in her list. They sit behind **See all channels**, and nobody told her to look.

By Thursday she has asked three people where the forms are. Each of them answered in a chat, so the next new hire will ask again.

I’ve often wished for one workflow: add a new person to a group, and they land in every Teams channel they need. So I went looking at what Teams can do today, and what’s coming.

The 5-minute version

1.  **Adding someone to a team isn’t onboarding them.** Microsoft says Teams shows a team’s first channel automatically. The rest wait behind **See all channels**.
2.  **A fix is coming.** Message center post MC1518033 says team owners will be able to add new members to channels automatically when they join a team.
3.  **General availability is December 2026.** It starts in early December and should finish by mid-December. No admin action is required.
4.  **You can start today.** Team owners can mark up to 10 standard channels **Recommend for everyone**. New members see them tagged as recommended.
5.  **Private channels are a separate job.** Only the private channel’s own owner can add people. A team owner can’t.

## Why new staff land in the wrong place

The usual diagnosis is “the new hire didn’t look around.” The real cause is how Teams shows channels.

Joining a team and seeing its channels are two different things. Microsoft’s help page on choosing channels says, “Microsoft Teams automatically shows a team’s first channel on your channel list.” Everything else is the member’s choice. Teams sends a notification when someone first joins, offering to pick channels. If they skip it, every other channel stays behind **See all channels** until they go looking.

For someone who has used the team for a year, that’s fine. They’ve already shown the channels they need. For someone on day one, it means the team looks empty apart from **General**.

Private channels are harder still. Microsoft’s private channel docs say, “Team members can only see private channels that they’re added to.” A new member can’t find a private channel at all, because for them it doesn’t exist yet.

## What the onboarding workflow changes

Microsoft announced the change in Message center post **MC1518033**, “Microsoft Teams: Onboarding workflow for new team members,” roadmap ID **573452**.

![Microsoft 365 admin center Message center post titled Microsoft Teams: Onboarding workflow for new team members, message ID MC1518033, roadmap ID 573452, published October 20, 2026, with rollout dates and a note that no admin action is required.](https://tenantcraft.ca/images/to-01-mc1518033.png)

Message center > MC1518033

The announcement. Team owners set it up, not admins, which is why owners need to hear about it before December.

The post describes today’s problem plainly: “new team members may need to manually discover and join the channels that are most relevant to their work.” The fix is that “team owners can automatically add new members to relevant channels through the onboarding workflow when they are added to a team.”

Here are the dates from the post:

-   **Targeted Release:** early November 2026, finishing in early November.
-   **General Availability:** starting in early December 2026, finishing by mid-December.
-   **Platforms:** Android, Desktop, iOS and Mac.

The platform list doesn’t include Teams on the web. If your staff work mostly in a browser, test there once it arrives before you promise anything.

The admin note is short: “No admin action is required. You may want to inform team owners about this upcoming improvement.” Telling owners is the right call, but they’ll need more than a heads-up to set it up well.

## What Microsoft hasn’t said yet

The Message center post doesn’t describe the setup screen, where the setting lives, or which channel types it covers. The feature hasn’t reached my tenant yet, so I can’t show you the click path. Don’t write training material around a menu you haven’t seen.

One question matters most: **private channels**. Today, Microsoft’s own table of private channel actions says a team owner can’t add members to a private channel. Only the private channel owner can. Until Microsoft says otherwise, plan as if the workflow covers standard channels only.

## Three ways to route new members

You have three tools. They do different jobs, and most teams need two of them.

| What it does | Recommend for everyone | Onboarding workflow |
| --- | --- | --- |
| Available |
Now In Teams today

 |

December 2026 Targeted Release in November

 |
| Effect on a new member |

Tags the channel Marked recommended when they join

 |

Adds them to channels When they join the team

 |
| Who sets it |

Team owner Per channel

 |

Team owner For their own team

 |
| Private channels |

No Owner adds people by hand

 |

Not stated Plan for standard channels only

 |

Strong on this point A limit to plan for

The third tool decides who joins the team in the first place: **dynamic membership**. More on that below.

## Step 1: pick the channels every new member needs

Do this first, because both tools need the same answer. Open the team and list its channels. For each one, ask: would a new person be stuck in their first two weeks without it?

Keep the list to three to five channels. If everything is required, nothing stands out, and new staff end up muting the lot.

A typical operations team might land on:

1.  **General,** for team-wide news. Microsoft always recommends it, so it doesn’t need step 2.
2.  **Announcements,** if you post updates that nobody should reply to.
3.  **The working channel,** where the day-to-day questions happen.
4.  **Forms and how-tos,** where the files new people go looking for live.

If a channel exists only because someone made it in 2023 and nobody has posted since, archive it. Every channel you remove is one less place for a new person to look.

## Step 2: recommend those channels today

You don’t need to wait for December. Team owners can do this now.

1.  Select **More team options** (**…**) beside the team name, then **Manage team**.
2.  Open the **Channels** tab.
3.  Select **…** on the channel you picked.
4.  Select **Recommend for everyone**.

![The Channels tab of a team in Microsoft Teams, listing Design, Digital Assets Web, General and Research and Development. The more options menu for Design is open, with Recommend for everyone highlighted between Get email address and Archive channel.](https://tenantcraft.ca/images/to-02-recommend-for-everyone.png)

Manage team > Channels > ...

Design has a Show button, which means it's hidden for this user. Recommend for everyone tags a channel so new members can find it.

On the member’s side, Microsoft says “Recommended channels are those recommended by team owners,” and members can sort the channel list **Recommended first**. Microsoft’s channel editing article adds that recommended channels “display a ‘recommended’ tag when new members join the team,” and that owners can suggest “up to 10 channels.” Microsoft documents the tag. It doesn’t say a recommended channel is added to a new member’s list for them, so check with a test account before you tell staff it is. Adding new members to channels is what the onboarding workflow promises.

## Step 3: limit who can post announcements

If one of your channels is for announcements, turn on **channel moderation** so only moderators can start posts. Microsoft’s Teams overview says moderators “can start new posts in the channel and control whether team members can reply to existing channel messages.”

Team owners are moderators by default. If you also turn off member replies, new staff can read every update without digging through replies to find it.

Moderation is available in standard channels only. Private and shared channels don’t support it.

## Step 4: list the private channels and who owns them

No setting fixes this step, because it depends on who owns each channel. Microsoft’s private channel docs say “only the private channel owner can directly add or remove people from it.”

A team owner who isn’t in the private channel can see it under **Manage team**, but not add anyone. So the person onboarding a new hire often has no way to add them.

For each team, keep a short list:

-   **Private channel name.**
-   **Its owners,** at least two, so one person’s leave doesn’t block it.
-   **Which roles belong in it,** so the owner knows who to add without asking.

There’s a second trap. Microsoft says if someone leaves or is removed from a team, they’re removed from all its private channels. “If the user is added back to the team, they must be added back to the private channels.” A staff member who moves departments and back, or gets removed by mistake, loses that access quietly.

## Step 5: decide who adds people to the team

The onboarding workflow starts “when they are added to a team.” Something still has to add them. You have two choices. Microsoft hasn’t said whether a member added by a dynamic rule triggers the workflow, so test that before you rely on it.

**An owner adds them by hand.** This works for small teams. It also means onboarding depends on someone remembering on day one.

**Dynamic membership adds them for you.** The team is built on a Microsoft 365 group with a rule, such as everyone whose department is Operations. Microsoft says people “are automatically added or removed to the correct teams as user attributes change.” Before you choose it, check these:

-   **It needs a licence.** Microsoft says dynamic membership “requires Microsoft Entra ID P1 licenses.”
-   **It isn’t instant.** Once Microsoft Entra ID updates the group, Teams can take up to **2 hours** more to show the change.
-   **Owners lose the Add member button.** With dynamic membership, “Owners can’t add or remove users as members of the team.” Anyone outside the rule, such as a contractor, can’t be added to that team. Change the rule, or give them a separate team.

Dynamic membership only works when the HR data in Microsoft Entra ID is right. If department fields are blank or out of date, fix that first.

## Before December: what to tell team owners

Microsoft’s only recommendation is to inform team owners. Make that message useful. Send each owner of a busy team this, adapted to your organization:

> In December, Teams adds an onboarding workflow that can put new members into the right channels automatically. Before then, please: pick the three to five channels every new person needs, mark them **Recommend for everyone** under **Manage team** > **Channels**, and send IT a list of your private channels and their owners.

Owners who were on Targeted release before enrollment locked may see the workflow in November. Check who’s enrolled under **Settings** > **Org settings** > **Organization profile** > **Release preferences**. Don’t plan on adding new pilot users: Microsoft says that in November 2026 admins can no longer add users to Targeted release, and the program retires in January 2027. If a pilot owner gets it early, have them set it up on a real team and write down the click path for everyone else.

## What this does not fix

-   **It doesn’t add people to the team.** The workflow starts after someone joins. An owner or a dynamic rule still has to add them.
-   **It doesn’t clean up your channels.** If a team has 30 channels and nobody knows which matter, automation adds new people to the mess faster.
-   **It doesn’t replace a person.** A recommended channel tells someone where to look. It doesn’t tell them what the team expects of them in week one.
-   **It doesn’t fix private channel ownership.** If a private channel owner leaves the organization or is removed from the team’s group, Microsoft promotes a member automatically. That person may not know they’re now in charge.

## The bottom line

Adding someone to a team only shows them one channel. Pick the three to five channels a new person needs, and recommend them for everyone today. When the onboarding workflow reaches your tenant in December, team owners can add new members to those channels automatically. Keep a list of private channel owners, because Microsoft hasn’t said the workflow covers those channels.

Private channels are where onboarding and offboarding both break. The permissions cleanup guide helps you find who has access to what, and who owns it.

Permissions Cleanup & Governance Prep Checklist

PDF · 7 pages · 45 checkpoints

[Email me the PDF](https://tenantcraft.ca/resources/guides/permissions-cleanup-prep)

---

_Canonical HTML: https://tenantcraft.ca/insights/teams-onboarding-workflow-new-members · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_
