SOLVED

Delay between Graph API and Teams Client

%3CLINGO-SUB%20id%3D%22lingo-sub-1510717%22%20slang%3D%22en-US%22%3EDelay%20between%20Graph%20API%20and%20Teams%20Client%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1510717%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20Teams%20automation%2C%20where%20we%20are%20removing%20from%20teams%20which%20are%20classified%20as%20internal%20.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20was%20working%20Okiesh%20for%20a%20year%2C%20however%20since%20last%20few%20months%20we%20are%20observing%20that%20it%20takes%20almost%202%20days%20to%20get%20the%20Guest%20user%20actually%20removed%20from%20Teams%20Client.%20We%20use%20Graph%20api%20(Memebers%20endpoint%20)%20to%20remove%20these%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20endpoint%20correctly%20return%20number%20of%20members%20with%20GET%20request.%20However%20%2C%20GUEST%20user%20can%20still%20access%20the%20teams%20for%20around%20two%20days%20then%20ultimately%20gets%20removed.%20Strange%20thing%20is%2C%20Guest%20users%20access%20to%20respective%20sharepoint%20site%20is%20removed%20immediately%2C%20its%20only%20Teams%20client%20that%20takes%20time.%20We%20have%20tried%20both%20V1%20and%20Beta%20endpoint%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20seen%20users%20reporting%20this%20randomly%20over%20the%20internet.%20One%20such%20case%20is%20at%20below%20link%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F51291779%2Fteams-graph-api-adding-a-team-member-not-always-working%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F51291779%2Fteams-graph-api-adding-a-team-member-not-always-working%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F57004682%2Faad-groups-and-ms-teams-sync-is-too-slow%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F57004682%2Faad-groups-and-ms-teams-sync-is-too-slow%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1510717%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGraph%20API%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGuest%20Users%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1510813%22%20slang%3D%22en-US%22%3ERe%3A%20Delay%20between%20Graph%20API%20and%20Teams%20Client%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1510813%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%20this%20seems%20to%20be%20a%20trend%20recently.%20Best%20open%20a%20support%20case%20and%20report%20it%2C%20so%20that%20MS%20can%20prioritize...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1543030%22%20slang%3D%22en-US%22%3ERe%3A%20Delay%20between%20Graph%20API%20and%20Teams%20Client%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1543030%22%20slang%3D%22en-US%22%3E%3CP%3E%40o%20provide%20further%20update%20on%20this.%20We%20did%20raise%20ticket%20with%20MS%20and%20the%20response%20was%2C%20%22This%20behavior%20is%20expected%20since%20the%20exponential%20growth%20of%20teams%20and%20they%20are%20working%20on%20this.%20Issue%20is%20the%20pipelines%20that%20takes%20care%20of%20syncing%20Azure%20AD%20members%20with%20teams%20client%20is%20constantly%20getting%20throttled%20hence%20the%20delay.%26nbsp%3B%3C%2FP%3E%3CP%3EMS%20is%20working%20on%20BETA%20endpoint%20that%20could%20be%20on%20top%20of%20TEAM%20directly%20so%20changes%20will%20be%20instantaneous%20%2C%20however%20there%20is%20no%20ETA%20%22%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hello

 

We have a Teams automation, where we are removing members from teams which are classified as internal . 

 

This was working Okiesh for a year, however since last few months we are observing that it takes almost 2 days to get the Guest user actually removed from Teams Client. We use Graph api (Memebers endpoint ) to remove these users.

 

The endpoint correctly return number of members with GET request. However , GUEST user can still access the teams for around two days then ultimately gets removed. Strange thing is, Guest users access to respective sharepoint site is removed immediately, its only Teams client that takes time. We have tried both V1 and Beta endpoint

 

Have seen users reporting this randomly over the internet. One such case is at below link 

 

https://stackoverflow.com/questions/51291779/teams-graph-api-adding-a-team-member-not-always-working

 

https://stackoverflow.com/questions/57004682/aad-groups-and-ms-teams-sync-is-too-slow

2 Replies
Highlighted
Best Response confirmed by ThereseSolimeno (Microsoft)
Solution

Yeah, this seems to be a trend recently. Best open a support case and report it, so that MS can prioritize...

Highlighted

@o provide further update on this. We did raise ticket with MS and the response was, "This behavior is expected since the exponential growth of teams and they are working on this. Issue is the pipelines that takes care of syncing Azure AD members with teams client is constantly getting throttled hence the delay. 

MS is working on BETA endpoint that could be on top of TEAM directly so changes will be instantaneous , however there is no ETA "