O365 throttling

Hi all,

I will be migrating 100's of users over to Exchange Online over the next few months. The ones I've completed so far took a very very long time to migrate and I think it;s because of the throttling that MS apply to O365 tennants.

Via the Microsoft 365 admin center I have lifted the EWS throttling for 90 days but my question is, does NME use EWS? Will the change I made in the admin center make any difference or do I need to log a support ticket with MS to have another kind of throttling lifted?

Thanks

Parents
  • Thanks for the reply, I'm still a bit confused.

    I have under a 1000 users so it says "Microsoft will not provide increases to the default throttles, so service requests should not be submitted."

    In regards to the PowerShell max connections part - I have one machine only so does that mean that the powershell setting should be 9?

    I also dont get the Admin Pooling bit.

    I would appreciate any more help if possible.

    thanks

     

  • Ok Admin pooling. 

    One admin account migrating 10 mailboxes at the same time is NOT admin pooling. 

    10 Admin accounts migrating 10 mailboxes at the same time is Admin Pooling and also less likely to be throttled. 

    PowerShell connections

    MFNE using a single thread of the batch to process administrative tasks using powershell. So the default PS throttle settings will be more then enough. 

  • Thanks Jeff.

    So my understanding then is that there is nothing I can do?

    I have one MFNE server with one admin account and Quest is at the default configs.

    I am seeing huge latency when migrating a MB, eg, 5Gb took over 20 hours - starting at around 3.5 items per hour and quickly dropping back to under 1000 an hour. Is this me being throttled by MS?

    Thanks

  • So my understanding then is that there is nothing I can do?

    No, I am saying you can use an Admin pool. That works around throttling by using separate admin accounts for each mailbox in the collection. 
    If you had 12 mailbox in your collection, and 12 Admin accounts and you were using 12 threads, each mailbox would be migrating using their own admin account concurrently.

    The first part of the mailbox migration is slow as the calendar items are translated from Notes entries to Outlook entries. This is a one to many translations due to how notes can do things and how exchange does things. So this is really slow. Once that part of the migration is over, the throughput picks up. Running a pass for 1 mailbox is roughtly what you will see for 10-12 mailboxes. If you have 500MB has hour at the end of the process, you will see 10-12 times that at the end of the process. 

    There are known error messages for MAPI throttling. Based on what you just disclosed, you are not hitting throttling limits, you are just seeing the exppected performance of calendar translations. 

Reply
  • So my understanding then is that there is nothing I can do?

    No, I am saying you can use an Admin pool. That works around throttling by using separate admin accounts for each mailbox in the collection. 
    If you had 12 mailbox in your collection, and 12 Admin accounts and you were using 12 threads, each mailbox would be migrating using their own admin account concurrently.

    The first part of the mailbox migration is slow as the calendar items are translated from Notes entries to Outlook entries. This is a one to many translations due to how notes can do things and how exchange does things. So this is really slow. Once that part of the migration is over, the throughput picks up. Running a pass for 1 mailbox is roughtly what you will see for 10-12 mailboxes. If you have 500MB has hour at the end of the process, you will see 10-12 times that at the end of the process. 

    There are known error messages for MAPI throttling. Based on what you just disclosed, you are not hitting throttling limits, you are just seeing the exppected performance of calendar translations. 

Children
No Data