Live status of all services Advisory

Admins' mail-enabled security groups created through the admin center UI may be provisioned incorrectly

Exchange Online EX1558755

Admins' mail-enabled security groups created through the admin center UI may be provisioned incorrectly.

Status
Service degradation
Feature
Provisioning – Object synchronization failures
Region
Not specified (all regions)
Started
Oct 13, 2026, 11:34 CEST
Duration
37 days 12 h
Last update
Nov 19, 2026, 21:56 CET
Next update
Nov 20, 2026, 00:00 CET

Current status

We've verified that reversing the impacting change resolves the issue in our testing environment and we're proceeding with the reversal for all affected users.

More info

Specifically, when admins attempt to create mail-enabled security groups in the Exchange admin center (EAC) or Microsoft 365 admin center, the groups may be provisioned as regular distribution groups rather than mail-enabled security groups. As a workaround, admins can use PowerShell to create mail-enabled security groups.

Scope of impact

Some admins attempting to create mail-enabled security groups in the Exchange admin center or Microsoft 365 admin center may be affected. This section may be updated as our investigation continues.

Root cause

A recent service change designed to adjust the way our service handles requests to create security and distribution groups is missing a necessary configuration and is causing impact.

Timeline

Every update Microsoft posted for this issue, newest first.

  1. Nov 19, 2026, 21:44 CET

    We've verified that reversing the impacting change resolves the issue in our testing environment and we're proceeding with the reversal for all affected users.

  2. Nov 19, 2026, 19:47 CET

    We've updated the "Title", "User impact", "More info", and "Scope of impact" sections to more accurately convey our current understanding of the impact. We've identified a recent service change designed to adjust the way our service handles requests to create security and distribution groups that's missing a necessary configuration and is causing impact. We're testing the reversal of this change to ensure that it remediates the impact as expected.

  3. Nov 18, 2026, 09:17 CET

    We're continuing to review service logs and contextual details, including HTTP Archive (HAR) logs provided by a subset of affected users, to identify the root cause of the issue and determine an appropriate mitigation plan.

  4. Nov 18, 2026, 08:20 CET

    We're reviewing service logs and contextual details provided by a subset of affected users to gain insight into the underlying source of impact and determine our next steps.

  5. Nov 18, 2026, 07:53 CET

    We're investigating a potential issue with Exchange Online and checking for impact to your organization. We'll provide an update within 30 minutes.

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.