The past year saw more and more organizations making the move to Office 365. To meet this growing demand for migration-related content, our experts wrote some of their best blog posts on the topic yet.
This list sums up our top 5 most-viewed migration posts from the entirety of 2019. Happy reading!
Should I consider Microsoft Teams for short-term projects, or is it more suitable for long-running groups such as committees?
Microsoft Teams can be used in both circumstances, but the organization of information is especially key in long-term scenarios. Setting standards for use, implementing a strategy, and training end users will all be necessary. In addition, there are several considerations for teams governance that may come into play.
I saw that Microsoft Teams currently has a limit of 250 users for a call/meeting. Is there anything on the roadmap to increase that number?
For larger meetings, current the intent seems to be to host a Teams Live Event. This is typically a better fit for this anyway since you can control who can contribute to the meeting.
Microsoft Teams relies on user mailboxes that’re hosted in Exchange Online and are powering the advanced features of Outlook. While Microsoft Teams can technically run without user mailboxes being hosted in Exchange Online, several Office 365 services rely on the mailbox to work fully, if at all. Some of these services use the Exchange mailbox as a store of messaging information, while others just leverage the ability to be able to contact you in the first place.
An example of this is Microsoft Planner. Without Exchange Online users may have issues viewing comments, adding comments to a task, or even viewing their favourite plans at all. Similarly, if you want to be notified when a task has been assigned to you, you’re going to need an Exchange Online mailbox.
So far all I’ve addressed is the functionality of Office 365 apps. What’s potentially more important is the compliance aspect of Microsoft Teams, such as the ability to perform eDiscovery searches and use supervision policies. These also require that mailboxes be hosted in Exchange Online to work properly because, while some aspects of Microsoft Teams may work without it, it won’t be a complete and fully functional solution.
When it comes to the technical side of sunsetting Skype for Business and transitioning users to Microsoft Teams, you need to consider (in addition to what your different options are along the journey) how interop works between those two environments, and what that ultimately feels like for the users? You also need to consider how the transition effects admins. How do you deal with this on a user by user, group by group basis? We’ll dive into all of this!
There are three phases for using Skype for Business and Microsoft Teams side-by-side. Microsoft will sometimes call them coexistence modes, and when they say coexistence, they’re referring to the coexistence between Skype for Business and Microsoft Teams as a user. In the first phase…
In this method for an in-place upgrade, a developer writes the scripts necessary to update current SharePoint content to the latest version in an automated way.
Since SharePoint runs as a platform with rich Application Programming Interfaces (APIs) and PowerShell cmdlets, this is a very robust option. Depending on the legacy source system, the custom script may also integrate with that system to ensure a more complete migration while preserving configuration and content metadata.
When to Select:
While powerful, fully taking advantage of this option requires a developer who is highly skilled in SharePoint development (APIs and/or PowerShell scripting). Since the code is custom, a high degree of testing (whether automated or manual) is necessary to ensure migrated results meet user and organizational expectations.
More organizations than ever are making the move from Slack to Microsoft Teams in recent years. We’ve facilitated hundreds of successful migrations varying in size and complexity by using our in-house migration tools. That said, every once in a while, we come across a migration that’s a little more specialized than others. Read on to learn how we approached our first Slack to Microsoft Teams migration as a service.
A recent project concerned a client who wanted to migrate conversations from private channels in Slack to Microsoft Teams. Straightforward enough, right? Well, while the majority of our clients prefer exporting conversations in Slack channels as HMTL files, this format didn’t quite fit the use requirements of the client…