1 / 38

Learn about the Microsoft Global Network and best practices for Office 365 Connectivity

Learn about the Microsoft Global Network and best practices for Office 365 Connectivity. Paul Andrew—Senior Program Manager Office 365 Paul Collinge —Senior Program Manager Office 365. BRK1005. Office 365 connectivity principles.

walsh
Download Presentation

Learn about the Microsoft Global Network and best practices for Office 365 Connectivity

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Learn about the Microsoft Global Network and best practices for Office 365 Connectivity Paul Andrew—Senior Program Manager Office 365 Paul Collinge—Senior Program Manager Office 365 BRK1005

  2. 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’s network Assess bypassing proxies, traffic inspection devices and duplicate security which is available in Office 365 ISP Microsoft Network Head Office  Branch Office ISP  aka.ms/o365ip ISP Internet Microsoft Network

  3. Datacenter andNetwork Layout

  4. Global, hyper-scale, enterprise-grade infrastructure Global regions AsiaPacific Australia Canada Europe,Middle East and Africa India NorthAmerica South America United Kingdom Japan South Korea Announced France South Africa Sovereignregions USGovernment China operated by21Vianet Germany

  5. Microsoft’s global network – not the Internet!

  6. Microsoft Global Network • Azure network team manage this which is one of the top two networks in the world. • Very high bandwidth, low latency, failover capable links • Tens of thousands of route miles of privately owned dark fiber Microsoft’s fiber optic network could stretch to the moon and back, three times over. • Multi Terabit connections DC-DC & DC-Internet • Peer with over 2500 ISPs globally in 38 countries • Identified by msn.net router names (for most routers) • Optimized to get your traffic to it’s destination efficiently • Aim is for customers to get onto this network as quickly as possible.

  7. Office 365 peering locations aka.ms/8075

  8. Test for optimal routing & peering onto MS Global Network UK – Peer in London in 26ms 1 4 ms 3 ms 4 msbthub [192.168.1.254] 4 28 ms 26 ms 27 ms 31.55.187.180 5 24 ms 24 ms 24 ms core2-hu0-8-0-5.southbank.ukcore.bt.net [195.99.127.186] 6 26 ms 24 ms 25 ms peer2-et-10-1-0.telehouse.ukcore.bt.net [195.99.127.7] 7 26 ms 26 ms26 ms195.99.126.55 8 36 ms 34 ms35 msae12-0.lon04-96cbe-1a.ntwk.msn.net [207.46.44.162] 9 37 ms 36 ms 37 ms be-9-0.ibr01.dbb.ntwk.msn.net [104.44.4.134] 11 35 ms 34 ms 36 ms ae1-0.db3-96c-3a.ntwk.msn.net [204.152.141.79] 13 34 ms 34 ms 34 ms 104.146.132.25 France – Peer in Paris in 8ms 1 8 ms 2 ms 1 ms 192.168.0.1 2 * 7 ms 7 ms 10.95.160.1 3 6 ms 6 ms 6 ms hlr1rj-ge-0-1-6.100.numericable.net [80.236.6.14] 4 8 ms 18 ms 10 ms ip-254.net-80-236-0.static.numericable.fr [80.236.0.254] 5 8 ms 8 ms 9 ms ip-249.net-80-236-0.static.numericable.fr [80.236.0.249] 6 11 ms 9 ms 10 ms 172.19.132.146 7 9 ms 10 ms8 msae7-0.par02-96cbe-1b.ntwk.msn.net [207.46.41.224] 8 8 ms 8 ms 9 ms ae3-0.pra-96cbe-1b.ntwk.msn.net [204.152.141.246] 9 21 ms 21 ms 22 ms be-6-0.ibr02.amb.ntwk.msn.net [104.44.4.230] 10 20 ms 18 ms 20 ms ae75-0.ams04-96cbe-1b.ntwk.msn.net [104.44.9.239] 11 21 ms 18 ms 19 ms 104.44.80.139 12 * * * Délaid’attente de la demandedépassé. 13 20 ms 20 ms 20 ms 13.107.6.151 Florida – Peer in Miami in 24ms 1    30 ms     3 ms    14 mszeus.olympus.home [192.168.0.1]   2    11 ms    14 ms    14 ms  10.100.16.1   3    15 ms    15 ms    16 ms  ten0-6-0-0.tamp20-car2.bhn.net [71.44.1.106]   4    16 ms    18 ms    19 ms  ten0-8-0-6.tamp27-car2.bhn.net [72.31.211.158]   5    16 ms    18 ms    19 ms  72-31-6-190.net.bhntampa.com [72.31.6.190]   6    16 ms    19 ms    19 ms  hun0-3-0-7.tamp20-cbr1.bhn.net [72.31.3.140]   7    21 ms    19 ms    24 ms  10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66.109.6.96]   8    28 ms    26 ms    28 ms  0.ae0.pr0.mia00.tbone.rr.com [66.109.1.89]   9    24 ms    23 ms    24 ms  66.109.7.238 10    24 ms    24 ms24 msae9-0.mia-96cbe-1b.ntwk.msn.net [104.44.225.167] 11   126 ms   129 ms   129 ms  be-75-0.ibr02.atb.ntwk.msn.net [104.44.224.230] 12   131 ms   129 ms   128 ms  be-3-0.ibr01.bn1.ntwk.msn.net [104.44.4.49] 13   130 ms   129 ms   128 ms  be-1-0.ibr02.bn1.ntwk.msn.net [104.44.4.63] 14   130 ms   129 ms   129 ms  be-3-0.ibr02.was05.ntwk.msn.net [104.44.4.26] 15   135 ms   134 ms   133 ms  be-4-0.ibr02.nyc04.ntwk.msn.net [104.44.4.29] 16   120 ms   119 ms     *     ae8-0.lon04-96cbe-1b.ntwk.msn.net [104.44.5.29] 17   123 ms   124 ms   124 ms  ae11-0.lon04-96cbe-1a.ntwk.msn.net [207.46.44.154] 18   131 ms   127 ms   132 ms  be-9-0.ibr01.dbb.ntwk.msn.net [104.44.4.134] 20   130 ms   128 ms   125 ms  ae2-0.db3-96c-3b.ntwk.msn.net [204.152.141.81] 22   126 ms   128 ms   129 ms  104.146.132.25 Scotland – Peer in NY! in 87ms 1 <1 ms <1 ms <1 ms 10.201.100.1 2 <1 ms <1 ms <1 ms 10.201.0.1 5 14 ms 14 ms 15 ms ABC-e-0-0-0-0.londonuk5.poorlypeeredISP.net [*.*.157.174] 6 16 ms 15 ms 15 ms AB2-e-0-0-2-0.londonuk1.poorlypeeredISP.net [*.*.157.113] 7 83 ms 83 ms 83 ms AB1-tengig-0-7-0-0.newyork.poorlypeeredISP.net [*.*.196.121] 8 82 ms 82 ms 82 ms AB2-e-9-0-1.jfk2.poorlypeeredISP.net [*.*.99.65] 9 82 ms 83 ms 82 ms ab1-e-10-1-1.jfk2.poorlypeeredISP.net [*.*.99.214] 10 82 ms 82 ms 82 ms nyc-brdr-02.poorlypeeredISP.net [*.*.26.101] 11 82 ms 82 ms 82 ms nyc-edge-04.poorlypeeredISP.net [*.*.134.1] 12 85 ms 86 ms87 ms  be-4-0.ibr02.nyc04.ntwk.msn.net [104.44.4.28] 14 141 ms 143 ms 145 ms xe-7-3-0-0.lts-96cbe-1a.ntwk.msn.net [207.46.43.45] 15 149 ms * * xe-9-1-1-0.ams-96c-1a.ntwk.msn.net [207.46.42.135]

  9. What’s an expected Network Latency? • Consider the client, customer network, Internet, and the Microsoft 8075 network • Within region expect <100ms total. Many services use connections to a node within region for service delivery or optimization, even if the data is in another. Therefore the regional latency figure, optimized connectivity to Microsoft’s backbone and the edge nodes are the key data points

  10. Exchange Online connectivity

  11. Connecting to Exchange Online Edge Servers CAFÉ Servers Edge Servers Outlook Web Access The internet CAFÉ Servers Firewall Edge Servers Exchange Data Store Microsoft Global Network Internet Service Provider • Today for the majority of traffic: • OWA connects to Edge over HTML/HTTP • Outlook Client connects to CAFÉ over MAPI/HTTP Edge Servers CAFÉ Servers Outlook Client

  12. Connecting to Exchange Online – Architecture • App discovery • Name resolution • Connect to front end server outlook.office365.com Authoritative DNS Servers cnames Autodiscover Server Authoritative DNS Servers Local DNS Server Microsoft internal autodiscover.microsoft.com Exchange Front End Server (CAFÉ) Rack VIPs of Front End Server load balancers Forwarding DNS Server Exchange Mailbox Server • Autodiscover, DNS, CAFÉ, Mailbox Server • All highly available and scalable layers • CAFÉ servers will failover if unavailable • User mailboxes replicated to four servers (one primary) • Configure DNS correctly and test latency to CAFÉ servers Outlook Client NOTE: OWA not shown

  13. Geo-DNS with Geo IP tables Authoritative DNS Servers Authoritative DNS Servers outlook.office365.com Global Traffic Manager DNS Servers other cnames NOTE: Autodiscover and back end servers not shown outlook-au.office365.com IP Addresses Exchange Front End Server (CAFÉ) Rack Local DNS Server • Local DNS server must be configured correctly and near to users • DNS finds nearby front end servers by geography • Use tracert and ping to measure latency to CAFÉ servers Outlook Client

  14. Geo-DNS with Anycast IP DNS Server DNS Servers DNS Server Anycast IP outlook.office365.com DNS Servers other cnames outlook.ms-acdc.office.com IP Addresses Exchange Front End Server Rack Local DNS Server • Parallel Geo-DNS system for HA. Expect to see CNAME differences • Anycast IP locates a Microsoft DNS server • Returns nearby Front End servers • Troubleshoot if front end server is too far away Outlook Client

  15. Outlook Client latency requirements • Use Outlook cached mode not online mode • Minimize latency • Seek to improve if it indicates cross region connections (>300mS) • Non-cached operations with high latency will be slow • Search • Opening other people calendars • Free / busy lookup • Manage rules and alerts • Exchange online archive • Emails departing the outbox

  16. Outlook Client DNS requirements • For DNS errors or network latency talk to the service owners • DNS Configuration • Local DNS server secured and with root hints configured • Alternatively use a forwarder from the network provider • Either should be near the users • Avoid global DNS forwarder providers • The eDNS extension in OpenDNS is not supported

  17. DNS Lookup & Traceroute DEMO

  18. Skype for Business Online Network Connectivity

  19. Skype for Business critical networking elements Client connectivity on all network connections (LAN, Wi-Fi) IP endpoint and ports open (Preferably UDP) Bandwidth Latency, jitter, packet loss, packet reorder Hybrid on-premises servers connectivity Identify all inbound network flows Define security and routing for each

  20. Call Connectivity Model • Signalling traffic (SIP) • Connects client to a pool in the location of the tenant • Informs the client of the relay to use for media services – TCP Port 443 • For media traffic the client attempts multiple connection methods simultaneously when starting media • [BEST] UDP Direct - Ports 3478, 3479, 3480, & 3481, (Optional)50,000-59,999 • [BETTER] TCP Direct – Port 443 • [OK] TCP via Proxy PAC • Best method that gets a response is used

  21. DNS Mapping Also required: • Authentication and identity connectivity • Portal and shared connectivity • Details at: http://aka.ms/o365ip

  22. 1-2-1 call media path (direct connectivity) Media Path Wired / Wireless Corporate user Corporate user Home user Corporate network ISP / Internet / Express Route Provider Azure network/ SfB DC Wired / Wireless Home network ISP / Internet

  23. Current Skype Peer to Peer calls on different networks (NAM Tenant) Media Relay

  24. Future Skype Peer to Peer calls on different networks (NAM Tenant) Transport Relay Media Relay

  25. Network Performance Requirements For optimal Skype for Business media quality, the following network performance requirements should be met: Media Quality and Network Requirements at: https://aka.ms/media-quality-and-network-connectivity

  26. Measuring & Monitoring Network Performance Use Skype for Business Network Assessment tool https://aka.ms/sfbtool Target Skype’s world wide Anycast IP – 13.107.8.2 (global.tr.skype.com) Assess both your network and connections to Office 365 Measures a 17 second conference call Assess with enough data to cover all network traffic patterns Assess for >= One working week Measurement every 5 minutes Use the 90th percentile value

  27. Skype for Business Network Assessment Tool Demo

  28. SharePoint Online connectivity

  29. SharePoint Online – Client Connectivity Mechanism • Now uses Anycast to connect to the same IP globally • DNS lookup for tenantname.sharepoint.com returns 13.107.6.151 • Multiple edge servers globally configured as that IP • BGP route advertisement and least cost routing is used • Finds the nearest SharePoint enabled Edge node to connect • TCP and SSL connections terminated, optimized and connected to the SharePoint front end server on an existing session

  30. SharePoint Online Connection Process Previous Unicast Model EMEA SPO Client • User requests directed to the active Microsoft datacenter hosting the tenant • TCP connections perform proportional to RTT • SPO content x-geo • APAC user accessing data in an EU datacenter • Poor connectivity to SPO datacenters within a geo TCP 443 Connection to the IP address SPO NAM 3 4 1 DNS Lookup tenantname.sharepoint.com Unicast IP address of active SPO tenant location 2 DNS Connected

  31. SharePoint Online Connection Process EMEA SPO Edge Nodes New Anycast Model EMEA SPO Client • Connects the client to the secure, highly available, globally distributed edge network • Terminates SSL connections closer to the client • Optimizes connections at the edge to rectify sub-optimal settings from the customer side • Re-uses connections between the edge and SharePoint Online TCP 443 Connection to the Anycast IP address SPO NAM 3 4 1 DNS Lookup tenantname.sharepoint.com Anycast IP address of tenant 2 Connected DNS

  32. Bringing SharePoint Online to you United Kingdom TCP and SSL session initiation UK User edge node TCP and SSL session initiation Encrypted hot connection United States edge node US User

  33. File Performance 55% 40% 2x-5x 3x-10x Faster opening Word documents in Office Online Faster opening PowerPoint documents in Office Online Increase in upload speeds Increase in download speeds

  34. Connection to the same tenant around the globe UK – Peer in London – Terminates in Amsterdam tracert paulcoll.sharepoint.com Tracing route to b-0001.b-msedge.net [13.107.6.151] over a maximum of 30 hops: 1 4 ms 4 ms 4 msbthub [192.168.1.254] 4 12 ms 9 ms 10 ms 31.55.187.188 5 11 ms 9 ms 10 ms 195.99.127.26 6 10 ms 13 ms 11 ms peer1-et-10-1-0.telehouse.ukcore.bt.net [62.172.103.23] 7 11 ms 11 ms 11 ms 195.99.126.57 8 18 ms 17 ms 19 ms be-61-0.ibr01.lon30.ntwk.msn.net [104.44.9.242] 9 18 ms 22 ms 18 ms be-2-0.ibr01.lts.ntwk.msn.net [104.44.5.39] 10 19 ms 18 ms 18 ms be-5-0.ibr01.amb.ntwk.msn.net [104.44.4.232] 11 16 ms 17 ms 19 ms ae65-0.ams04-96cbe-1a.ntwk.msn.net [104.44.9.235] 16 17 ms 19 ms 17 ms13.107.6.151 Trace complete. Sydney – Peer in Sydney –Terminates in Sydney (3G connection) tracert paulcoll.sharepoint.com Tracing route to b-0001.b-msedge.net [13.107.6.151] over a maximum of 30 hops:   1     4 ms     *       13 ms  Windows-Phone.mshome.net [192.168.137.1]   4    43 ms    30 ms    32 ms  10.247.113.13   5    46 ms    59 ms    35 ms  10.246.133.254   6    43 ms    32 ms    36 ms  120.21.253.249 11    83 ms    51 ms    54 ms  104.44.12.58 12    48 ms    40 ms    45 ms  ae1-0.syd03-96cbe-1b.ntwk.msn.net [204.152.140.113] 15    64 ms    39 ms    39 ms13.107.6.151 Trace complete. Charlotte – Peer in Atlanta – Terminates in Ashburn Tracing route to b-0001.b-msedge.net [13.107.6.151] over a maximum of 30 hops:   1     2 ms     3 ms     1 ms  192.168.0.1   2     2 ms     2 ms     2 ms  107-140-128-1.lightspeed.chrlnc.sbcglobal.net [107.140.128.1]   3     3 ms     5 ms     3 ms  99.144.25.186   4     5 ms     5 ms     3 ms  99.133.205.114   5     7 ms     7 ms     4 ms  12.83.102.137   6    10 ms    10 ms    16 ms  12.122.154.134   7     9 ms     9 ms     8 ms  ggr1.attga.ip.att.net [12.122.141.105]   8    11 ms     9 ms    14 ms  206.121.10.30   9    10 ms     9 ms     8 ms  ae9-0.atb-96cbe-1b.ntwk.msn.net [104.44.224.190] 10    23 ms    25 ms    23 ms  be-74-0.ibr02.atb.ntwk.msn.net [104.44.8.102] 11    23 ms    22 ms    24 ms  be-3-0.ibr02.atb.ntwk.msn.net [104.44.4.48] 12    24 ms    24 ms    23 ms  be-1-0.ibr01.cnr02.bn6.ntwk.msn.net [104.44.4.158] 13    25 ms    23 ms    22 ms  be-3-0.ibr02.bn1.ntwk.msn.net [104.44.4.27] 14    22 ms    22 ms    23 ms  ae71-0.bl2-96c-1b.ntwk.msn.net [104.44.8.173] 19    22 ms    22 ms    21 ms13.107.6.151 Trace complete

  35. Wrap up Office 365 Connectivity • BRK3041 Connectivity Strategy earlier today • BRK3051 Connectivity Planning on Thursday • BRK3387 Connectivity meet-up on Friday Workload Details Sessions • Skype for Business BRK4004 on Thursday & BRK3029 now • SharePoint Online BRK3257 on Thursday • Exchange Online BRK4029, was on Monday

  36. Please evaluate this session Phone:download and use the Microsoft Ignite mobile app https://aka.ms/ignite.mobileapp Fromyour Please expand notes window at bottom of slide and read. Then Delete this text box. PC or tablet: visit MyIgnitehttps://myignite.microsoft.com/evaluations Your input is important!

More Related