I wanted to provide an update on this whole thing:
The limit is a real thing (as you all have noticed) - and at this time, it is going to stay there. We realize that there are those that are impacted by this, but based on our telemetry, this is a very rare scenario.
Note that the errors and warnings being thrown if the mailbox is in the situation of having more than 200 email addresses is technically cosmetic, in other words - the mailbox still does function and log on/mail flow is not impacted by the new limit. Obviously,
being unable to edit the addresses is a thing, though. But mailbox function is not impacted immediately.
Both CMDlets and Exchange Admin Center will successfully update the number of email addresses providing the end result of the CMDlet execution is a situation where the mailbox has 200 or fewer email addresses on it. In other words - if you, for example,
had 220 addresses on an mailbox, and then removed 20 through EAC (multi-select) and then pressed Save, we expect the mailbox to be updated properly and validation errors to go away. Same goes for CMDlets; if a set of addresses is passed to be removed, CMDlet
execution should succeed.
So - it is possible to export current addresses, decide which ones should be removed, remove them from affected mailboxes and then graft them to let's say a shared mailbox (which does not require a license). Then set that shared mailbox to forward all incoming
email to your own user mailbox. It is just an idea, of course, but it would satisfy the requirement of having additional 200 email addresses for the user.
I am currently writing a KB article that goes into all this as well as mentions the errors / warnings that people will see. I will also have the documentation that says that the limit is "100" corrected. The
Exchange Online Limits article has the 200 limit documented, although I hate the wording of "Recipient proxy address limit" as I do not think it is meaningful to most humans. It should really say something like "Max. number of email addresses a recipient
can have" but still working on that.
One more thing - I think someone earlier in the thread mentioned that there was "no limit" before. This is not correct. The limit was always there, but it was very high; depending on # of characters in emails, it could have been close to 1000 email addresses
but could have been fewer. In other words - there was always a limit but very few ever ran into it.
Finally - let me just say that it pains me when we cause additional work to you, our customers. The limit we imposed has nothing to do with something any of you did, but it was the right call at this time for our service. Due to the nature of the problem,
there is a possibility that in some time we could remove this limit or make it higher, but that is something that we do not have any timeframe for at this time.
I will update this thread with the KB article once published. I expect a few days. Also - if any of you are going to Microsoft Ignite next week, look me up there and we can discuss!