cdbuzzell / teamsrequests Goto Github PK

Instead of waiting an arbitrary amount of time for the Team Clone operation to complete, make calls to check before continuing
https://docs.microsoft.com/en-us/graph/api/resources/teamsasyncoperation?view=graph-rest-1.0
A Microsoft Teams async operation is an operation that transcends the lifetime of a single API request. These operations are long-running or too expensive to complete within the timeframe of their originating request.
When an async operation is initiated, the method returns a 202 Accepted response code. The response will also contain a Location header, which contains the location of the teamsAsyncOperation. Periodically check the status of the operation by making a GET request to this location; wait >30 seconds between checks. When the request completes successfully, the status will be "succeeded" and the targetResourceLocation will point to the created/modified resource.

I have been using this process to provision Teams groups for my company for a few months now with mostly good results. The issue I have been experiencing is when the ownership permission is applied to the group using the REST call to Graph, it is only applying the owner to the Office 365 group, and because they are an owner only and not a member as well, they are unable to add features such as Planner.

What I have done to correct this issue is to precede the HTTP call to add ownership to the group with the below HTTP call to add the requester as a member first, then add them as an owner.

HTTP action
{"inputs": { "method": "POST", "uri": "https://graph.microsoft.com/v1.0/groups/@{outputs('Strip_Team_ID_from_Location_Response')}/members/$ref", "headers": { "Authorization": "Bearer @{body('Parse_JSON')?['access_token']}" }, "body": { "@@odata.id": "https://graph.microsoft.com/v1.0/users/@{body('Get_Owner_ID')?['id']}" } } }

The result is a Teams group having the requester as both member and owner in Azure AD which allows for the requester to be able to utilize the Teams Group like any member can.

IF the template Team does have a wiki, the Team resulting from the request ends up having two wikis.

If the Request includes adding a Team owner (or secondary owner) who also happens to have created the template, the HTTP request to add the owner fails because that user is already present.

How might that error be best avoided/suppressed?

The exported Flow contains the AllowGuests attribute/column, but the screenshots for setting up the TeamsRequests list does not.

Instead of making the initial HTTP call to get a bearer token, you can choose the Azure AD auth type on the POST to do it for you, eliminating the need for the first HTTP action.

UrlEncode the secret string in the flow to deal with special characters

Include all actions to build from scratch, so people don't have to rely on fixing up the imported flow