Today, Monday 11th of September, 2023, a new error came up in Exchange Online:
It seems the error only occurs in a minimal number of tenants.
We had two clients reporting this issue during the day, and we also noticed that people started posting this issue on the Internet during the day.
Clients reporting this error message from Easy365Manager also see it when running a regular Get-Mailbox command with the EXO PowerShell module:
Write-ErrorMessage : this method should only be called from updatesessiontoreadlimitedpropertiesusingfullobject At C:\Users\ms-adm\AppData\Local\Temp\tmpEXO_er3cdapt.do2\tmpEXO_er3cdapt.do2.psm1:1188 char:13 + Write-ErrorMessage $ErrorObject + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-Mailbox], Exception + FullyQualifiedErrorId: [Server=AM0PR01MB5491,RequestId=abfe3984-1643-4394-9ab2-34bcFe3498e3, TimeStamp=Mon, 11 Sep 2023 16:30:58 GMT],Write-ErrorMessage This method should only be called from UpdateSessionToReadLimitedPropertiesUsingFullObject API using Management cmdlet
So, it seems to be a general issue with the Exchange Online backend infrastructure, and we encourage everybody seeing this issue to raise a ticket with Microsoft.
Unfortunately, Microsoft has not posted any information about this error, so admins have to cross their fingers that their tenant won’t get hit or that Microsoft will eventually address this issue.
It’s a very unfortunate trend to see errors in Exchange Online be given the silent treatment by Microsoft. This has a very cooling effect on customer confidence.
Update I, 2023-09-12
It seems Microsoft have now identified and announced this issue in some tenants:
Also, according to feedback from one client, the problem is now solved in their tenant.