How to Fix Microsoft 365 Mailbox Stuck on Being Prepared
Question details
The user needs to resolve an issue where a newly created Microsoft 365 user account cannot access their email because the mailbox setup process is frozen.

- Product
- Microsoft 365 / Exchange Online
- Device & OS
- not provided
- Scenario
- Provisioning a new cloud-only user mailbox in the Microsoft 365 and Exchange Admin Center.
- Observed behavior
- The mailbox status is continuously stuck on 'The mailbox is being prepared' for more than 24 hours, the user is missing from the Exchange Admin Center, and reassigning the Office E3 license does not resolve the issue.
Ensure you have Exchange Administrator or Global Administrator privileges and have the MSOnline PowerShell module installed to execute the necessary diagnostic commands.
Diagnose and Resolve Provisioning Errors using PowerShell
Use Microsoft Online PowerShell to uncover hidden provisioning, identity, or licensing errors that are preventing the mailbox from completing its setup.
When standard administrative interfaces do not show the root cause of a stuck mailbox, PowerShell allows you to query the backend ObjectErrors for the specific user.
This method is highly effective for identifying hidden retention policy conflicts, duplicated aliases, or backend license syncing issues.
Confirm that the user account is completely new and that no previously deleted mailbox with the same name or alias is currently being held by an active retention policy.
Open PowerShell as an Administrator and execute the command 'Connect-MsolService'. Enter your Global Administrator credentials when prompted to authenticate your session.
Execute the following command, making sure to replace the email address with your user's actual principal name: '(Get-MsolUser -UserPrincipalName user@contoso.com).Errors.ErrorDetail.ObjectErrors.ErrorRecord.ErrorDescription | Format-List'.
Analyze the PowerShell output for specific license, identity, or provisioning failures. Once identified, correct the underlying issue in the Microsoft 365 Admin Center or provide these specific error logs to Microsoft Support for further assistance.

Switch to WPS Office for a Seamless and Free Productivity Experience
While complex mailbox provisioning errors require backend Microsoft Exchange administration, your everyday document tasks shouldn't be complicated or expensive. WPS Office is a powerful, lightweight, and completely free alternative to Microsoft Office, offering full compatibility with all your files without the hefty subscription fees.
- 1. Download WPS Office: Visit the official WPS website to download the free installation package for your Windows, Mac, or Linux operating system.
- 2. Install the Software: Run the downloaded installer and follow the simple on-screen instructions to install the application in minutes.
- 3. Open Your Files Instantly: Launch WPS Office and directly open your existing Microsoft Office documents with all original formatting preserved.

Frequently Asked Questions
Why does Microsoft 365 say the mailbox is being prepared for more than 24 hours?
This extended delay is typically caused by hidden background provisioning errors, licensing conflicts, or a situation where a previously deleted mailbox with the same alias is still protected by a retention policy.
How long does a new Microsoft 365 mailbox normally take to provision?
Under normal circumstances, a newly created Microsoft 365 mailbox should provision and become fully accessible within 15 to 30 minutes. Delays exceeding 24 hours indicate a backend error.
Can a Microsoft 365 retention policy block new mailbox creation?
Yes. If an old mailbox was deleted but is preserved by a retention or litigation hold, attempting to create a new user mailbox with the exact same User Principal Name (UPN) or email alias will result in backend provisioning conflicts.
Is PowerShell strictly necessary to fix a stuck mailbox?
While simple fixes like reassigning a license can be done in the web portal, PowerShell is often required to expose the specific backend ObjectErrors and ErrorDescriptions that are invisible in the standard Microsoft 365 Admin Center.




