Create Private Teams Channels from Power Automate
Diesen Beitrag auf Deutsch lesen
Use Microsoft Graph through HTTP with Microsoft Entra ID to create private Teams channels with an owner and defined members.
TL;DR
Power Automate's standard Teams connector cannot create private channels. Use the HTTP with Microsoft Entra ID action to POST to Microsoft Graph with membershipType set to private and a members array containing at least one owner. The flow can add up to 200 members, while permissions and Teams policy can still block the request.
Original by Marcel Lehmann, on PowerPlatformTip. Read the original
This is our own summary, not a republication or full translation. Both publications are edited by Marcel Lehmann.
Governance takeaway
- Makers: Call Microsoft Graph through HTTP with Microsoft Entra ID, set membershipType to private, and include at least one owner so creation does not fail with HTTP 400.
- Admins/CoE: Check that the acting identity has Channel.Create or Group.ReadWrite.All and that Teams policy allows Create private channels; otherwise valid flows can receive 403 Forbidden.
- Security/Compliance: Treat the members array as the access boundary, because private channels are visible only to listed members; keep the returned channel ID for controlled follow-up automation.
Frequently asked questions
Why can't the Teams connector in Power Automate create a private channel?
The native Teams connector only creates standard channels and offers no option to set the membership type or assign an owner.
Why does Graph return a 400 error when I create a private Teams channel?
Most likely because no owner was included. A private channel cannot be created empty, so the request needs a members array with at least one person holding the owner role.
Do I need an app registration for the Graph call in Power Automate?
No. The HTTP with Microsoft Entra ID action uses the preauthorized identity of the connection, so app registration and secret management are not needed.