{"id":79940,"date":"2020-10-21T09:42:44","date_gmt":"2020-10-21T08:42:44","guid":{"rendered":"https:\/\/loopup.com\/?p=79940"},"modified":"2022-06-23T09:28:14","modified_gmt":"2022-06-23T08:28:14","slug":"reflections-from-microsoft-ignite-2020-whats-new-and-improved-for-teams","status":"publish","type":"post","link":"https:\/\/loopup.com\/us\/resource-center\/blog\/reflections-from-microsoft-ignite-2020-whats-new-and-improved-for-teams\/","title":{"rendered":"Reflections from Microsoft Ignite 2020: What\u2019s new and improved for Teams?"},"content":{"rendered":"\n

Microsoft\u2019s annual Ignite conference is usually THE place to find out what new software capabilities and changes are coming over the next 6-12 months. This year, Microsoft held a supersized virtual event rather than their usual giant in-person event in the USA. Running across multiple time zones, the sessions were replayed to cater for a worldwide audience. The event did not disappoint, and it was pleasing to see Microsoft lifting the lid on many new features and enhancements for Teams.<\/p>\n\n\n\n

With so much content coming from Ignite across O365, M365 and their other technologies, each year, Microsoft publish a book of news<\/a> that covers all its forthcoming developments on their website.<\/p>\n\n\n\n

In this post, we\u2019re going to focus on some of the major announcements relating to Teams and what they might mean from a Teams Telephony<\/a> point of view\u2026<\/p>\n\n\n\n

Upping the ante on \u2018survivability\u2019<\/h3>\n\n\n\n

In a session<\/a> on \u2018Teams Calling Made Simple\u2019, Microsoft announced its plan to bring an element of \u2018survivability\u2019 to the Teams service. Microsoft is introducing a \u2018Survivable Branch Appliance\u2019, where a gateway (a Session Border Controller or SBC) physically deployed onsite, runs a micro version of the Teams software that will allow Teams to register and process calls in a limited capacity if an internet connection is not available.<\/p>\n\n\n\n

\"Survivable<\/figure>\n\n\n\n

Up until now, an internet connection was required to use the\nTeams client and make or receive calls, which can cause issues when there are\nno resilient internet links. This isn\u2019t necessarily as bad as it sounds, because\nas more and more workloads are migrating away from being run or stored locally,\n there are potentially bigger problems\nthan being able to maintain a dial tone to your phone or client. However, it\u2019s not\nideal, especially in today\u2019s world where remote connectivity is becoming the\nnorm, rather than the exception. Expectations around service resilience are\nhigh.<\/p>\n\n\n\n

Previously, this issue could be solved with multiple\ninternet connections or by running critical users over mobile data connections.\nMicrosoft\u2019s Teams survivability option might suggest that this issue was\nfrequently experienced by Microsoft\u2019s users, so they needed to come up with a\ndifferent solution. <\/p>\n\n\n\n

It will be interesting to see how this solution has evolved from the Cloud Connector Edition (CCE) appliance that was used to connect SBCs to the Skype for Business Online service. The CCE had a similar model where virtual machines ran on the server board inside compatible gateways but was complex and frustrating to update and manage.<\/p>\n\n\n\n

We can help weigh up the pros and cons as they become apparent, but some initial thoughts around issues for consideration include:<\/p>\n\n\n\n

  • What infrastructure changes might be required?
    • DNS entries?<\/li><\/ul>
      • Firewall \/ DMZ requirements?<\/li><\/ul><\/li>
      • How will the Teams clients find the survivable branch\nappliance?
        • Auto discover via DNS or some sort of in-band\nnotifications?<\/li><\/ul><\/li>
        • What configuration will be required in the Teams\nAdmin Console?<\/li>
        • What about any other workloads?<\/li>
        • Will it support all Teams-certified devices?<\/li><\/ul>\n\n\n\n

          Upgrading the calling interface<\/h3>\n\n\n\n

          Teams is one of the most rapidly evolving products that\nMicrosoft has produced, so it is not uncommon to see frequent modifications and\nimprovements to the user interface (UI). This year, we have already seen the introduction\nof the pop-out chat, along with the new meeting experience that makes\nmultitasking easier while using Teams. And it doesn\u2019t stop there – we are expecting\na revamped calling experience which should significantly enhance usability.<\/p>\n\n\n\n

          Currently, the \u2018calls\u2019 tab inside Teams can look a little sparse, with lots of unused space. Microsoft is redesigning the format – laying things out in a more logical fashion, giving users a dial-pad, and providing a list of most recent calls and frequently contacted \u2018speed dial\u2019 numbers. For anyone that makes a large number of calls, this streamlined view with one-click calling should make life easier and save a lot of time. <\/p>\n\n\n\n

          \"Teams<\/figure>\n\n\n\n

          Enhancing the meeting experience <\/h3>\n\n\n\n

          Another area that Microsoft has been working hard to improve\nis the meeting experience. Again, this is vital as more businesses have shifted\naway from the office towards working from home. They have already introduced a 3×3\nvideo grid, Large Gallery View and Together Mode, and will soon bring in additional\nfeatures such as extra Together Mode layouts to cater for different sized\nmeetings and custom layouts.<\/p>\n\n\n\n

          Custom Layouts should make a large difference to heavy meeting users, as it will cater for a wider range of meeting scenarios, allowing more flexibility in the way content can be presented in a meeting. For example, the speaker\u2019s video stream can appear \u2018cut out\u2019, as if they are standing in front of the content they are discussing as they would in an in-person meeting. <\/p>\n\n\n\n

          \"Teams<\/figure>\n\n\n\n

          Not only do these changes make the in-meeting experience more dynamic, but they make the experience before and after the meeting more seamless too with a new \u2018Meeting Recap\u2019 option. This makes any content shared during the meeting available, alongside recordings, transcriptions and tracking details of attendees. It\u2019s a big step towards narrowing the gap between the virtual and in-person meeting experience.<\/p>\n\n\n\n

          Ongoing innovation<\/h3>\n\n\n\n

          These interface updates and tweaks might seem small on their own, but together they represent a big jump forwards in the usability and end-user experience. It is amazing that these updates have been developed at a time where both the Teams product and infrastructure have been put under increased strain. But adversity can often be a powerful driver of innovation.

          Although 2020 seems to be the year when Teams has really come into its own, the Ignite conference suggests that much more positive progress is still to come.<\/p>\n\n\n\n

          Ben Lee is a Senior Director in LoopUp\u2019s Consulting Team. He has worked with Microsoft technologies for most of his career, and has led some of the world\u2019s largest UC deployments.<\/em><\/p>\n\n\n\n