Adding invited (guest) user to teams seems to not work properly (GRAPH API)

New Contributor

Issue: Adding invited (guest) user to teams seems to not work properly.


After setting up the tenant to allow invitation of user from another domain, we are able to invite external users (in set domain) to teams. This works fine when doing it manually, in the GUI.
However, when trying to add an invited user threw the windows graph API, something is not working properly.
Our procedure to invite a user to a team is as follows:
Note we are using application privileges

  1. Invite the user to the tenant (with or without welcome mail)

  2. Add the invited user to the team

Both these calls complete successfully and does not return any error messages. In all the admin GUI’s (AAD, Teams, Exchange) the user is invited and is added to the group.
But the user in question does not receive a welcome mail that he/she has been added to the team. And if the user (given we send a welcome mail in step 1) tries to access the user gets notified that he/she does not have permissions and/or does not see the team.


API Permissions


API PermissionsAPI PermissionsNOTE:

After some investigation, by monitoring the network traffic. It's seems that the missing call, to get properly invited to the team is:

where you send in a list of userid (8:orgid:{userid}) and the groupid. (teamurl seems to be the channel id)




I have tried to call this from application & delegation, but get 'Unauthorized'. Also I could not find any API permission that granted access to ''.

7 Replies



This one may be a good one for @Alexander H who I know does a lot of work with Teams and the Graph API. 


Best, Chris


How long are you waiting? Your graph calls are adding the user to the group, there is known lag that can sometimes take 24 hours or more before changes to the group are properly respected within the Team UI.


as Steven says, it can take up to 24h to sync everything.

Do you have the link to the doc page where you found the bulkupdate link? Cant seem to find the page.

Then i can take a look at it.


Hi @Steven Collier & @Alexander H 

After some more testing, here are my result: 

Sometimes it takes 8 hours, sometimes 3 hours and sometimes 10 minutes. So, as you said uptil 24 hours, which is alot :) And none of these get a welcome mail, which is unfortunate.  But this is a little more consistent then a couple of weeks ago, where it was completely random if a user got added or not (waited several days).


About the bulkUpdate, I only found that by monitoring the network traffic when adding/inviting a user manually. Also the link has recently (as of last week) changed from to Also it was PUT not POST.



Then if a go to another team, where this user is not invited, copy the cURL (bash), edit the url (channel-id) and groupid (payload/body) to reflect the new team, then post the request i Postman and RUN it. The user get added immediately and receives a welcome email to the team.



Any reason why it takes upto 24 hours when doing it at the backend, but in the GUI it happens instantaneously?





The Teams service is built from the groups service, but it is a relatively loosely coupled system. At the moment the Graph only exposes an API to add people to the Group, so you need to wait for the Teams application to pick up that change.


The Teams client makes changes within the Teams service and into the group simultaneously, it also chooses to send an email to welcome the user to the Team. I think what you really want is a graph api to add users directly to the Team and group together, have a look for the Microsoft Graph uservoice and put in your idea.


It might also be worth testing out the Microsoft Teams Powerhell component, it has a cmdlet to add a team member but I don;t know if that is to the Team or Group. If it get what you want you could wrap that up in an Azure Automation runbook to build your own API.


Ok, guess we have to live with the delay for now. Also tried the Powershell, but was more or less the same result.


Added a uservoice:


Thanks for the replies.