Forum Discussion
Duplicate Organizations & Users in Microsoft Teams (mac)
systemsmaven Unfortunately, we're testing the software with free accounts. I was able to remove the duplicate user, but I am still unable to remove duplicate organizations from individual users.
Hmmmm, if you can find out who the owner of the second organization is they should be able to remove all of the members and delete the free organization. The trick will be finding out who the owner of the second team is. Whomever it is should have the Manage org option available in their Teams settings. Members can also leave a free Team but they may end up leaving the wrong one so your best bet is to have the owner remove the members.
Here's the write up on how to delete an Teams Free Org:
https://support.office.com/en-us/article/delete-your-teams-free-organization-2c28cfcf-3fbf-497c-938f-8815a8f6a6b9
systemsmaven From what I can tell, EVERY member owns a unique Organization that was created automatically when they set up their account.
The individual users don't seem to have the ability to delete their duplicate organization from the Manage Org menu:
We were hoping to use this as an alternative to Slack, but this seems pretty buggy.
Oh no... from the write up it looks they'd all have to call MS to have the orgs removed...
It really does work great once you've got it up and running. It sounds like your initial implementation went a little sideways. My company has about 100 teams for all different purposes, (departmental teams, project management, cross-functional groups, we even have a Dungeon and Dragons team and a Book Club)
systemsmaven The biggest frustration right now is that it was a system generated action that created all of these duplicate Organizations by default during the user creation process. Users couldn't create their accounts without entering a company name, and the company name was automatically used to create an organization.
We got an error every time we tried to invite a user and then create an account (both Mac and PC users) so there may be a bug that hasn't been addressed yet.
Doubtful that every single team member is going to follow through and call Microsoft (seems like a weird approach?) so I think we're going to be stuck with them for now. Thanks for your help!