While Microsoft Teams offers a wider scope and array of possibilities, also it requires thorough preparation: consequently, companies find it challenging to roll out. During this session, we learned what lies ahead, gained insights on the optimal road and potential pitfalls as we move towards Microsoft Teams.
The presentations from the event are available, exclusively for Beltug members (after login).
Microsoft Teams – vision and customer roadmap
Nathalie Regniers, Senior Product Marketing Manager at Microsoft gave an overview of the tools in Microsoft Teams and how these features will optimize smart collaboration tools. In addition to the collaboration and communication features, Teams will also enable direct routing - so that calls originating from the user’s own provider will connect to Teams.
Nathalie showed us a complete overview of all the different features in Teams (see slide 6): explaining that Microsoft is aiming to offer a universal toolkit for teamwork with O365, including Yammer, SharePoint, Outlook and the different office apps.
However, change management is crucial when moving from Skype for Business to Teams, Nathalie emphasised. 'Advocate' colleagues can give employees a bit of guidance, drawing their attention to interesting features and walking them through the tool. (Slide 13 shows resources for companies to find their way through the new tool.)
To conclude, Nathalie answered the audience’s numerous questions - about security, working with overseas areas (with particular legislation), potential migrations, and so on.
The path from legacy unified communications to modern collaboration
Next, Jonathan Beesoon, Senior Solutions Architect at Dimension Data, took the floor. He explained how to move from the legacy UC (Unified Communications) to modern collaboration. Whereas SfB is mainly about communicating amongst colleagues and (external) parties, Teams is about collaboration and even involves AI. Within the broader scope of Teams, Jonathan explained, the tool comes with a few challenges.
Jonathan sees 5 steps in engaging people into Teams:
When moving from SfB, typically a company first plans the journey towards Teams, onboards and starts using Teams, and runs Teams and SfB side by side. Finally, they drop SfB. Jonathon reassured the audience that many 'legacy' features can coexist during that process with the new Teams features.
Stay aware of the team lifecycle, he highlighted (slides 25 and 26). From there on, a workflow will follow its way.
Next, you need to think about policies (naming, size for storage, etc), yet also about the end of a team - what is the expiry date? And you need policies on 'trashing' or 'archiving'.
To wrap up, Jonathan summarised the advised approach:
Access to more information about this topic and/or to download the paper is easy and fast, but exclusively for Beltug members (just login to get access).
Beltug gathers a lot of information. Here you find the advantages of Beltug membership
The Beltug Team
Click here to login