A new issue has surfaced in Exchange Online which causes the following two CmdLets to fail:
Get-MailboxFolderStaticticsGet-MailboxRegionalConfigurationRunning these CmdLets often hangs for a long period of time (a minute or more) and results in the following error message:
Write-ErrorMessage : ||Error on proxy command 'Get-MailboxFolderStatistics -Identity:'l.hau'
-skipCount:'0' -resultSize:'1000'' to server AM0PR09MB3971.eurprd09.prod.outlook.com:
Server version 15.20.8632.0000, Proxy method PSWS: InternalServerError:
Element 'Objs' with namespace name 'http://schemas.microsoft.com/powershell/2004/04' was not
found. Line 1, position 2. : {
"code": "InternalServerError",
"message": "Element 'Objs' with namespace name
'http://schemas.microsoft.com/powershell/2004/04' was not found. Line 1, position 2.",
"innererror": {
"message": "Element 'Objs' with namespace name
'http://schemas.microsoft.com/powershell/2004/04' was not found. Line 1, position 2.",
"type": "System.Xml.XmlException",
"stacktrace": ""
},
"adminapi.warnings@odata.type": "#Collection(String)",
"@adminapi.warnings": []
} [Server=AM7PR09MB3877,RequestId=c0b1ecb7-9b7e-5da3-0a66-1863fbac8577,
TimeStamp=4/14/2025 10:54:44 AM] .
At C:\Users\adm.msk\AppData\Local\Temp\tmpEXO_trozoxbs.xa1\tmpEXO_trozoxbs.xa1.psm1:1189
char:13
+ Write-ErrorMessage $ErrorObject
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-MailboxFolderStatistics], CmdletProxyException
+ FullyQualifiedErrorId : [Server=AM7PR09MB3877,RequestId=c0b1ecb7-9b7e-5da3-0a66-
1863fbac8577,TimeStamp=Mon, 14 Apr 2025 10:54:44 GMT],Write-ErrorMessage This error appears to stem from a malformed or unexpected XML response from the backend, possibly related to changes in how the Exchange Online REST API (EXO V3 module) handles responses.
As a result, third-party tools and scripts that rely on these CmdLets via the EXO REST API proxy may also be affected.
Microsoft has not yet officially acknowledged the issue, but we suspect more information will surface soon—or that a silent backend fix may be rolled out, as is often the case with Exchange Online service updates.
In the meantime, admins depending on this cmdlet should report this issue to Microsoft, monitor the situation, and consider holding off on critical processes that rely on it.
We’ll update this post as new information becomes available.
Update 2025-04-15 00:30 CEST:
There is still no public information on this issue, and we’re no longer seeing the problem in our testing environment.
It’s evident that general issues occurred in Outlook and M365 earlier today, but hopefully this is fixed now:
