Co-Organizer in teams Meeting

[srduval]

I was looking for a way to add a co-organizer in teams and came across this post from last year. Anyone know if it's still not possible and/or on the road map to being available?

The ask is my HR group is wanting to automate the scheduling of meetings and for some of those meeting they are wanting to be able to list a co-host/organizer of the meeting.

Power Automate JSON add co-organizer - Microsoft Community Hub

[annetoal]

According to Re: Power Automate JSON add co-organizer - Microsoft Community Hub it appears to be impossible to do what you are wanting, at least as of last September. Sorry.

Anne

[SamuelBenjamin]

Did you try this to use the onlinemeetings patch?

PATCH /users/{userId}/onlineMeetings/{meetingId}

Be sure to include the header Prefer: include-unknown-enum-members.
The json should include the already existing attendees, including the new one.

{
"participants": {
"attendees": [
{
"upn": "existingattendee1upn",
"role": "attendee"
},
{
"upn": "existingattendee2upn",
"role": "attendee"
},
{
"upn": "newcoorganizerupn",
"role": "coorganizer"
}
]
}
}

[srduval]

I'll have to give this a try and see what happens. The project I was needing this for was moved from my work queue, but I'll have to try it and report back for future reference.

[SamuelBenjamin]

It's working fine for me in production environment. Just note if you add the same user twice with attendee and coorganizer role, then will always get the lower permission role. So if this situation may happen within your scenario, then some coding will be required to filter the participants before adding the new coorganizer.

And also note adding/removing attendees with this method will NOT notify them.

[DSFlemming]

Hello SamuelBenjamin

I would be great if I could get this working. I need to convert the existing attendee to a coorganizer with that JSON. Would that work too? 

The action fails with a 404 error forbidden error.

[SamuelBenjamin]

Hi! Your code seems ok, the 404 forbidden error maybe something related to your permissions to access this endpoint. In my case, I use application permissions (standard http request action with previously created token) so not having permission issues at all. You may check this, because the invoke http request with azure action has some permission restriction with some endpoints.

Regarding your question, yes, it should work, just note when you input same upn with different roles (participant and coorganizer in your case), the lowest privilege will be applied.

The action to update de online meeting details requires to input the already existing participants so in your case, some extra code will be mandatory.
In my workflow:
1 I get the online meeting details to retrieve the already existing participants array.

2 Filter array to verify to be sure the upn I will promote to coorganizer is not any longer in the array.
3 Add the new coorganizer to the array.

[DSFlemming]

Thanks very much. I'm not using an application so I'll adjust my process.

[srduval]

Ok I finally got around to trying this and using the send http to outlook action in power automate, I'm getting an invalid URI error "https://graph.microsoft.com/v1.0/me/onlineMeeting/@{outputs('Create_a_Teams_meeting')?['body/id']} is my URI, does the outlook http (graph api) not support a teams meeting?

[SamuelBenjamin]

Sorry, not sure what are your trying to do here... There are 2 ways to create Teams meeting:
-Via calendar api (create event): it just creates an outlook appointment and you can use the "isonlinemeeting" and "onlinemeetingprovider" to enable the Teams meeting. The response will include the online meeting join url. All attendees will receive the calendar invite to the meeting. Users will have the option to direct join the meeting from calendar, just right clicking the event and selecting "join".
The calendar API, as far as I know, does not allow to specify coorganizers, that's why we use the onlinemeetings API in a second stage to promoto coorganizers.

-Via onlinemeetings API: you can create, update and delete onlinemeetings. With this API, you can specify roles on the meeting such as attendee, coorganizer, moderator and all the options available whe you setup the meeting options on your computer.
This API will not notify users, that's important. So you will have to recover the online meeting information and include it into a calendar invite as a regular text, within the body of the event. Note users will not have the option to join the meeting by right click on the invite.

What are we doing in our project?

We create the event via calendar API, including the propertes isonlinemeeting=true and onlinemeetingprovider="teamsForBusiness" so everybody gets notified.

Then from the create event response we get the join web url for Teams. With this url, we get the meeting details, that include already existing participants, onlinemeeting ID, etc.

We then promote participants to coorganizers as explained a on previous post.

[srduval]

Thanks for the reply. What I am trying to do is automate the scheduling of some all-company meetings. These meetings are being created by a shared organizational account so that they are not tied to anyone individual. Then I'm trying to share (co-host) that meeting with our marketing team. I am using the create teams meeting action in power automate, then passing the meeting id from the create action to the send HTTP request. So maybe I have to run the whole process through the API instead of picking up 1/2 way. I might also have a permissions issue, I tried running some stuff on the MS tryit engine, and ran into an issue where I needed admin consent, so I've escalated that to my admin and we'll see what happens if/when they approve it.

[SamuelBenjamin]

The error you are getting is because you are sending an http request that is not allowed by the connector.

As you may note, there are many Send HTTP request actions in Power Automate, such as Send HTTP request to Office 365 Outllok, Send HTTP request to Sharepoint, Send HTTP request to Office 365 users, etc.
Not all the requests are allowed in all of these actions, as are restricted to certain scopes.

The easiest way to perform this action is using application permissions and a regular HTTP request (premium connector).

[srduval]

I bet you are right. My problem is I don't know how to get a token prior to be able to authenticate with outlook prior to initiating the API call

[SamuelBenjamin]

You need application permissions. Your IT needs to create the application and give your the secret. Once you have it, you can use the HTTP action to get a token. Then, use the token to send the request to the API.

https://iamrehanmemon.medium.com/generate-authentication-bearer-token-in-power-automate-using-azure-...

For enhanced security, you can use Azure Vault Keys to store the secret
https://recursion.no/blogs/power-automate-store-your-api-access-tokens-in-azure-key-vaults-and-autom...