Have you recently tried running this PowerShell Command:
Get-MailboxStatistics and been hit with this unexpected error:
Get-MailboxStatistics: ||Failed to commit the change on object "EURPR02DG595-db531" because access is denied.
This issue is currently affecting multiple Microsoft 365 tenants and is yet another symptom of instability and flawed change management in the Exchange Online (EXO) REST API.
When Does This Happen?
This error typically occurs when you’re attempting to retrieve mailbox folder statistics using the Get-MailboxStatistics PowerShell cmdlet on an Exchange Online mailbox. While Get-MailboxStatistics is a read-only command, the EXO REST API occasionally returns this misleading error message, indicating a write operation issue that shouldn’t exist in this context.
Affected users report that the error often surfaces randomly and inconsistently across different tenants.
This issue is problematic for all scripted solutions that rely on the Get-MailboxStatistics cmdlet, and underlying EXO REST API.
This is not the first time we are seeing strange behaviors from the EXO REST API.
Other issues we’ve learned from our large client base are listed here:
The impact of this EXO REST API isn’t limited to PowerShell users – it also affects third-party tools that rely on these APIs, including Easy365Manager and EasyEntra.
Easy365Manager
When attempting to retrieve mailbox statistics through Easy365Manager, users may encounter the following error:
Error occurred while processing EXO REST result: Cannot perform runtime binding on a null reference
This generic application error message is caused by the failure of the EXO REST API to return a valid result. Easy365Manager is expecting data that isn’t being delivered due to the access denied error at the API level.
Update 2025-05-18: We have created an update for this issue, which is now publicly available.
In EasyEntra, the issue manifests with this error message:
Error occurred in EXO REST query 'GetMailboxStatistics': Failed to commit the change on object "EURPR02DG449-db129" because access is denied.
This makes it clear that the underlying REST call has failed, despite the command being read-only. The database ID (EURPR02DG449-db129) may vary between tenants but confirms the nature of the issue.
Both tools depend on the EXO REST API for mailbox diagnostics. Until Microsoft resolves this at the backend, you should report the issue as detailed below.
Update 2025-05-18: We have created an update for this issue, which affected customers can request from support@easyentra.com.
Update 2025-05-31: We have released a public update that makes EasyEntra silently drop this issue.
You should report this error to Microsoft immediately.
We highly recommend providing the below information when submitting your ticket to ensure quick escalation to senior tech and to avoid a lot of back-and-forth with Microsoft first-line support:
1. Upgrade EXO PowerShell to the latest version:
Install-Module ExchangeOnlineManagement -Force 2. Perform a verbose authentication with EXO using a specific UPN:
Connect-ExchangeOnline -UserPrincipalName adm-user@example.com -Verbose This will return detailed output confirming module version, authentication steps, and connection setup.
3. Show the connection output:
Get-ConnectionInformation 4. Verify your management roles:
Get-ManagementRoleAssignment -RoleAssignee
adm-user@example.com | ft Name,Role,RoleAssigneeName -AutoSize 5. Run the failing command with verbose output to capture the error context:
Get-MailboxStatistics user -Verbose Or with the newer EXO REST cmdlet:
Get-EXOMailboxStatistics user -Verbose In the failing case, you will receive the access denied error:
Get-MailboxStatistics: ||Failed to commit the changeon object "EURPR02DG595-db531" because access is denied.
Include the full output from the above commands in your support ticket to ensure efficient escalation to senior support team members.
Summary
Microsoft has not yet officially acknowledged the issue, and no public advisory has been released. Based on past experience, it’s possible that Microsoft will apply a silent backend fix without prior notice.
We will update this article as more information becomes available.
As a response to how this issue affects EasyEntra and Easy365Manager, we have created a pre-release of EasyEntra, available upon request, and a new public release of Easy365Manager available here.
Update 2025-05-19:
The issue is still being reported by various tenants.
We have published a new release of Easy365Manager that silently drops errors related to this issue.
Update 2025-05-20:
One of our clients got feedback from Microsoft: “This issue is related to instability in the Exchange Online (EXO) REST API, therefore we are initiating few backend diagnostics”.
There is still no official information on the issue.
Update 2025-05-21
We’re still getting multiple reports from clients affected by this issue. Additionally, if the traffic on this page reflects the impact of this issue, it’s growing fast.
Update 2025-05-30:
Microsoft has now released official information regarding this issue and set the status to solved:
