How to transfer Teams data from EXT users to Synchronized

Adam 21 Reputation points
2021-07-20T07:16:36.973+00:00

Hello, so in my organization, I always had my employees invited to Microsoft 365, so in AAD they appeared as #EXT# users (they were told to create an account on their company email, mastech-technology.pl). However recently we decided that we want these users synchronized with the local Active Directory to utilize a single sign-on feature. We have already achieved this task by using Azure AD Connect, but now there are two users for each employee. It is important to mention that tenant's domain is also mastech-technology.pl.

What I need to do now is to find a way to transfer MS Teams data from these old #EXT# users to new "Member" users. Right now I can't even add these users to Teams, I get a "uniqueness contraint" error, presumably because of the same email (or I should say UPN) used to log in. Do anyone know the best work-around for this problem?

Microsoft Teams | Microsoft Teams for business | Other
{count} votes

1 answer

Sort by: Most helpful
  1. Sharon Zhao-MSFT 25,756 Reputation points Microsoft External Staff
    2021-07-21T02:50:59.68+00:00

    @Adam ,

    Where is the two accounts of each employee?

    If accounts are on Microsoft 365, it means your synchronization is failed. For more information, you could refer to this article.

    It has no solution to migrate all Microsoft Teams related data from one account to another account within same tenant. A workaround is to back up Teams related data from Office 365 content search or eDiscovery search. Anna Ma gives a detailed description of this workaround, you can refer to it in this link.


    If the response is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.