Exchange online client connectivity across regions

#Exchange online client connectivity across regions update#

Load balancing If some servers are experiencing higher loads, mailboxes may need to be load-balanced across different servers.

Fail over If hardware or connectivity failures arise in a site, Exchange 2010 in Office 365 automatically switches (or fails over) to a different mailbox database to ensure continuous access to your mailboxes.The switch from one active copy of a mailbox to another one stored on a different mailbox server may happen for the following different reasons: When a user connects to their mailbox, they take actions on the active copy, and changes are then propagated to its passive copies. At any given time, one copy of a particular mailbox is considered active and the remaining ones are deemed passive. This redundancy ensures that if one copy of the mailbox fails for some reason (for example due to a hardware failure on a particular server), we can access the same mailbox elsewhere. In Office 365, we store multiple copies of user mailboxes, geographically distributed across different sites and datacenters. Through the protocol version negotiation, the device and the server agree to behave in a particular manner in accordance with the version selected. Editor)Д«efore any device accesses an Exchange mailbox, it negotiates with the Exchange server to determine the highest protocol version that they both support, and then uses this protocol version to communicate. (The Exchange ActiveSync article maintained by the Exchange community on Wikipedia has more details. Each successive version of the protocol offers new capabilities. Most mobile devices that connect to Exchange do so using the Exchange ActiveSync protocol. This article explains how mobile devices connect to Exchange Online (Office 365) service and how the connectivity may be impacted if the device does not support certain Exchange ActiveSync (EAS) protocol requirements. In the meantime, we continue to work with device manufacturers to help them resolve their Exchange ActiveSync protocol implementation issues. Look for the announcement on the blog when the fix is fully deployed with instructions for reconfiguring affected devices. We estimate that the fix will be fully deployed worldwide by April 30th, 2012.

#Exchange online client connectivity across regions update#

Update : In order to mitigate issues with some mobile device implementations of redirection, Microsoft is currently deploying an interim solution that should eliminate the need for manual server reconfiguration of the affected devices when your Office 365 server location changes. We continue to work with device manufacturers to help them resolve their Exchange ActiveSync protocol implementation issues. Update: : Microsoft has completed deployment of the interim solution that should eliminate the need for manual server reconfiguration of the affected devices when your Office 365 server location changes.