Add user to Microsoft Teams Channel(private) using Microsoft Flow/Power Automate

[kbilakanti]

Hey,

I have power app which is integrated within Microsoft teams private channel, now i need to provide access to users for that specific Microsoft teams channel using Power Automate. Any help is appreciated.

I have used sharepoint as data source and is their any chance where i can provide sharepoint site permissions to user as well using power automate including app share as well.

In a nutshell, i need to make app accessible to new users by just one click using power automate.

[RobElliott · Accepted solution]

@kbilakanti it's not possible to add a user to a channel using Power Automate, there isn't an action for that.

Rob
Los Gallardos
If I've answered your question or solved your problem, please mark this question as answered. This helps others who have the same question find a solution quickly via the forum search. If you liked my response, please consider giving it a thumbs up. Thanks.

[jvdlinden]

You can use the Microsoft Graph API:

Solved: Add members to private channel from power automate - Power Platform Community (microsoft.com...

[francoisharmse7]

This was my solution. The challenge I had was to add a guest user to a private channel via powerautomate.

This is my solution to add Guest Users to Private Channels in MS Teams with PowerAutomate.

Step0 - Register the domain of the Guest Users in your AD account as a valida Guest Domain

Step1 - User a registration form (MS Forms)

Step2 - Create a Trigger Process in MS PowerAutomate to receive the Form Data. I like to create small/short flows to only capture and validate form data, and then call a separate Flow / RestService. This makes your solution a little bit more decoupled and reusable. (Imagine replacing the Form with a web app form or mobile app form in the future).

Create a second HTTP request trigger flow receiving the Form data (optional way to setup multi-flow solution)

Step3 - Create a Private Channel in teams via GrapAPI

GraphAPI - POST https://graph.microsoft.com/v1.0/teams/<teams_id>/channels

POST BODY:

{ "membershipType": "private", "displayName": "<e.g. channel name from form data>", "description": "<e.g. description from form data>", "members": [ { "@odata.type": "#microsoft.graph.aadUserConversationMember", "user@odata.bind": "https://graph.microsoft.com/v1.0/users('owner.user@mydomain.com')", "roles": [ "owner" ] } ], "@odata.type": "#Microsoft.Graph.channel" }

Step4 - Call GraphAPI to retrieve the Guest User Details

GraphAPI: GET https://graph.microsoft.com/v1.0/users?$filter=mail eq 'guest.user@email.com'

I have added this in a loop - since I had many members who had to be added - and I also included a condition check to check if the domain is indeed valid

Now you can assign the output (or portions of the output) to some variables

Step5 - Retrieve the ID value from the step above (Step4). This is the value that must be used to add the new guest member.

1. Retrieve the ID from the Step4 output
2. Also set a variable to the account type - which should (MUST BE) be "guest"

Now - Add guest users to the private teams channel

Step6 - Call GraphAPI to add guest members

GraphAPI: POST https://graph.microsoft.com/v1.0/teams/<team_id>/channels/<channel_id>/members

Post Body: The role must be "guest" for guest account But valid options for other types of access can be

1. owner
2. member
3. guest

Microsoft documentation (HERE) states roles must be owner or empty This did not work so well for me. Use guest

{ "@odata.type": "#microsoft.graph.aadUserConversationMember", "roles": [ "@{variables('membership_type')}" ], "user@odata.bind": "https://graph.microsoft.com/v1.0/users('@{variables('principal_user')}')" }

Bonus Step Now you can catch all responses from the previous steps and respond back with an HTTP Request/Response connector.

1. A 200 response on successful executions
2. A non-200 response on failed executions (or how ever you desire)

To configure exception handling or failure handling responses do this below

[wind0soft]

Hi, can anyone provide an update for this based on the new HTTP Graph connector: 

I can create a channel no problem using:

But anytime I try and add a new owner the flow will not save:

I've tried this code:

{ "@odata.type": "#Microsoft.Graph.channel", "membershipType": "private", "displayName": "Private corner again", "description": "This is for private content", "members": [ { "@odata.type":"#microsoft.graph.aadUserConversationMember", "user@odata.bind":"https://graph.microsoft.com/beta/users('{UserID1}')", "roles":["owner"] }, { "@odata.type":"#microsoft.graph.aadUserConversationMember", "user@odata.bind":"https://graph.microsoft.com/beta/users('{UserID2}')", "roles":["member"] }, ] }

And I've tried adding a second @ sign but it will not save.  

Any ideas would be greatly appreciated!

[jvdlinden]

Hello @wind0soft I notice that in the plain text code you pasted, at the very end of your members array, you leave a comma. This one should be removed otherwise there is another user to be expected in the JSON array. But I do not see the comma in your image.

You can also use the website https://jsonlint.com/ to verify your JSON code.

Below I provide you with an a working example of how I have created a private channel (with members):

I hope this helps.

By the way: I use the default 'HTTP' action, but I guess it would be the same in your case. I use the same method and request URL.

[wind0soft]

Hi all-

I really appreciate the feedback but unfortunately it didn't work for me.  Yes in the code I posted there is a extra comma.  However, even with code that is validated 

I get an error in power automate

However, if I use this connector 

The code will save but then I get a error when it runs with a Bad URI result.  

Any thoughts?

[jvdlinden]

Just checking, did you use URL https://graph.microsoft.com/ while setting up the connection? As suggested here: Solved: Http Request with Graph - Power Platform Community (microsoft.com)

You can also try to use the action 'Send an HTTP request' (Office 365 Groups) to perform actions on Microsoft Graph. In my case that works too (delegated):