Don't throw error if only 1 PF mailbox in the environment

[dpaulson45]

Issue:
When there is only 1 Public Folder mailbox in the environment, we throw an error stating that this is bad. Which technically it is, but not an issue that needs to be addressed if the mailbox is small enough.

Reason:
Requested by a customer who has this setup.

Fix:
Run Get-Mailbox -PublicFolder again to see if there are multiple PF mailboxes. If there are, and the Root PF Mailbox is not excluded from serving the hierarchy, then show the error message.
Resolved #2478

Validation:
Pester tested

[Copilot]

Pull request overview

Adjusts HealthChecker’s “Root Public Folder Mailbox Serving Hierarchy” finding to avoid flagging an error when only a single Public Folder mailbox exists, reducing noise for small/valid single-PF-mailbox environments.

Changes:

• Collects a new boolean (MultiplePublicFolderMailboxes) during org data collection by quickly checking whether more than one PF mailbox exists.
• Updates the analyzer to only raise the “Root Public Folder Mailbox Serving Hierarchy” error when multiple PF mailboxes exist and the root PF mailbox is not excluded from serving hierarchy.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
Diagnostics/HealthChecker/DataCollection/OrganizationInformation/Invoke-JobOrganizationInformation.ps1	Adds a second PF mailbox query (ResultSize 2) and stores a MultiplePublicFolderMailboxes flag on the collected root PF mailbox object.
Diagnostics/HealthChecker/Analyzer/Invoke-AnalyzerFrequentConfigurationIssues.ps1	Gates the existing “Root Public Folder Mailbox Serving Hierarchy” error condition on MultiplePublicFolderMailboxes.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dpaulson45]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).