If you’ve just created a new Microsoft 365 tenant and the Exchange Admin Centre (EAC) won’t load, you may be dealing with an Exchange Online provisioning failure. This article covers the symptoms, root cause, and a proven workaround to get things working quickly.
Symptoms
After creating a new Microsoft 365 tenant and assigning licences (such as Microsoft 365 Business Standard), you may notice:
- The Exchange Admin Centre fails to load entirely, showing the error: “Parsing of Response Content Failed in API Operations”
- The classic Exchange Admin Centre (ECP) is also unreachable
- Exchange Online PowerShell (
Connect-ExchangeOnline) fails to establish a connection - No mailboxes can be created, no aliases can be set, and mail migration cannot proceed
- Other Microsoft 365 services (Teams, SharePoint, etc.) may work fine
These symptoms typically persist for days and don’t resolve on their own, even after waiting well beyond the usual provisioning window.
Root Cause
This issue is caused by a failure in Microsoft’s automated provisioning of the Exchange Online service for the new tenant. Normally, when a new tenant is created with licences that include Exchange Online, Microsoft’s backend spins up the Exchange Online environment (sometimes called the “Exchange organisation”) within minutes to a few hours.
In this scenario, that process fails silently. The tenant ends up in a semi-configured state where Exchange Online was never fully initialised. Any requests related to Exchange (whether through the admin centre, classic ECP, or PowerShell) return errors because there’s no properly provisioned Exchange instance to connect to.
The “Parsing of Response Content Failed in API Operations” error is a an indicator of this. It means the Exchange service is returning malformed or unexpected data because the service isn’t there.
This is not caused by admin error or misconfiguration. It’s a backend issue on Microsoft’s side.
Initial Troubleshooting (What Won’t Work)
Before jumping to the fix, here’s what we tried that did not resolve the issue:
- Waiting for propagation: The issue persisted for several days with no improvement
- Using PowerShell instead of the web portal: Exchange Online PowerShell also failed, confirming the issue is with the service itself, not just the web interface
- Logging in with a different Global Administrator account: Same behaviour, ruling out account-specific problems
- Raising a support case with Microsoft (via CSP): While this is the correct escalation path, the timeline for Microsoft to investigate and re-provision the Exchange service can be lengthy
Resolution: Force Exchange Provisioning with an Exchange Online Plan 2 Licence
The fastest way to resolve this is to force Exchange to re-provision by adding a standalone Exchange Online licence to the tenant. Here’s how:
- Go to the Microsoft 365 Admin Centre for the affected tenant (you can also do this via your Microsoft licensing provider)
- Navigate to Billing > Purchase services
- Search for Exchange Online (Plan 2) and add it to the tenant (you can buy a monthly subscription and cancel it once it resolves things)
- Assign the Exchange Online Plan 2 licence to one of the tenant’s user accounts - however it worked for us without assigning this first.
- Wait a few minutes, then try accessing the Exchange Admin Centre again
By introducing a new Exchange SKU into the tenant’s subscriptions, you’re essentially forcing the Microsoft 365 platform to set up the necessary Exchange infrastructure that it failed to create during initial provisioning.
In our case, the Exchange Admin Centre loaded without error immediately after the Plan 2 licence was assigned. All functionality became available at once, including mailbox creation, alias management, and PowerShell connectivity.
After the Fix
Once the Exchange environment is confirmed working:
- Proceed with mailbox creation, migration, and configuration as normal
- The Exchange Online Plan 2 licence can potentially be removed after the environment is fully provisioned and stable (test this carefully before removing it)
- If you opened a support case with Microsoft, update it with the resolution so they can investigate the root cause on their end
Prevention Tips
There’s no guaranteed way to prevent a Microsoft cloud provisioning bug from your side, but these practices can help you catch it early:
- Verify core services immediately after tenant creation: After assigning licences, confirm that Exchange, SharePoint, and Teams are all accessible before proceeding with configuration
- Use both the portal and PowerShell to diagnose: If the admin centre isn’t working, try PowerShell (and vice versa). If both fail, the problem is with the service itself
- Escalate quickly: For issues where an entire service is non-functional for a new tenant, raise a support case at critical priority immediately. Don’t wait days hoping it will self-resolve
- Keep this licence trick in your back pocket: Adding a standalone Exchange Online Plan 2 licence to force re-provisioning is a reliable workaround that can save you days of waiting for Microsoft support
Key Takeaway
When core Microsoft 365 services don’t initialise properly for a new tenant, the fix typically involves getting Microsoft to re-run the provisioning process. You can either wait for Microsoft support to do this through official channels, or use the licence-based workaround described above to kick-start the process yourself. This approach resolved our issue immediately and allowed us to get the customer’s email service online without further delay.
If you’re experiencing this issue or need help setting up a new Microsoft 365 tenant, get in touch with our team.
