The limit you are talking about protects against large volume senders overwhelming the shared resources of our service and ensures emails are not all sent out at once for automated systems. Can you please tell us more about the problems this causes to the software that queueing and retries are not able to handle?Tom S commented
Microsoft is not applying the limit properly, or it's description of the limit is wrong. A 30 message per minute limit should apply the "554 5.2.0" exception to the MESSAGE, not some of the recipients for that message. Our problem is that If we send a message to several recipients and hit the limit, it may fail one or two of them but send to the rest. If I re-submit the email, it'll cause duplicates for some of the recipients (bad). If I delete the recipients that already received the message, then the other recipients will not see those on their copy of the email (also bad).