Transcript SharePoint Online

Microsoft has invested $15 billion in infrastructure,
building over 100 datacenters and we are
constantly evaluating new locations
Our high-performing network is one of the
top 3 in the world with public peering in 23
countries with 1,500 ISPs.
Our Datacenters support over 20 Million
businesses and over 200 Online Services. Office
365 is sold in 140 markets, 43 languages, and 25
currencies.
Microsoft’s network is one of the three largest in the world
1 million+ servers • 100+ Datacenters in over 40 countries • 1,500 network agreements and 50 Internet connections
*Operated by 21Vianet
Datacenter region is selected based on the customers chosen country
Office 365 Region
Datacenter Locations1
Customers Chosen Country3
Unique Characteristics
Europe
Dublin, Ireland; and Amsterdam, the Netherlands;
Austria; Finland
Located in Europe, Middle East, and Africa
Contractual commitment for location of customer data
at rest
North America
Quincy, WA, Chicago, IL, Boydton, VA, Des Moines, IA
and San Antonio, TX
Located in North America countries except Brazil
Contractual commitment for location of customer data
at rest
Asia Pacific
Hong Kong, Singapore, Malaysia, South Korea, and
Japan
Located in Asia Pacific countries except China, Japan,
Australia, New Zealand, Fiji, and India.
US Government
Iowa and Virginia in the USA
U.S.A. for US Government agencies
Operated by US Citizen employees of Microsoft corp.
Separated from Office 365 commercial servers. Only
available to US government agencies.
Brazil2
Sao Paulo State and San Antonio
Brazil
Passive for data resiliency only in San Antonio
China
Shanghai (operated by 21 Vianet)
China
Japan
Saitama Prefecture and Osaka Prefecture, Japan
Japan
Australia
New South Wales and Victoria, Australia.
Australia, New Zealand, and Fiji
India
Mumbai, Pune and Chennai
India
Canada (future)
Toronto and Quebec City, Canada. Planned for 2016
Canada
1Not
all datacenter locations are disclosed. Microsoft has 100+ world wide datacenter locations. All regions have multiple datacenter locations.
CRM Online services do not use datacenters located in Brazil.
3The customers chosen country is set when the customers administrator enters during the initial setup of Office 365 services. This selects the primary storage
location for the customers data, the customers sales tax treatment, and the specific services that are available.
2Dynamics
New Office 365
datacenter
regions
Japan launched December 15, 2014
Australia launched March 31, 2015
India launched October 12, 2015
Canada in H1 of CY2016
New datacenters
in existing regions
We do also add new datacenters to existing regions for
resiliency and capacity planning purposes.
Recently Austria and Finland datacenters were added to the
Europe region.
Malaysia, South Korea, and Japan are being added to the
APAC region.
http://www.peeringdb.com/view.php?asn=8075
Brisbane
Australia
Kuala Lumpur
Malaysia
Los Angeles
USA
Melbourne
Australia
Amsterdam
Netherlands
Miami
USA
Perth
Australia
Auckland
New Zealand
New York
USA
Sydney
Australia
Wellington
New Zealand
Palo Alto
USA
Vienna
Austria
Moscow
Russia
San Jose
USA
Luxembourg
Luxembourg
Singapore
Singapore
Seattle
USA
Sao Paulo
Brazil
Stockholm
Sweden
Montreal
Canada
Zurich
Switzerland
Toronto
Canada
Taipei
Taiwan
Prague
Czechoslovakia
London
UK
Paris
France
Ashburn
USA
Frankfurt
Germany
Atlanta
USA
Hong Kong
Hong Kong
Boston
USA
Dublin
Ireland
Chicago
USA
Milan
Italy
Dallas
USA
Turin
Italy
Denver
USA
Tokyo
Japan
Honolulu
USA
Seoul
Korea
Las Vegas
USA
•
•
•
•
•
Site data is published at
http://www.peeringdb.com/view.ph
p?asn=8075
Some cities have multiple peering
points
Peering locations may be on-net
or off-net
Peering may involve physical
connection and/or routing
advertisements
Data as of July 2014 is subject to
change
Outlook, Outlook Web Access, OneDrive for Business
Native clients on
tablets, PCs,
& desktops
Native clients
on mobile devices
Browser-based
Clients also cache
with HTML5
Browser-based
mobile clients
Office 365 offers a wide variety of options across devices for customers to access the service
OWA uses HTML 5 Offline Application Caching if enabled in Offline Settings
Server
workloads
Microsoft
network
Microsoft
edge nodes
Internet
peering and
routing
Content
delivery
network
Customer
Internet
connection
Rich client
applications
Recommended for over 25 user sites
Exchange Online
http://aka.ms/tune
•SharePoint
Similar toOnline
on-prem
• Estimates rely upon on-prem baselines
• HTTPS views of webpages, uploads/downloads of content
Onlinemode reduces impact and provides for latency tolerance (<325
•Lync
Cached
• Document editing with Office Web Apps or Office
mSec)
•Use
IMyour
is bursty,
latency
tolerant,
and very small
pilot
to
predict
new requirements
• Bursty,
but latency
tolerant
• Perfmon,
Netmon,
top, etc. to baseline
Voice
uses
RTAudio
• Without
baseline,
no
real way to estimate
Baseline bandwidth requirements
before Office 365
• 50kbps
low, 80kbps high,
autodetermination
• Definite
advantages
to Outlook
2013 SP1
•• Netmon
to
baseline baseline for pilot users
Measure
bandwidth
• Video depends upon resolution
•• Will
ramp upfor
as4000kbps
morebandwidth
content
is required
loaded
into
SharePoint,
OneDrive,
Extrapolate
total
forresolution
your workload
• 280kbps low,
high, dependent
upon
for Business
• OneDrive
Desktop
depends
upon upgrades
desktop resolution
Assumes sharing
enough
time to order
if needed
• Peer-to-Peer
versus
Client-Server
Start with at least
20%
head room
• Evaluate options to conserve bandwidth
Migrations


