Live status of all services Advisory

Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups

Exchange Online EX1477761

Admins experience intermittent failures adding, modifying or removing members from Exchange Online distribution groups.

Status
Service degradation
Feature
Tenant Administration (Provisioning, Remote PowerShell)
Region
Not specified (all regions)
Started
Jun 9, 2026, 23:43 CEST
Duration
129 days 5 h
Last update
Oct 15, 2026, 17:55 CEST
Next update
Oct 22, 2026, 19:30 CEST

Current status

We've initiated the deployment of our fix, which is ongoing and has saturated through over 50 percent of the affected environment. We're continuing to monitor its progress as it continues and anticipate it will complete, remediating impact for all users, by our next scheduled communication update.

More info

Admins may intermittently receive an error stating, "Failed to update Members - Response Content is Null" when managing distribution group membership in the Microsoft 365 Admin Portal or Exchange Admin Center.

As a workaround, admins can use Exchange Online PowerShell to add or remove members from affected distribution groups.

Impact is specific to admins utilizing on-premises Exchange who are attempting to add or remove members from Exchange Online distribution groups.

Scope of impact

This issue impacts some on-premises Exchange admins attempting to add or remove members from Exchange Online distribution groups. This section may be updated as the investigation progresses.

Root cause

A conflict between a configuration and a recent update is preventing admins from adding or removing users from distribution groups for on-premises configurations.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Oct 15, 2026, 17:55 CEST

    We've initiated the deployment of our fix, which is ongoing and has saturated through over 50 percent of the affected environment. We're continuing to monitor its progress as it continues and anticipate it will complete, remediating impact for all users, by our next scheduled communication update.

  2. Oct 8, 2026, 17:57 CEST

    We've completed the validations for our fix, which we're preparing to deploy to the affected environment. We still anticipate deployment will begin by Thursday, October 15, 2026.

  3. Oct 1, 2026, 17:57 CEST

    Our validations are taking longer than initially anticipated as we test the effectiveness of our code fix to ensure it fully remediates impact once deployed. We anticipate beginning deployment by Friday, October 15, 2026, and we aim to provide updates on our timeline to release as we complete our validation process.

  4. Sep 24, 2026, 18:06 CEST

    We're deploying a code fix to our internal test environment to validate its efficacy in remediating the impact. We anticipate our validations will be completed by our next scheduled communications update, at which time we'll aim to provide a timeline for the broad deployment.

  5. Sep 23, 2026, 19:55 CEST

    After reviewing reports of impact and provided diagnostic data, we've isolated that when admins are attempting to add or remove members from Exchange Online distribution groups, there's a conflict between a configuration and a recent update which is preventing admins from being able to add or remove users from distribution groups for on-premises configurations. We’re removing the problematic behavior from our code flow with a new code fix. We aim to provide a timeline for code fix deployment to be initiated by our next scheduled update.

  6. Sep 23, 2026, 18:54 CEST

    We've received reports from a subset of affected admins that the impact scenario documented in EX1466035 is still ongoing and additional analysis is required. We're reviewing the latest reports of impact to further our understanding and to determine our next troubleshooting steps.

When Microsoft 365 goes down

The live overview shows the current state of every Microsoft 365 service, refreshed every minute from Microsoft Graph.

To see whether your own tenant is affected, check Service health in the Microsoft 365 admin center. Only a backup outside Microsoft protects against data loss, and only a tested break-glass account against locked-out admins. We set up both in fixed-scope sprints.

Source: Microsoft Graph, Service Communications API. This is the view of a Swiss Microsoft 365 tenant: services not licensed there are missing, and individual issues may affect your tenant differently. Microsoft names the region only in the issue text. The Switzerland view shows issues for Switzerland, for Europe in general and those without a region, but not issues that only name other countries such as Germany or the UK. This page is not provided by Microsoft.