Office 365 Performance Management

Meet Paul Andrew | @pndrw• Office 365 Technical Product Manager

– Office 365 datacenter, networking, identity management– Passion for informing and inspiring IT Professionals

to create simpler solutions to complex problems

Meet Joshua Maher | @joshmaher• Senior Content Developer, Office 365

– Focus on improving the deployment experience forOffice 365

M3: Planning for Office 365 Internet capacity – Exchange Online

Agenda

• Steady-state network capacity• Migration network capacity• Workstation configurations• NAT support• Network performance factors• Office 365 throttling• Devices and multi-site configurations

Steady-state network capacitySteady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Steady-state network capacity

• Figuring for post migration everyday network requirements

• Determine your download, upload, and latency between your on-premises environment and the nearest Microsoft cloud services data center

• Use the calculator– http://

gallery.technet.microsoft.com/Exchange-Client-Network-8af1bf00

EXCHANGE ONLINE CALCULATOR

demo

Migration network capacitySteady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Migration network capacity

• Migration Velocity Testing– Understand your network and application usage

o Microsoft Network Monitoro Microsoft Remote Connectivity Analyzero Microsoft Online Services Diagnostics and Logging (MOSDAL) Support Toolkit

• Strategies to Improve Migration Velocity– To improve migration velocity as well as reduce your organization’s bandwidth

constraints, you should consider the following:o Reduce mailbox sizeso Use the mailbox move capabilities with an Exchange hybrid deploymento Schedule mailbox moves to occur during periods of low Internet traffic and low on-

premises Exchange use

Migration network capacityMigration Method

Office 365 user throttling

Office 365 migration-

service throttling

Office 365 resource

health-based throttling

Observed average throughput per hour and per client (if applicable)

IMAP Migration No Yes Yes 10-15 GB (100 concurrency)

Cutover Migration

No Yes Yes 10-15 GB (100 concurrency)

Staged Migration

No Yes Yes 10-15 GB (100 concurrency)

Hybrid Migration

No Yes Yes 10-15 GB per on-premises Exchange 2013 or 2010 CAS (MRS Proxy) with 20 concurrent moves

Third party MAPI Migration

Yes No Yes 4-12 GB (20 concurrency)

Third party EWS Migration

No Yes Yes 5-10 GB (20 concurrency)

Client Uploading (From Outlook PST)

Yes No Yes 0.5 GB

Workstation configurationsSteady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Workstation configurations

• Each PC needs to connect to the Internet, download, and install any necessary service packs or updates

• Deploy updates via a package deployment tool such as Microsoft System Center Configuration Manager

• Alternatively consider Active Directory group policy or throttling your deployment of the Office 365 desktop setup

NAT supportSteady-state network capacityMigration network capacityWorkstation configurationsNAT SupportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Network Address Translation support

• What is NAT? – Private (RFC1918) IP address space– Firewalls and proxy make traffic appear to be coming from one

or more publicly routable IP addresses– Thousands of people on a corporate network can “share” a few

publicly routable IP addresses

• NAT limitations with Office 365 – Outlook opens eight connections– There are a maximum of 60,000 ports available on a Windows-

based NAT device

Network Address Translation support

• Calculating maximum supported devices behind a single public IPaddress with Office 365 – Monitor network traffic to determine peak port consumption per client

o Maximum supported devices behind a single public IP address = (64,000 – restricted ports)/(Peak port consumption + peak factor)

o If 4,000 ports were restricted for use by Windows and 6 ports were needed per device with a peak factor of 4:

o Maximum supported devices behind a single public IP address = (64,000 – 4,000)/(6 + 4)= 6,000

• To support more than 2,000 devices behind a single public IP address– Simplest solution is to segment your user address space and statically “assign”

a number of IP addresses to each gateway

Network performance factorsSteady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Network performance factors• Network capacity - Time it takes to migrate mailboxes to

Exchange Online is determined by the available and maximum capacity of your network

• Network stability - If the network isn’t stable, data transfer takes longer because of error correction. Depending on the migration type, error correction can significantly affect migration performance

• Network delays - Intrusion detection functionality configured on a network firewall often causes significant network delays and affects migration performance

Office 365 throttlingSteady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Office 365 throttling

• Office 365 user throttling– User throttling affects most third-party migration tools and client-uploading

migration method– User throttling is the most restrictive throttling method in Office 365

• Office 365 migration-service throttling– Migration-service throttling affects all Office 365 migration tools– An example of migration-service throttling is controlling the number of

mailboxes that are migrated simultaneously, default value is 3

• Office 365 resource health-based throttling– All migration methods are subject to the governance of availability throttling,

but Office 365 service throttling doesn’t affect Office 365 migrations as much– Resource health-based throttling is the least aggressive throttling method

Devices and multi-site configurations

Steady-state network capacityMigration network capacityWorkstation configurationsNAT supportNetwork performance factorsOffice 365 throttlingDevices and multi-site configurations

Devices

• WAN Accelerators– WAN accelerators are great when you control both ends of the traffic.– When you aren’t planning half the traffic WAN accelerators are hard to deal with.

o For example, Office 365 services encrypt some Office 365 content and the TCP header. Your device may not be able to handle this kind of traffic.

• Hardware and Software Load-balancing Devices– You may want to use a load balancer if you have AD FS or any SSO solution– We provide a software-based NLB solution built into Windows Server. Office 365

supports this solution to achieve load balancing.

Multi-site configurations

• Client computers may connect to different Office 365 datacenters– Computer location, VPN, DNS, Office 365 service, and so

on.– Customers have some control– Different connections will have different performance

attributes

M4 Summary: Planning for Office 365 Internetcapacity – Exchange Online

• Steady-state network capacity• Migration network capacity• Workstation configurations• NAT support• Network performance factors• Office 365 throttling• Devices and multi-site configurations• Plan for Internet bandwidth usage for Office 365

– http://technet.microsoft.com/en-us/library/hh852542.aspx

©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.