Troubleshooting
Maximum PowerShell sessions against Microsoft Exchange
If you receive an error message with the following syntax:
then this means that you have reached the maximum allowed concurrent PowerShell sessions against Exchange Online.
To resolve the issue, you must close a few other PowerShell sessions. The Omada Identity Exchange Hybrid Connectivity automatically removes its PowerShell session after each connection to Exchange Online.
If the error continues to occur you can open a case with the Exchange Online Team with the title Increase Throttle Policy and ask for more concurrent sessions, the default setting is PowerShellMaxConcurrency = 3.
Microsoft Exchange doesn't support reported mailbox type
If you receive an error message with the following syntax:
Cannot convert value System.Collections.ArrayList to type "Microsoft.Exchange.Data.Directory.Recipient.RecipientTypeDetails[]". Error: "Cannot convert value "SchedulingMailbox" to type "Microsoft.Exchange.Data.Directory.Recipient.RecipientTypeDetails". Error: "Unable to match the identifier name SchedulingMailbox to a valid enumerator name.
then this means that Microsoft Exchange doesn't support SchedulingMailbox (or any other mailbox type that is mentioned in the log).
To resolve the issue, remove mailbox type mentioned in the log from Mailbox subtype in all queries.