This next tip comes from Marius “Why are you still on-premises” Agur Lind. Got a tip of your own? Send it to firstname.lastname@example.org (and don’t forget to include either your Twitter handle or LinkedIn profile link for the eternal link appreciation).
Have you ever used an on-premise deployment and found that some testing and enabling mailboxes fail at weird intervals? Have you double, triple, and quadruple-checked the password and it’s still failing? Tried to see if dirsync is failing and updated the user password?
Well here’s what be ailing you:
Go check out the details of the warning message under alerts, and you might just find the following:
System.Web.Services.Protocols.SoapException: The server cannot service this request right now. Try again later.
The reason why you’re getting this error is most probably because you’ve hit the outgoing email threshold of your Exchange Online. Wanna know how to fix it? Add more licenses.
Yes, I’m not kidding, the Exchange Online threshold policy is based on the number of user licenses, so if you’re hitting this limit you just have to try again later. There is no queue system, you just have to handle it yourself.
Could be worse, but there you have it.