New Microsoft 365 users are licensed but their mailboxes aren't being created. What should I check?

November 19, 2026 5 answers
Asked by BreezyMilo

New users created directly in Entra ID and users synced from Active Directory are both stuck at “preparing a mailbox” for over 24 hours. They have licenses, but Exchange Online doesn't find the recipients.

Exchange service plans show PendingInput for cloud-native users and Success for synced users. Microsoft support has been contacted. What else should I check while waiting?

Answers

n.936!claspwren

Start with a few affected accounts and check the actual Exchange service plan, not just whether a license SKU is assigned. In the licensing details, make sure the Exchange plan is enabled and check the user's UsageLocation too.

Then compare how those users got their licenses. If some use group-based assignment, verify that the expected group membership and assignment are present. A plan showing Success doesn't necessarily mean the mailbox is ready, so compare it with the recipient status in Exchange Online.

BreezyMilo:

Some licenses come through dynamic groups, but not all of them. I'll compare those with directly assigned licenses and check the Exchange plan on both.

Reply to this answer
MoxieT

Check serviceProvisioningErrors through Microsoft Graph for a couple of stuck users. Request that property explicitly with Get-MgUser and inspect the returned errors. A conflict such as a duplicate proxy address may show up there and give you something more specific than the mailbox preparation message.

If there are no useful errors, capture that too. Include the Entra object IDs, license plan states, creation times and diagnostic output in the support case so Microsoft can trace where provisioning stopped.

Reply to this answer
9h+claspwrench_374

Take a look at the recent onboarding automation changes as a separate track, especially if the affected count is growing quickly. Compare the attributes and license assignments on a manually created test user with one created by automation. That can help distinguish a shared service issue from something the workflow is setting.

Reply to this answer
3n!cobblewinder_826

There are reports of Microsoft support providing a PowerShell script for a similar provisioning problem, but the script and its purpose aren't available here. Ask support whether your tenant needs a remediation rather than running an unverified script. The symptoms alone don't establish that this is related to an outage or that the same fix applies.

Reply to this answer
_g48~fendrix.5

For the dynamic group angle, check the membership rules rather than assuming dynamic groups can no longer assign licenses. The discussion specifically corrected that claim to point to the memberOf rule operator, not dynamic groups as a whole.

Even if a rule needs attention, it wouldn't by itself explain a directly licensed test user getting stuck. Treat it as one thing to verify, not the answer to every affected account.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions