Our service is designed to protect the resources and ensure that certain users will not overwhelm it and cause latency for others. This limit is in place to protect against spike sending that we wish to discourage. As such, we have no plans to change the limit for regular mailboxes.
Where possible, we encourage customers who have these requirements to seek solutions that do not send emails all at once, can make use of DLs, or use services like Dynamics or third-party services to send large volumes of emails to customers or student and parents.
However, we are thinking about alternatives we can provide to solve this issue of higher sending for automated email scenarios to address this customer need.
An error occurred while saving the commentDoc Pratt commented
We just migrated a client from in-house Exchange to O365 Bus Prem., 95 licenses. Their application SW batches and sends 100 +/- invoices daily. They can group invoices and send multiples to each customer but some of their larger customers require individual invoices. There has been suggestions of going back to the exchange server but we may need to use a 3rd party SMTP server. Since the Try This Instead suggestion is over 3 years old, is there an updated suggestion?Doc Pratt supported this idea ·