'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Exchange Online User Still Blocked After Restricted Entities Removal
Question details
An Exchange Online user cannot send emails even after being removed from the Restricted entities list.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- An administrator has removed a blocked user account from the Restricted entities list to restore outbound email capabilities, but the unblocking process fails to take effect.
- Observed behavior
- The user remains blocked from sending email several hours after removal. Additionally, attempting to remove the block via PowerShell returns a transient database error.
Ensure you have waited at least a few hours since removing the user from the Restricted entities list, as standard backend replication in Microsoft 365 can occasionally be delayed.
Submit a Service Request via Microsoft 365 Admin Center
Use this solution to engage Microsoft Support, as persistent blocking accompanied by PowerShell database errors requires backend intervention.
When removing an account from the Restricted entities list fails and returns transient database errors in PowerShell, the problem is beyond tenant-level administrative controls. The restriction likely involves deeper backend or account-level outbound spam mechanisms that Microsoft Support must inspect and clear manually.
Open a web browser and log into the Microsoft 365 Admin Center (admin.microsoft.com) using your global administrator credentials.
On the bottom right corner or the left-hand navigation pane, click on the 'Help & support' option to open the support assistant.
Type a brief description of the problem, specifically mentioning the 'transient database error' encountered in PowerShell. Proceed to create a new service ticket for the technical support team.
If you purchased your Microsoft 365 subscription through a reseller or Cloud Solution Provider (CSP), contact them directly. They are authorized to escalate the backend unblocking request to Microsoft on your behalf.
Keep Productivity High with WPS Office
While waiting for Microsoft Support to resolve your Exchange Online server issues, ensure your daily documentation tasks are uninterrupted. WPS Office offers a free, lightweight, and highly compatible suite for your word processing, spreadsheet, and presentation needs.
- 1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the Software: Run the downloaded file and follow the on-screen instructions to complete the fast installation process.
- 3. Start Creating: Launch WPS Office to immediately open, edit, and save your existing Microsoft Office documents without any formatting loss.
Frequently Asked Questions
How long should it take for a user to be unblocked from Restricted Entities?
Typically, once a user is removed from the Restricted entities page in the Microsoft 365 Defender portal, the restriction is lifted within 1 to 24 hours depending on server replication.
What does a transient database error mean in Exchange Online PowerShell?
A transient database error generally indicates temporary communication or synchronization failures between Microsoft's backend server clusters. It means the system could not execute your command at that specific moment.
How can I check if a user is on the Restricted entities list?
Go to the Microsoft 365 Defender portal, navigate to 'Email & collaboration', click on 'Review', and select 'Restricted entities'. This page displays all accounts currently blocked from sending outbound emails.
