org-wide removed user gets added again

[Ricardo Mendes]

Hello all,

I have been doing some testings with org-wide teams and faced myself with a wird thing when removing and adding users.

I create an org-wide Team as a Global Admin directly from Teams client (Web). After the team creation I saw that all users in the tenant got added to that org-wide Team. Until now everything as expected.

Deleted one member directly from the team - Diego Siciliani. Created a new user in M365 Admin Center (Ricardo Mendes). After some minutes I found that Diego Siciliani was added again (no change was made to that user in M365 Admin Center). Did some other testings and this did not happen again. No dynamic membership was used for this.

Anyone had seen something like this?

Rgs,

RM

[#2]

There is some obfuscated magic when it comes to the group membership of an Org Wide Team. Believe me I have looked as initially I was just expecting it to be a pre configured dynamic membership group.

Not sure about the, you did some more testing and it didn't happen again bit but what you described is what I would expect.

So you removed a user from the Team but not Azure AD or it was not set as inactive in Azure AD. So it is still an account and therefore it will get added back in.

If this is not desirable then you might be better off creating a Team with dynamic group membership configured to your hearts content.

Also refer to this:

https://docs.microsoft.com/en-us/microsoftteams/create-an-org-wide-team

Key bit being:

These types of accounts won't be added to your org-wide team:

Accounts that are blocked from sign in
Guest users
Service accounts
Room or equipment accounts
Accounts backed by a shared mailbox

Thanks

Henry

[#3]

@HenryPhillipsNimbitech thanks for your feedback. 

Regarding the testings done they were all with the same assumptions. Deleted some users from the org-wide team using the Teams client. And by doing this, only the first one to be deleted got readded again, all the other were not. 

Regarding the link you shared that was exactly what seems strange, because according the documentation, if you remove a user, they should not be readded:

"Remove accounts that might not belong

Even though members can't leave an org-wide team, as a team owner, you can manage the team roster by removing accounts that don't belong. Make sure you use Teams to remove users from your org-wide team. If you use another way to remove a user, such as the Microsoft 365 admin center or from a group in Outlook, the user might be added back to the org-wide team."

[#4]

Hi @Ricardo Mendes ,

Sorry completely glossed over that point.

I know you have probably checked this anyway but is there a big difference account wise between the account that got added back in and the one that didn't. So say Role wise as an example?

Thanks

Henry

[#5]

Hi @Ricardo Mendes ,

This might also highlight the fact that a Team with its Membership populated by way of a dynamic group might be the way to go as at least that way you are in more control, especially if you need it for a not quite all Org purposes.

Thanks

Henry

[#6]

nop. same user settings, roles, licenses.