SMTP Traffic
After hours test mailbox
 Baseline SMTP in and out
migrations to baseline
at the existing edge
• Bandwidth consumed
 Production will increase
• Average migration rate
 2*baseline in +
For a migration event, the
2*baseline out
total bandwidth consumed  During coexistence,
is X X>(MB+MB1+…MBx)
between on-prem and

Will go away at end of
migrations

HTTPS, as inbound requests
(downloads from the
hybrids)
Office 365 will add
additional
Administration

Traffic is negligible




HTTPS traffic
Latency tolerant
Bursty and intermittent
DirSync noticeable only
on first run





HTTPS traffic
Only deltas after initial sync
Every 3 hours (+ runtime)
Variable based on deltas
More during the day than at
night
Microsoft Datacenter
Office 365
Services on
ExpressRoute
Customer Site 2
Office 365
Services Require
Internet
Customer Site 1
MPLS VPN
WAN
Customer
Datacenter
Public
internet
Internet Co-lo
Azure services
Alternate connection
Pricing plans:
Unlimited data plan
Metered data plan
Office 365 workloads on ExpressRoute
Office 365 workloads that require
Internet
Exchange Online & Exchange Online Protection
Yammer
SharePoint Online, OneDrive for Business, Office 365 Video,
Delve
Office 365 ProPlus client downloads
Skype for Business Online (formerly Lync Online)
Standard DNS and CDN lookups
Office Online
Office 365 (operated by 21 Vianet) service in China
Azure AD & Azure AD Sync
Power BI and Project Online
On-premises Identity Provider Sign-In
• WAN accelerators
• Some customer scenarios have seen improved performance
• Never a silver bullet and other measures should be investigated
• Required to be disabled for debugging or support
• Firewall IP address exceptions and URLs
• IP Addresses not as quickly updated
• Proxies
• PAC files, CONNECT, and are they helping or hurting
Stage 1 Performance troubleshooting engineer not required
Stage 2 Performance troubleshooting engineer is required
•
•
•
•
•
•
TCP Idle time settings
Proxy Authentication
DNS performance
SACK and TCP MSS
Lync tests to Server
SharePoint customization performance
Client
Proxy
Office 365 Datacentre
54.88ms
0.346ms
Internal RTT (ms)
External RTT (ms)
Total RTT to O365
54.88
346
400.88
Here we can see clearly, the poor RTT is outside the customer’s environment, on the ISP link to Office 365. If this
RTT is unexpected, the customer can engage their ISP to investigate.
TCP data packets
TCP ACK
TCP data packet
TCP ACK
TCP Window Scaling enabled?
Maximum TCP receive buffer (Bytes)
No
65535 (64k)
Yes
1073725440 (1gb)
Presuming a 1000 Mbps link here is the maximum throughput we can get
with TCP window scaling disabled and then with it enabled
Round Trip Time (ms)
Maximum Throughput
(Mbit/sec) without scaling
300
1.71
447.36
200
2.56
655.32
100
5.12
1310.64
50
10.24
2684.16
25
20.48
5368.32
10
51.20
13420.80
5
102.40
26841.60
1
512.00
134208.00
Maximum Throughput
(Mbit/sec) with scaling
Download a 14mb PDF from an EMEA tenant to Australia
600.0
500.0
507.0
Seconds
400.0
300.0
200.0
100.0
21.0
0.0
1
2
Time to transfer a 30Mb file
120
111
100
Time (Sec)
80
60
40
20
12
0
1
2
•
•
•
•
7692
12:28:03
14/03/2014
12:28:03.8450000
0.0000000
100.8450000
10.127.0.199
contoso47-48ipv4b.sharepointonline.com.akadns.net
TCP
TCP: [Bad CheckSum]Flags=......S., SrcPort=43511,
DstPort=HTTPS(443), PayloadLen=0, Seq=3807440828, Ack=0, Win=65535 ( Negotiating scale factor 0x0 ) = 65535
7740
12:28:04
14/03/2014
12:28:04.1440000
0.2990000
101.1440000
contoso4748ipv4b.sharepointonline.com.akadns.net
10.127.0.199
TCP
TCP:Flags=...A..S., SrcPort=HTTPS(443), DstPort=43511,
PayloadLen=0, Seq=3293427307, Ack=3807440829, Win=4380 ( Negotiated scale factor 0x2 ) = 17520
7692
12:28:03
14/03/2014
12:28:03.8450000
0.0000000
100.8450000
10.127.
0.199
contoso47-48ipv4b.sharepointonline.com.akadns.net
TCP
: [Bad
CheckSum]Flags=......S., SrcPort=43511, DstPort=HTTPS(443), PayloadLen=0, Seq=3807440828, Ack=0, Win=65535 (
Negotiating scale factor 0x0 ) = 65535 {TCP:818, IPv4:122}
7740
12:28:04
14/03/2014
12:28:04.1440000
0.2990000
101.1440000
contoso
47-48ipv4b.sharepointonline.com.akadns.net
10.127.0.199
TCP
TCP:Flags=...A..S.,
SrcPort=HTTPS(443), DstPort=43511, PayloadLen=0, Seq=3293427307, Ack=3807440829, Win=4380 ( Negotiated scale
factor 0x2 ) = 17520
{TCP:818, IPv4:122}
If Outlook client is in
the same region as the
Tenant, then we
connect direct to it
Microsoft DNS
3
Client’s DNS asks the
Microsoft DNS Server
Microsoft’s DNS servers
return the IP addresses of the
regional datacenter
North America Datacenters
2
Portal
EXO
MBX
EXO
Client’s DNS
The client asks the
local DNS Servers
CAS
5
Exchange Online accesses
the datacenter where the
tenant resides and proxies
the requests
1
4
The user accesses the
regional datacenter
DNS Call returns an IP
address of a Datacenter
local to the user’s
location
Outlook connects to that
and the data is
backhauled over the
Fibre network between
the tenant location and
the local Datacenter
Result is a much fast
connection for the client
and data stays in tenant
location.
Microsoft DNS
3
Client’s DNS asks the
Microsoft DNS Server
Microsoft’s DNS servers
return the IP addresses of the
regional datacenter
2
Client’s DNS
The client asks the
local DNS Servers
North America Datacenters
Exchange
Online accesses
the datacenter
where the
tenant resides
and proxies the
requests
EXO
MBX
5
1
EU Datacenters
Portal
4
The user accesses the
regional datacenter
EXO
CAS
Exchange Online uses GEO DNS
Internet
egress point
You get a different IP Address from
the DNS depending on where in the
world you request it
Impacts a multi-country corporate
network with multiple Internet
connection points
Commonly DNS is only requested at
one point and cached
Microsoft datacenter
DNS call
Customer network
Data transfer
You can get DNS from another part
of the globe to where you have
Internet connectivity
Tracing route to OUTLOOK-APACNORTH.OFFICE365.COM [132.245.65.146]
over a maximum of 30 hops:
1
1 ms
1 ms
1 ms SkyRouter.Home [192.168.0.1]
3
11 ms
11 ms
11 ms ip-89-200-132-100.ov.easynet.net [89.200.132.100]
4
10 ms
10 ms
10 ms igbtmdistc7503.msft.net [195.66.236.140]
5
84 ms
84 ms
84 ms xe-0-3-2-0.ash-96cbe-1a.ntwk.msn.net [207.46.45.227]
6
96 ms
95 ms
95 ms ae2-0.atb-96cbe-1a.ntwk.msn.net [207.46.33.228]
9 140 ms 142 ms 140 ms 191.234.83.150
10 142 ms 138 ms 139 ms ae11-0.lax-96cbe-1b.ntwk.msn.net [207.46.47.11]
11 256 ms 256 ms 256 ms ae2-0.tya-96cbe-1a.ntwk.msn.net [207.46.46.149]
12 265 ms 265 ms 265 ms ae0-0.tya-96cbe-1b.ntwk.msn.net [204.152.140.181]
13 288 ms 290 ms 292 ms xe-7-0-1-0.sin-96cbe-1a.ntwk.msn.net [207.46.38.252]
14 290 ms 288 ms 287 ms xe-5-3-1-0.sin-96cbe-1b.ntwk.msn.net [207.46.41.39]
15 279 ms 279 ms 279 ms ae1-0.sg2-96cbe-1a.ntwk.msn.net [191.234.80.90]
18 280 ms 280 ms 279 ms 132.245.65.146
3 min Idle TCP
session timeout
Property.TCPRetransmit == 1
User – JakeC
Domain – Contoso
Password Hash #
Proxy Auth
Required
Proxy
DC
DC
Initial connect:
14:12:24.6483418 19.0046514 0.0003578 iexplore.exe 10.200.30.40 btssig-msl.bcp-01.Contoso.sig HTTP:Request, CONNECT
Contosoemeamicrosoftonlinecom-3.sharepoint.emea.microsoftonline.com:443 , Using NTLM Authorization NTLM NEGOTIATE MESSAGE
Proxy Response:
14:12:24.6876389 19.0439485 0.0283000 iexplore.exe btssig-msl.bcp-01.Contoso.sig 10.200.30.40
HTTP:Response, HTTP/1.1, Status: Proxy authentication required, URL: Contosoemeamicrosoftonlinecom-3.sharepoint.emea.microsoftonline.com:443
NTLM CHALLENGE MESSAGE
We then send the request again, this time with NTLM authentication for the proxy: Contoso Office 365 Network Review
Second request with NTLM Auth:
14:12:24.6883198 19.0446294 0.0004838 iexplore.exe 10.200.30.40 btssig-msl.bcp-01.Contoso.sig HTTP HTTP:Request, CONNECT
Contosoemeamicrosoftonlinecom-3.sharepoint.emea.microsoftonline.com:443 , Using NTLM Authorization NTLM AUTHENTICATE MESSAGE
Version:NTLM v2, Domain: headoffdom, User: paul.collinge, Workstation: W7TEST20
200 OK response from proxy but this takes 3 seconds.
14:12:27.7859643 22.1422739 3.0878394 iexplore.exe btssig-msl.bcp-01.Contoso.sig 10.200.30.40 HTTP HTTP:Response, HTTP/1.1,
13:52:52 16/04/2013
31.2765664
0.0000000
10.200.30.40
10.214.2.129
DNS:QueryId = 0xE41, QUERY (Standard query), Query for Contosoemeamicrosoftonlinecom3.sharepoint.emea.microsoftonline.com of type A on class Internet
13:52:56 16/04/2013
35.0579179
3.7813515
10.214.2.129
10.200.30.40
DNS:QueryId = 0xE41, QUERY (Standard query), Response - Success, 157.55.232.50, 2.22.230.131 ...
http://technet.microsoft.com/en-us/library/office-365-system-requirements.aspx
http://aka.ms/tune
http://aka.ms/tunemva
http://blogs.technet.com/b/onthewire/