Team provisioning issues - Owners not seeing Team

[Jef Meyer]

We’re using the Teams PS Module version 1.0.1 to provision Teams.  A script creates a Unified Group using a Global Tenant account, then adds a user as a member to the UG, then promotes the user to an Owner, and again adds another Member and promotes them to Owner, finally a Team is created off this UG and the Global Tenant account is removed. 

From a process perspective this is working most of the time, however we’ve found that since fall 2019, occasionally, one or both Owners are not able to see the Team in the client or web.  From the tenant, everything seems to be provisioned correctly, however the only way to resolve the issue is by removing the Owner (demoting to Member, deleting from Team and adding back).  We had a ticket open with MSFT, however they are reporting it’s a timing issue and we need longer delays in the process to ensure that the ownership changes are completing in time.  However if this was the case, I wouldn’t expect to see the correct owners in management.  Also, I would expect that after a few hours, the Owner would eventually see the Team.  This is not the case, even after 2 weeks in some cases.  Is anyone else experiencing this issue or have a workaround?

[#2]

That is indeed the case, and the root cause is the "loosely coupled" nature of Groups/Teams. Because they package together multiple workloads, and sometimes the synchronous "notifications" between those workloads fail, it's not that uncommon to have to wait for the background async process to pick up the changes. Thus the delays.

[#3]

@Vasil Michev - thanks for the response.  I understand that there may be a delay, however I would assume that eventually the Owners would be able to see the Team, especially when from the Admin side, everything looks correct.  The issue is that we've found that we need to remove the user completely from the Team and add them back before they're able to see the Team.  We're looking for a resolution to this since it's causing end user frustration.

[#4]

Well, I guess you might have the wrong expectations about the length of the "eventually" window :) If you repeatedly see the process taking over 24h, best work with support.