Exchange Online Throttling and Limits FAQ

re: Exchange Online Throttling and Limits FAQ

Michael Mainer — Tue, 30 Apr 2013 21:09:46 GMT

@Jay Foster

Creating an appointment would not come close to reaching a throttling limit. I'd have to know what their cloud service does before I could comment on it.

With regards,

Michael Mainer

re: Exchange Online Throttling and Limits FAQ

Jay Foster — Tue, 30 Apr 2013 20:48:30 GMT

Michael,

I want to move my office to cloud-based Amicus Cloud which works great with Outlook 2010. I currently have Microsoft 365 which I would also keep. However, I've gotten feedback from several law firms that say it literally takes "minutes" for an appointment to post sometimes using Amicus with Office 365 due to this throttling issue. Any updates on this?

re: Exchange Online Throttling and Limits FAQ

Ivan Serebrov (Dell Software Group) — Mon, 25 Mar 2013 05:54:26 GMT

Michael, I heard Office 365 Wave 15 throttling has gotten more severe. For example, powershell sessions limit on per tenant basis was introduced. When could we expect an update to this article to reflect Wave 15 changes? Thanks!

re: Exchange Online Throttling and Limits FAQ

Kris Taracad @4Finance — Wed, 23 Jan 2013 19:23:49 GMT

This was a very informative post with exactly the answer I was looking for. Unforunately we are using Exchange Online which limits what I can do but information is power. Thank you very much for this.

Kris

re: Exchange Online Throttling and Limits FAQ

Michael Mainer — Thu, 29 Nov 2012 17:39:47 GMT

@Regarding throttling policy cmdlets and Exchange Online.

Yes, it is true that the throttling policy cmdlets were removed from Exchange Online. I've raised this as a concern with the product team.

With regards,

Michael Mainer

Microsoft Corporation

re: Exchange Online Throttling and Limits FAQ

Michael Mainer — Thu, 29 Nov 2012 17:37:44 GMT

@Shafdat_ali,

I suggest you post your question with additional information to the Exchange development forum. I'd expect you will get answer sooner that way.

social.technet.microsoft.com/.../threads

With regards,

Michael Mainer

Microsoft Corporation

re: Exchange Online Throttling and Limits FAQ

Shafqat_ali — Thu, 29 Nov 2012 05:00:04 GMT

i am sending the message with attachments of greater then 10 MB using MAPI 2.0 throws exception:

Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

at System.Net.Sockets.Socket.MultipleSend(BufferOffsetSize[] buffers, SocketFlags socketFlags)

at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)

--- End of inner exception stack trace ---

at System.Net.Sockets.NetworkStream.MultipleWrite(BufferOffsetSize[] buffers)

at System.Net.Security._SslStream.StartWriting(SplitWritesState splitWrite, SplitWriteAsyncProtocolRequest asyncRequest)

at System.Net.Security._SslStream.ProcessWrite(BufferOffsetSize[] buffers, SplitWriteAsyncProtocolRequest asyncRequest)

at System.Net.TlsStream.MultipleWrite(BufferOffsetSize[] buffers)

at System.Net.Connection.Write(ScatterGatherBuffers writeBuffer)

at System.Net.ConnectStream.ResubmitWrite(ConnectStream oldStream, Boolean suppressWrite)

--- End of inner exception stack trace ---

at System.Net.HttpWebRequest.GetResponse()

at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()

at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)

--- End of inner exception stack trace ---

at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)

at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)

at Microsoft.Exchange.WebServices.Data.SimpleServiceRequestBase.InternalExecute()

at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute()

at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalCreateItems(IEnumerable`1 items, FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode, ServiceErrorHandling errorHandling)

at Microsoft.Exchange.WebServices.Data.ExchangeService.CreateItem(Item item, FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode)

at Microsoft.Exchange.WebServices.Data.Item.InternalCreate(FolderId parentFolderId, Nullable`1 messageDisposition, Nullable`1 sendInvitationsMode)

at Microsoft.Exchange.WebServices.Data.Item.Save(WellKnownFolderName parentFolderName)

re: Exchange Online Throttling and Limits FAQ

SBasheer — Thu, 20 Sep 2012 06:54:24 GMT

The Get-ThrottlingPolicy commandlet is not available on office 365 online. So the statement "Use the Get-ThrottlingPolicy cmdlet (without arguments) to get all the throttling policy settings" will not work for Office 365 domains. It is a pity that MS has not specified this anywhere and people spent hours setting up the environments just to figure out this doesn't work.

I lost the time, don't want any one else to lose it again.

re: Exchange Online Throttling and Limits FAQ

SBasheer — Thu, 20 Sep 2012 06:46:33 GMT

The Get-ThrottlingPolicy commandlet is not available on office 365 online

re: Exchange Online Throttling and Limits FAQ

Ivan Serebrov (Quest Software) — Thu, 20 Oct 2011 09:52:58 GMT

Administrators cannot configure throttling policies for Exchange Online.

On one hand this makes total sense to not allow customers change the throttling settings in Exchange Online so that MS could have predictable load levels.

On the other hand higher bandwidth may be required for migration purposes, which is a one-time project. I expect corresponding settngs may be changed by MS for a customer upon request, but this would require contacting support.

I have an enhancement proposal: allow customer to change specific throttling settings for just one specific account. Use case: I want to run a migration and use third-party (not native migration-batch) tools for that. Those tools use an ms online administrator account to connect to Exchange Online. If there was a powershell cmdlet allowing to set higher throttling settings for this specific account, that would be great. Of course, throttling setting limits need to be defined for this account as well, but they can be considerably higher than the ones for generic users just using services.

This would allow to:

1. Still have predictable load levels.

2. Eliminate the need for contacting support to do migration.