Showing posts from January, 2023

White Paper to Microsoft TEAMS CROSS-TENANT Migration

Dedicated White Paper to Microsoft TEAMS CROSS-TENANT Migration. The guide includes Teams Team/Channels, private/ personal chat and Enterprise Voice  (Direct Routing) migration explanation and recommendations. It is written for decision maker, project manager and solution architects. Download @ SlideShare

Teams Channel Cross Tenant Migration

  Teams Channel Migration Starting with the generics of Teams Team/ Channel migrations. There can be not Team without a corresponding M365 group. This implies, that other services are available and Teams is heavily depending on those. Mainly it is SPO/ OneDrive. It is used for files in Teams. Not talking about the M365 Group provisioning here in detail, but the important sequence you must follow is: 1.        Create a user mapping file and provision target users 2.        Provision M365 groups in target tenant all member user must exist Note for M365 Groups: There is no tool available yet, which could keep M365 Groups in persistent sync. Therefore, delta sync’s are required. Other services used by or from within Teams are e.g. Tabs, Wiki & Planner. Shared Mailbox are not part of the Teams integration, but other apps made available in Teams might. Secondly, Teams has shared channels and private channels. Both have their own complexity. ·        Private channel requir

Cross Tenant Migration Options for Teams Chat Messages Destination

  Migration Options for Teams Chat Messages Destination We take away, that is nearly impossible provisioning Teams personal chat messages on time and along with other personal data migration during the cut-over day. Therefore left is, how or where we can stage the personal chat messages. Generally, the migration consist of two phases, reading and writing the message. Those both processes are individual.   Writing chat messages into the target tenant with all listed possibilities: Write the private chat messages to a folder in Outlook in the target tenant. By doing so, there are limitation for users. Outlook folders will display the messages in the Teams client, nor are those messages searchable or readable from the Teams client. Migrate all the private chat messages from source to the target appear inf in Teams. It is so fare the best user experience option, with the limitation, that the migration account is the “new mess

Teams Cross Tenant Migration for Personal Chat

  Teams Personal Chat Migration   The largest challenge I have been facing is migrating 1:1 chats from one Teams tenant to another . 1:1 Chat Migration is extremely slow. Guess you have experienced this while using Teams App. If you scroll within a chat and reached the non-cached messages, they are pulling very slow. This is what you will experience upon execution of Chat messages. Additionally complex is the availability of shared files. If OneDrive isn’t fully sync’ed, placing the sharing information is impossible. This indicates the sequence for user service migration. Let’s list the three major challenges in personal chat migrations:   1.       Counting the Private Messages Teams has no out-of-the-box possibility counting the personal/ group chat messages. You could write a script using the GraphAPI:   getTeamsUserActivityCounts method A limitation exists here, it can only return the number of messages in a specified period (D7, D30, D90, and D180). It does not retu

Teams Direct Routing Cross Tenant Migration

  Direct Routing – your own SBC with a PSTN Provider Best option as usual is the Direct Routing. Where I will focus on in this blog article. During migration, there might be other services using PSTN, like a PBX or even a Call Center. This is not part of this migration consideration, but with the described migration approach, it is separated from the Teams migration. This will provide you with more flexibility than the other PSTN interaction possible in Teams. In general with any PSTN provider it is difficult or even impossible splitting PSTN number block along with your migration of users. Therefore another approach must be implemented. Additionally the described process also eliminates the need of additional SBCs in your environment and protects your investment. The idea and used method is called DUAL FORKING . Dual forking is the possibility addressing a call to multiple destinations. In our case we want this dual forking happening between two Microsoft M365 Tenants.