New Group Standard Channel Setup

Overview

This automated flow watches for newly created Microsoft 365 Groups and, when one is detected, provisions a standard set of Teams channels inside the team that backs the group. Standard channels (Announcements, Resources, plus any others configured via env vars) are created with their own description, and a templated welcome message is posted to each channel so new members land on a ready-to-use Team. The General channel is left as-is and only receives the welcome post.

Use Case

When IT or HR rolls out new collaboration spaces, a fresh Team often starts with only the default General channel — leaving owners to manually create the same set of standard channels (Announcements, Resources, etc.) and seed them with kickoff messages every single time. This flow eliminates that toil by detecting new Groups the moment they are created and shaping each backing Team to a consistent, governed structure, so every new workspace launches with the same look, feel, and onboarding content.

The flow is ideal for teams that:

• IT admins standardising Teams provisioning across the tenant
• Workplace/collaboration teams enforcing a consistent channel taxonomy
• Organisations rolling out governance for self-service Group creation
• Change/adoption teams wanting every new Team to ship with welcome content
• Scenarios where channel naming and descriptions must match a documented standard

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Deploying to another environment

Import the solution, set flowlibs_AdminNotifyEmail to the mailbox that should receive completion notifications, review flowlibs_StandardChannels and adjust the channel names/descriptions/welcome text to your tenant's standards, bind the four connection references (Office 365 Groups, Teams, SharePoint, Outlook) to accounts with permission to create channels Tenant-wide, and turn the flow on.

Adding or renaming standard channels

Update flowlibs_StandardChannels with the desired JSON array. Each entry takes name, description and welcome. The flow loops over the array so no flow edits are required to add more channels.

Skip the welcome post in General

Set flowlibs_PostWelcomeInGeneral to false to suppress the summary message in the General channel — useful if owners prefer to write their own opening post.

Scope to specific Groups

Add a condition immediately after the trigger that checks the new Group's display name prefix, classification, or owner against an allow-list (e.g., only Groups owned by HR) before continuing.

Create private channels instead

In the CreateChannel action, switch membershipType from standard to private and add owners/members from the originating Group to restrict access.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

outputs('Get_team_for_group')?['body/id']

json(variables('varStandardChannels'))

items('For_each_standard_channel')?['welcome']