The_Exchange_Team : So what I take from that is this:
- If the cloud mailbox has the status of Shared mailbox and OnPrem Exchange still "thinks" it is a user mailbox, then via AADC, the cloud is able to convert it (back) to a user mailbox. If that functionality is in there, then why not provide the correct way for the intended changes?! (Probably kind of the same question as hatsikidee posted before).
- Those Shared mailboxes directly created via New-/Enable-RemoteMailbox -Shared should have the RemoteRecipientType "ProvisionMailbox" and hence don't have the problem from Ex2016 CU10 on, right?
- If the currently more or less Microsoft supported way to fix this problem is to directly fiddle with AD properties, wouldn't it be easier to change all the mailboxes with RemoteRecipientType "Migrated" to "ProvisionMailbox" and be done with the problem once and for all (at least for those customers that don't need to migrate OnPrem mailboxes any more)? Obviously this would need to be made possible in Exchange Online, which I suppose it is not right now.