9/20/2018 8:02 PM Meet up with the Office 365 networking team and share your onboarding experiences Jeff Mealiffe, Paul Andrew, Paul Collinge, Sameer Sitaram Office 365 Team, Microsoft © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Meet the Office 365 networking team 9/20/2018 8:02 PM Meet the Office 365 networking team Jeff Mealiffe is a Principal Program Manager on the Office 365 engineering team. He works directly with many customers to help work through challenges around security & connectivity, and continues to manage virtualization and performance guidance for on-premises Exchange deployments. Paul is a Senior Program Manager at Microsoft working on Office 365 cloud networking, network connectivity and performance. He works on the Office 365 IP's and URLs surface area, ExpressRoute for Office 365, and Office 365 connectivity with network device partners. Paul has worked as a program manager and product manager at Microsoft for over 12 years and as a developer prior to that. Paul holds an MBA from the University of Washington and a Bachelor of Technology from Massey University in New Zealand. Paul Collinge is a Senior Program Manager in the Office 365 Product Team, specializing in network connectivity and performance. Sameer is a Product Marketing Manager in Office 365 focused on networking, and strategies for complex organizations. © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM Networking Trends SaaS disrupts traditional datacenter-to- datacenter connectivity models Security controls move from network into applications and the cloud Internet to the Cloud becomes shorter Connectivity itself is moving to the Cloud ISP 2 ISP 3 ISP 4 ISP 1 Internet ISP 2 ISP 3 ISP 4 ISP 1 Internet © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

  Office 365 connectivity principles Identify and differentiate Office 365 traffic using Microsoft published endpoints data Egress Office 365 data connections as close to the user as practical with matching DNS resolution Avoid network hairpins and optimize connectivity directly into the nearest entry point into Microsoft network Assess bypassing proxies, traffic inspection devices and duplicate security which is available in Office 365 aka.ms/o365ip Head Office Branch Office ISP Microsoft Network  Microsoft Network ISP  Internet

“What are your biggest pain points with 9/20/2018 8:02 PM “What are your biggest pain points with Office 365 connectivity today?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “How are you managing high availability to minimize outage risks for your end users?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “How would you characterize the performance of Office 365 workloads for your end users?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “How are you using the IP Addresses and URL’s data we provide? How should we improve?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “Do you have a security policy that governs internet access? How does that security policy treat Office 365 bound traffic?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “What security features in Office 365 would let you treat Office 365 as a trusted destination?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “Did your company choose ExpressRoute? Why did you choose it over using the internet to connect to Office 365?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

“Question 9 Lorem Ipsum ” 9/20/2018 8:02 PM “Question 9 Lorem Ipsum ” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

“Question 10 Lorem Ipsum ” 9/20/2018 8:02 PM “Question 10 Lorem Ipsum ” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM “Given the guidance and future direction shared this week, are we on the right track?” © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

9/20/2018 8:02 PM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Appendix

Audience questions (remove from slide) Why can’t we just have one namespace for Office 365? Does ExpressRoute ever make sense for Office 365? Your guidance is to avoid break/inspect of Office 365 traffic, but I can’t do that for everything – can you expand on the guidance and explain the impact of break/inspect?