The APIs do not support batch processing. There are two Graph APIs available for reading and one available for writing. The third problem is throughput performance. #Private one on one chat codeThe CreateChat and CreateMessage methods are just pseudo code to send an HTTP Request. For some organizations, this discovery process must start running weeks before they plan to start the chat migration. This discovery process is very slow to run but provides an accurate count at the run time. Below are the Export API queries to get all messages. These results can be used if you are willing to extrapolate the data and use an estimation.Ī second solution is to use the getAllMessages method in the Graph API. It does not return the total number of private chats or messages. However, it can only return the number of messages in a specified period (D7, D30, D90, and D180). One solution to counting private chat messages is to call the getTeamsUserActivit圜ounts method in the Graph API to return the number of messages. This discovery process can be quick or very time-consuming based on the chosen solution. The first problem is to discover all the private chats. The challenge in an Office 365 tenant to tenant migration is that there are more private chat messages to migrate than most organizations ever imagine.īut three problems exist – not one – in a chat migration project! Problem 1: Counting Private Chats Some large organizations with tens of thousands of users may have millions of private chat messages to move in a Teams migration. Many more private chat messages exist today than 2+ years ago because of the incredible growth in Teams during the pandemic. Why is Throughput Performance for Microsoft Teams Private Chat Migration Slow? This allows for the most recent work data to migrate over quickly, but the other items go into a format that is quicker to migrate. Reading 1:1 chat often isn’t the issue, writing is. Some tools let you only migrate the previous 2 weeks in the format with metadata, and migrate the rest to a text file. The best advice is to try to limit the amount of chat that is being migrated. Each chat, and reply, needs a API call to preserve all the chat metadata. Is there a clean and concise way to accomplish this?Īnswer: We agree, this is perhaps the largest challenge right now. Below is the original question and answer, of which we’ll dive into the details more in this post.Īttendee: The largest challenge I have been facing is migrating 1:1 chats from one Teams tenant to another. The idea for this post originated from the very active live Q&A in the recent TEC Talk: Lessons Learned in Merger and Acquisition Microsoft 365 Tenant Consolidation Projects. This post outlines the difficulties in migrating Teams private chats so you can prepare your project plan accordingly. The primary challenges are throughput performance and content fidelity. These large T2T migrations face challenges when it comes to Microsoft Teams private chat migrations. We see a lot of tenant to tenant (T2T) migrations with several thousand users – often tens of thousands of users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |