Unicorn Development AG hat dies direkt geteilt
Who can share the following experience in T2T migrations or has an explanation, what may have gone wrong? With this post we try to investigate, what may be the root cause for issues when migrating Teams Meetings to a new tenant. 😳 We observed in two different migration projects, that Teams Meeting links were not migrated correctly when using Quest Software (On Demand Migration). Most of the Teams Meeting links were migrated correctly, but the number of links not migrated (and therefore still pointing to the old tenant) was far too high, to be ignored. The Software was set up and used by different migration teams, but both projects migrated their date from the same source tenant. ❓Now we ask ourselves, are there other IT professionals who made the same experience? ❓We are struggling to find out, if the data in the source tenant or a Software bug may be the reason for these results? 🤷🏻♀️ Of course, the root cause can also be a layer 8 issue. In that case the Software documentation may be misleading, if two different migration teams from different companies make similar mistakes. 💡Your feedback is very appreciated! How we helped our customers to sort this out: Unicorn Development AG programmed an app for us, which identified the Teams Meeting links still pointing to the old tenant. The app is also providing options to cancel those meetings or to delete them from all user mailboxes.