First, if you hit errors with cmdlets, please make sure that you file a formal support incident with Microsoft. It’s the only way that Microsoft will pay any real attention (i.e., assign an engineer to find out why the problem happened).

Second, with respect to this problem, I think I would try and use the strengths of the REST cmdlet in terms of fetching large numbers of objects fast and reliably while avoiding any lurking rocks which you might have discovered. In this instance, it could be that the pipeline is not being read correctly. So I would do:

[array]$Mbx = Get-ExoMailbox -ResultSize unlimited
ForEach ($M in $Mbx) {
$Perms = Get-ExoMailboxPermission…
If $Perms add to set of rights…
}

Thanks for the post. I would really like to move away from the old cmdlets to the new, but the problem I seem to have with the REST based cmdlets is when using pipelines. They just straight up fail without giving me a meaningful error. Here’s an example that I regularly need to run… Find all the users in the tenant who have full access permissions to a mailbox. With the old cmdlet, this is easy…

Get-Mailbox -ResultSize Unlimited | Get-MailboxPermission -User “John.Doe@acmecorp.com” | Select Identity,User,AccessRights

With the EXO cmdlets this gives a generic error

Get-EXOMailbox -ResultSize unlimited | Get-EXOMailboxpermission -User “John.Doe@acmecorp.com” | Select Identity,User,AccessRights

Get-EXOMailboxpermission : An error occurred while processing this request..

Many of us simply don’t have or are not given the time to trawl around google posts figuring out how to make the REST cmdlets work when the PS ones already work fine.

Any suggestions or any good resources that you know of that might reduce the pain?

Thanks

After 14 years of Get-Mailbox, isn’t it time to move on? (rhetorical)

Great info as always!

Thank you.