Infrastructure Best Practices for Teams Remote Workers

Notes de l'éditeur

• #6: So Teams is available in 181 countries and in 25 languages. To achieve this we are currently deployed in three regions around the world, this includes the Americas, EMEA, and APAC. We have failover data centers in region. It is also worth pointing out that chat data at rest stays in region based on tenant affinity. So if you sign your subscription for O365 in a country like France you can be assured that your data at rest stays in EMEA and falls under the laws of the EU. Files in Teams are stored in country for Australia Canada, India, Japan and the united states. We also honor the EU model clauses.
• #9: Unofficial, non-trademarked acronym and pneumonic.
• #15: 130,000 miles of fiber optic cable. 160 global network point-of-presence locations. 3,500+ ISP peers. The goal of this image is not solely about what the dots mean, but to show that there are Office 365 and Azure locations across the globe and that Microsoft operates one of the most performant networks on the planet: https://docs.microsoft.com/en-us/azure/networking/azure-network-latency
• #18: Customer was automotive manufacturer. Customer was moving off Avaya PBX, plus they were moving into a new Office HQ building. Key concepts: No default route on network – OSPF only shared/advertised routes to internal networks. If you needed to egress to Internet, you had to go through proxy. Proxy Service was “cloud based” (Zscaler) built by GRE tunnel from local customer office to in-region Zscaler node Additionally, public DNS recursion was not available internally – via Proxy Service only. ICMP was blocked on network, as well - This caused all sorts of issues and made troubleshooting very difficult.
• #20: Primary Zscaler node was in Washington DC, so egress was always expected there. GRE tunnel from local customer office to in-region Zscaler node provided connectivity Because Zscaler was not set up for “advanced firewall” feature, all traffic was forced to TCP Zscaler peering then sent traffic back to NYC, even though a closer MSFT POP was available.
• #21: Once routes and ports were opened via Zscaler “advanced firewall” feature, testing via the MSFT tool became viable. Results weren’t overly great.
• #22: Movement towards a true local egress model – where traffic did NOT hit Zscaler at all – showed definite improvement.
• #23: The change to local egress and proxy bypass, however, was significant.
• #29: The way in which organizations work has evolved. Both work styles and the workforce are becoming more and more diverse. There are several trends – and challenges – that we’re seeing.​  ​ [MOBILE AND SOCIAL]​ When people collaborate today, they leverage social tools– 45% use social technologies in their day-to-day work3.​ Users also work across more devices - in the past five years, the number of devices per user has increased 400%.4 The mobile phone has completely changed how we communicate and work. Many users live on their phone. In addition, people use different apps and services resulting in them having to jump between different experiences during the day.​  ​ [DIVERSE AND GLOBAL]​ The workforce itself is more diverse. For the first time, there are five generations together in the workplace, – all with different background in technology and different expectations about communication and collaboration tools. For example (hold up phone if available), some people are comfortable chatting on a phone, others prefer e-mail, or face to face. ​ Teams are increasingly geo distributed. Employees are no longer necessarily in the same office, let alone the same time zone. Per IDC, 72.3 percent of employees will be working remotely by 20205, making it more challenging to have face-to-face conversations. There’s a greater need to enable communications and collaboration – regardless of geography.  ​  ​ [TEAM-BASED AND COLLABORATIVE]​ There is also a movement towards transparency and inclusivity in how decisions are made. Organization structures are becoming more flat. People are on twice as many teams as they were five years ago.1 ​ And those teams are dynamic. It's rare that people don’t change on a multi-month project. And when someone leaves, the first step is for all to go through their e-mail to find the information needed to get the new person up to speed.​ Being on more teams has also led to a dramatic increase in the amount of collaboration. The new way of work is team-based and collaborative. Workers report that 80 % of their time at work is spent collaborating.2 (i.e. in meetings, calls)​  ​ [probe if the customer is experiencing some of the above to personalize the presentation]​ ​ [MAIN POINT TO LAND]​We built Microsoft Teams in response to these communication and collaboration trends in the modern workplace.​We’ve seen that Teams really thrive when information is shared in an open and transparent way and when people with diverse workstyles can access information easily. We’ve built Teams to enable that. ​ We’ve also seen that there is no one size fits all. We’ve built teams to be flexible and so that you can customize and personalize it based on the needs of your team.​ What happens when you don’t provide tools to support these new workstyles? End users simply download the consumer grade tools to do the immediate task at hand. This creates friction for end users as they have to manage multiple logins and move between different experiences, and it creates risk for the organization as shadow IT develops. ​ [This video illustrates the problem with fragmented, best of breed solutions and is included for your background knowledge only, not to show in the customer meeting.]​ 1  2009, 2014 US IW Survey​ 2 How much workplace collaboration is too much? ​ 3 2017, McKinsey Global Institute Survey Advanced social technologies and the future of collaboration​ 4 Survey Reveals Skyrocketing Usage and Growing IT Maturity in Enterprise Mobility ​ 5 IDC Forecasts U.S. Mobile Worker Population to Surpass 105 Million by 2020​