Unexpected results using Get-Mailbox cmdlet in parallel

Question

I got unexpected results using the Get-Mailbox cmdlet.

My code is making 17 calls in parallel of the same command with a different filter parameter, each call should return the correct result for the specific filter:
Get-Mailbox -ResultSize Unlimited -RecipientTypeDetails UserMailbox -Filter "ExternalDirectoryObjectId -like '<hex>*'".

We sum all the calls results and expect to get the total count of the mailboxes with RecipientTypeDetails UserMailbox.

The problem is that some calls return 0 results instead of returning the correct one (although there are actual results that should be returned - running the same cmdlet on PS returns a result), therefore the sum of all the calls isn’t accurate to the sum we expect to.

The issue is not on a specific filter, it’s random (therefore the total results are not always the same).

What could be the reason for those results?

Answer 1

Hi there,

It’s a good idea to replace older calls to the Get-Mailbox cmdlet with Get-ExoMailbox. However, it’s not just a matter of cut and paste updates. In some cases, the nature of the new REST-based cmdlets mean that some additional care is necessary to ensure that the updated code works as expected.

You can get more info from here https://techcommunity.microsoft.com/t5/exchange/using-filters-with-the-get-exomailbox-cmdlet/m-p/2466152

Hope this resolves your Query!!

---

--If the reply is helpful, please Upvote and Accept it as an answer--