Forum Discussion

Motly-2000's avatar
Motly-2000
Copper Contributor
May 16, 2022

Get-EXOMailboxFolderStatistics result limit 1000 items

EHLO community,   I have a PowerShell scripted process to extract mailbox statistics for a group of large mailbox users 80-90GB. Many of these users demand to keep their primary mailbox full of all...
exchange online
hybrid
office 365
VasilMichev's avatar
VasilMichev
MVP
May 16, 2022
I'm not entirely sure what you mean here. Get-EXOMailboxStatistics is a "single object" cmdlet, it has never supported -ResultSize, neither has Get-MailboxStatistics. And since you usually run it in tandem with Get-Mailbox/Get-ExOMailbox, this is easy to get around.
But it looks to me you might probably mean Get-MailboxFolderStatistics/Get-ExOMailboxFolderStatistics instead? Same here though, no -ResultSize parameter. In any case, if the built-in cmdlets are not returning the full set of folders, you'd probably need some EWS or Graph API based solution.
  • Motly-2000's avatar
    Motly-2000
    Copper Contributor
    May 18, 2022
    Thank you for the reply, yes I'm an idiot, yes the folder stats is what I meant, big difference.
    Updated the post.
    Difficult scenario to test without a mailbox with over 1000 top level or nested folders.

    I'm hoping I missed something obvious but all tests of both Get-MailboxFolderStatistics/Get-ExOMailboxFolderStatistics, now limit at 1000.

    Thanks again.
    • Network23's avatar
      Network23
      Copper Contributor
      Jun 07, 2022

      Motly-2000 VasilMichev TonyRedmond 

      Hi,
      Good news, I opened a case last week from O365 support, and it seems they just added the resultsize parameter to the Get-MailboxFolderStatistics. The following command :

      (Get-MailboxFolderStatistics -Identity $TargetMailbox -resultsize unlimited).Count

      on our big big mailbox is now returning more than 1000 results.

      Thanks for your assistance.

      • Satnaz's avatar
        Satnaz
        Copper Contributor
        Oct 11, 2024
        This worked, Thank you.

        I used the below script to count sub folders on my biiiig mailbox.

        $Mailbox = Get-Mailbox -Identity "email address removed for privacy reasons"

        $Folders = $Mailbox |
        Get-MailboxFolderStatistics -ResultSize Unlimited | # Ensure all folders are retrieved
        Where-Object { $_.FolderPath -notmatch '^\$' } | # Exclude the root folder
        Measure-Object |
        Select-Object -ExpandProperty Count

        $Result = New-Object -TypeName PSCustomObject -Property @{
        Username = $Mailbox.Alias
        FolderCount = $Folders
        }

        $Result |
        Select-Object -Property Username, FolderCount
    • Network23's avatar
      Network23
      Copper Contributor
      May 30, 2022

      Motly-2000 I was able to reproduce the issue, since I do have a mailbox with approx 2000 folders. The command

       

      Get-MailboxFolderStatistics -Identity $TargetMailbox

       

      Is now returning only the 1000 first items, it is a big issue for our systems since a script to export and archive mails in subfolders of that email relies on this command, since the capped result change without any warning, we do not have time planned to implement a whole Graph API based solution right now, and we are currently stuck on archive request on a nearly full mailbox ...

      • TonyRedmond's avatar
        TonyRedmond
        MVP
        May 31, 2022
        I agree with Vasil that you should open a support case. It might be that the developers haven't run the cmdlet against a mailbox with so many folders. In the meantime, you might find that developing a Graph-based answer isn't as complex as you think. See https://office365itpros.com/2022/05/19/mailbox-folder-statistics/ for an example.

Resources