SOLVED

Team creation delay?

%3CLINGO-SUB%20id%3D%22lingo-sub-339136%22%20slang%3D%22en-US%22%3ETeam%20creation%20delay%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339136%22%20slang%3D%22en-US%22%3E%3CP%3EWhenever%20we%20create%20a%20new%20O365%20group%20with%20new%20members%20%3CSTRONG%3E%3CEM%3Eor%3C%2FEM%3E%3C%2FSTRONG%3Eadd%20members%20to%20an%20excisting%20O365%20group%2C%20it%20can%20take%20up%20to%20half%20a%20day%20to%20an%20entire%20day%20for%20the%20team%20to%20show%20up%20in%20MS%20Teams%20(browser%20or%20client).%20Has%20anyone%20else%20experienced%20something%20similar%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EInteresting%20enough%2C%20when%20we%20go%20the%20other%20way%20and%20start%20by%20creating%20a%20new%20team%20from%20MS%20Teams%2C%20the%20O365%20group%2FSharePoint%2Fmailbox%20show%20up%20instantly%20without%20any%20hassle.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20could%20be%20the%20reason%20behind%20this%20behavior%3F%20We%20have%20no%20AD%20federation%2FOnprem%20sync%20enabled%2C%20just%20cloud%20users%20from%20Azure%20AD.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-339136%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-341140%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20creation%20delay%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-341140%22%20slang%3D%22en-US%22%3E%3CP%3EYou're%20absolutely%20right.%20Our%20customer%20has%20over%2015.000%20users%20and%20specific%20need%20for%20automation%20%2B%20template%20design%2C%20so%20some%20sort%20of%20provisioning%20through%20MS%20Graph%20API%20is%20an%20necessity%20in%20this%20case.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339216%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20creation%20delay%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339216%22%20slang%3D%22en-US%22%3EAgree%20with%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72542%22%20target%3D%22_blank%22%3E%40adam%20deltinger%3C%2FA%3Eon%20this.%20We%20see%20many%20cases%20where%20organisations%20try%2C%20for%20example%2C%20to%20create%20Teams%20via%20the%20Graph%20API%20or%20Powershell.%20It%20has%20taken%20up%20to%2024%20hours%20to%20show%20up!%20However%2C%20as%20you%20and%20Adam%20say%20if%20you%20do%20it%20straight%20through%20the%20Teams%20App%20then%20it%20pretty%20much%20shows%20immediately.%3CBR%20%2F%3E%3CBR%20%2F%3EAt%20the%20moment%2C%20I%20would%20recommend%20the%20same%20as%20Adam%20and%20to%20do%20it%20through%20Teams.%20However%2C%20there%20is%20a%20growing%20demand%20for%20this%20so%20I%20would%20maybe%20consider%20raising%20this%20question%20at%20the%20Teams%20Developer%20AMA%20today%20at%209AM%20PST%20in%20the%20Microsoft%20Teams%20AMA%20forum.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20this%20latency%2Fpropagation%20needs%20to%20come%20down.%20More%20and%20more%20people%20need%20to%20do%20this%20programmatically%20-%20long%20term%20there%20can't%20be%20so%20much%20disparity.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-339138%22%20slang%3D%22en-US%22%3ERe%3A%20Team%20creation%20delay%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-339138%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20this%20is%20expected%20behaviour!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDue%20to%20the%20many%20services%20used%20Office%20365%20groups%26nbsp%3B%20it%20takes%20time%20to%20propagate!%20(up%20to%2024%20hours)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20general%20rule%20is%3A%20Add%20members%20in%20the%20service%20you%20want%20to%20use%20them%20for!%20In%20this%20example%20it%20is%20Teams.%20Then%20add%20them%20from%20Teams%20and%20it%20will%20go%20instantly!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20propagation%20will%20go%20faster%20in%20other%20directions%20in%20the%20future%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2F%20Adam%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Whenever we create a new O365 group with new members or add members to an excisting O365 group, it can take up to half a day to an entire day for the team to show up in MS Teams (browser or client). Has anyone else experienced something similar?

 

Interesting enough, when we go the other way and start by creating a new team from MS Teams, the O365 group/SharePoint/mailbox show up instantly without any hassle.

 

What could be the reason behind this behavior? We have no AD federation/Onprem sync enabled, just cloud users from Azure AD.

3 Replies
Highlighted

Yes, this is expected behaviour!!

 

Due to the many services used Office 365 groups  it takes time to propagate! (up to 24 hours)

 

The general rule is: Add members in the service you want to use them for! In this example it is Teams. Then add them from Teams and it will go instantly!

 

Hopefully propagation will go faster in other directions in the future

 

/ Adam

Highlighted
Best Response confirmed by Thijs Hurenkamp (Occasional Contributor)
Solution
Agree with @adam deltinger on this. We see many cases where organisations try, for example, to create Teams via the Graph API or Powershell. It has taken up to 24 hours to show up! However, as you and Adam say if you do it straight through the Teams App then it pretty much shows immediately.

At the moment, I would recommend the same as Adam and to do it through Teams. However, there is a growing demand for this so I would maybe consider raising this question at the Teams Developer AMA today at 9AM PST in the Microsoft Teams AMA forum.

I think this latency/propagation needs to come down. More and more people need to do this programmatically - long term there can't be so much disparity.

Best, Chris
Highlighted

You're absolutely right. Our customer has over 15.000 users and specific need for automation + template design, so some sort of provisioning through MS Graph API is an necessity in this case.