Account Locked & Blocked

How to Fix Microsoft 365 Error When Unblocking a Restricted User

Emma BrownEmma Brown Oct 7, 2026 869 views

Question details

Administrators are unable to unblock restricted users in Microsoft 365 through the portal or PowerShell due to persistent system errors.

How to Fix Microsoft 365 Error When Unblocking a Restricted User
Product
Microsoft 365
Device & OS
not provided
Scenario
An administrator attempts to unblock a restricted user account but encounters failures and system errors instead of a successful unblock.
Observed behavior
The unblock operation fails after approximately 36 hours, displaying GUI and PowerShell errors related to the Hygiene DAL retrying a transient condition.
Before you start

Ensure you have Global Administrator or Security Administrator privileges in Microsoft 365 before attempting to manage restricted user accounts or access the service health dashboard.

Solution 1Recommended

Check Service Health and Contact Microsoft Support

Use this solution because this specific error is typically associated with a known service-side issue (such as Advisory DZ769160) that requires intervention from Microsoft.

When the GUI and PowerShell report errors related to the Hygiene DAL retrying a transient condition, the issue is often on Microsoft's backend.

Standard administrative actions like password changes, session revocations, and MFA resets usually will not resolve this specific service-side restriction.

1
Access the Microsoft 365 Admin Center

Sign in to the Microsoft 365 admin center using your Global Administrator credentials.

2
Check the Service Health Dashboard

Navigate to Health > Service health in the left menu. Look for any active advisories regarding restricted users, specifically referencing Advisory DZ769160.

3
Open a Support Request

If the advisory is active or the user remains blocked after 36 hours, navigate to Support > Help & support. Enter your issue details and click the headset icon to contact Microsoft support for backend intervention.

Check Service Health and Contact Microsoft Support
Microsoft Intervention Required: Because the cmdlet pipeline and Hygiene DAL are failing on the server side, only Microsoft support can force the unblock process for the affected tenant.
Free Microsoft Office alternative

Try WPS Office for Seamless and Hassle-Free Document Management

While you wait for Microsoft to resolve complex administrative backend errors, ensure your team stays productive with WPS Office. It is a lightweight, independent suite that allows you to continue your work without relying on web-based admin portals.

  1. 1. Visit the WPS Website: Go to the official WPS Office website using your preferred web browser.
  2. 2. Download the Installer: Click the 'Free Download' button to get the correct version for your operating system.
  3. 3. Install and Launch: Open the downloaded file, follow the quick installation prompts, and start creating documents immediately.
Highly compatible with Microsoft Word, Excel, and PowerPoint formatsLightweight and fast installation without complex admin requirementsFree to use with an intuitive, familiar tabbed interfaceBuilt-in PDF editing and format conversion tools
microsoft office alternative - wps office

Frequently Asked Questions

Why am I getting a Hygiene DAL error in PowerShell when unblocking a user?

This error occurs when the Microsoft backend system retries a transient condition but fails after reaching the maximum number of attempts. It is a known service-side issue (documented under Microsoft Service Health Advisory DZ769160) and is not caused by your local configuration.

Will resetting the user's password fix the restricted user block?

Typically, changing the password is required to secure the account before unblocking. However, during this specific service outage, password changes, MFA resets, and session revocations will not resolve the service-side restriction blocking the account.

How long does it normally take to unblock a restricted user in Microsoft 365?

Under normal circumstances, a user is unblocked within 1 to 24 hours after an admin releases them from the portal. If the process exceeds 36 hours and throws GUI or cmdlet errors, it indicates a service-side problem requiring Microsoft support.