# M365 Tenant Suddenly Not Provisioning Mailboxes — retained record

> Retained reddit record from reddit:sysadmin.

Canonical: https://highsignal.app/data/records/5617d6c79f603577

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:sysadmin)  published 2026-11-19 13:28 ingested 2026-11-20 02:38

[original source ↗](https://www.reddit.com/r/sysadmin/comments/1y09cel/m365_tenant_suddenly_not_provisioning_mailboxes/)

## retained text



```
So, I've got a doozy of an issue I've never seen before. I've both got in a ticket with MS and reported the matter as a possible service issue. They were quick to eliminate it as a service issue but still haven't reached back out with my mystery "assigned agent."

Apparently, since Monday, users who are created in our M365 tenant, either directly in Entra or via AD connect sync to Entra, are not being provisioned mailboxes. Users in both creation flows have been assigned adequate licensing. Running Invoke-ProvisioningRecipientDiagnostic leveraging the Entra ObjectID (because they obviously can't be found leveraging UPN/email address) returns the user found perfectly in Entra but not in Exchange Online (which is no joke--they're stuck in "  
We are preparing a mailbox for the user." when you look at their mail in the Admin Center.) It's also not helpful output. Running Get-MgUserLicenseDetail on cloud-native users returns Exchange service plans as "PendingInput," but on-prem synced users show "Success." Neither get past the "preparing a mailbox" even after 24 hours has passed.

  
Now I've got 100+ users awaiting mailboxes that are not being provisioned. Has anyone encountered this before? Got any pointers for an admin who is in uncharted M365 territory? I've been doing this for 8 years come mid-December, and I've never seen this crap before.
```



document fetched 2026-11-20 00:38 · canonical https://reddit.com/r/sysadmin/comments/1y09cel/m365_tenant_suddenly_not_provisioning_mailboxes
