Auto-Create M365 Group for New Project

Overview

This flow automates the creation of Microsoft 365 Groups whenever a new project is added to a SharePoint list. It eliminates the manual step of setting up collaboration infrastructure for new projects by automatically provisioning the group, adding the project lead as a member, updating the SharePoint record, and sending a confirmation email.

Use Case

Project managers or PMO staff add new projects to a central SharePoint list. Without automation, someone must manually create a Teams/M365 Group, invite the project lead, and record the group details. This flow handles all of that automatically, ensuring every project gets a collaboration space within seconds of being registered.

The flow is ideal for teams that:

• IT Admins responsible for provisioning collaboration spaces
• Project Managers and PMO staff who onboard new projects
• Teams that want consistent, automated M365 Group creation tied to a SharePoint list of record

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.

Import the solution and authorize connections

Import the solution zip into the target environment and authorize the SharePoint, Office 365 Groups, and Outlook connection references with an account that can create M365 groups and read/write the Projects list.

Provision the Projects SharePoint list

Create a SharePoint list with columns Title (Text), ProjectLead (Text, UPN format), Department (Choice), ProjectDescription (Note), GroupCreated (Yes/No), and GroupId (Text). The flow's PatchItem step writes GroupCreated and GroupId back to this list.

Set environment variable values for your tenant

Set flowlibs_SharePointSiteURL to your tenant's SharePoint root site, flowlibs_ProjectsListGuid to the GUID of the new Projects list, flowlibs_NotificationEmailAddress to your desired recipient, and flowlibs_M365GroupMailPrefix to your preferred mail-nickname prefix.

Turn on the flow after configuration

The flow is shipped in the Stopped (Off) state. After importing, configuring connections, and setting env vars, enable the flow so the SharePoint trigger starts firing.

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.

concat(variables('varMailPrefix'), replace(toLower(triggerOutputs()?['body/Title']), ' ', '-'))

not(equals(triggerOutputs()?['body/ProjectLead'], ''))

Dynamic JSON built with concat() and json() wrapping the project title, description, and computed mail nickname, then POSTed to https://graph.microsoft.com/v1.0/groups.