Others

How to Fix DirectorySynchronizationStatus PendingDisabled in Azure AD

Chanuka GeekiyanageChanuka Geekiyanage Oct 22, 2026 868 views

Question details

The user needs to resolve an issue where Azure AD Connect synchronization remains stuck in a PendingDisabled state after running a PowerShell command.

How to Fix DirectorySynchronizationStatus PendingDisabled in Azure AD
Product
Azure AD Connect / Microsoft 365
Device & OS
not provided
Scenario
Managing directory synchronization using the Set-MsolDirSyncEnabled PowerShell cmdlet.
Observed behavior
The directory synchronization status remains PendingDisabled for over 72 hours without completing the requested change.
Before you start

Ensure you have global administrator privileges in your Azure AD tenant and have waited the standard 24 to 72 hours for synchronization status changes to process before troubleshooting.

Solution 1Recommended

Check Azure AD Connect Status Report and Escalate to Support

Identify potential blocking errors in the Azure portal and contact Microsoft Support if the synchronization remains stuck beyond 72 hours.

Disabling or changing directory synchronization can normally take anywhere between 24 and 72 hours, depending on the size of your directory and the number of objects. If it exceeds this timeframe, an underlying service error is likely blocking the operation.

1
Log in to the Azure Portal

Navigate to the Azure portal in your web browser and sign in using your Microsoft 365 Global Administrator credentials.

2
Review Azure AD Connect Health

Go to Azure Active Directory, select Azure AD Connect from the left pane, and carefully review the status report for any active sync errors or warnings that could be halting the process.

3
Contact Microsoft 365 Support

If no specific errors are listed and the directory sync status remains PendingDisabled after 72 hours, open a support ticket with Microsoft 365 Support from your admin center to clear the backend sync queue.

Check Azure AD Connect Status Report and Escalate to Support
Avoid Repeated Commands: Do not attempt to repeatedly run the Set-MsolDirSyncEnabled cmdlet while the status is pending, as this will not speed up the process and may cause further delays.
Free Microsoft Office alternative

Looking for a Seamless and Free Microsoft Office Alternative?

While managing complex administrative tasks like Azure AD synchronization, ensure your team's everyday document productivity remains uninterrupted. WPS Office offers a lightweight, highly compatible, and cost-effective alternative to Microsoft Office for all your word processing, spreadsheet, and presentation needs.

Fully compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Lightweight design that uses minimal system resources.Familiar user interface ensuring a zero-learning-curve transition for your team.Includes robust built-in PDF editing and conversion tools.
microsoft office alternative - wps office

Frequently Asked Questions

How long does it normally take to disable directory synchronization in Azure AD?

Disabling directory synchronization typically takes between 24 and 72 hours, depending heavily on the size of your Active Directory and the total number of objects being processed in the cloud.

Can I force the synchronization status to change from PendingDisabled manually?

No, you cannot force the status change manually using PowerShell. If it remains stuck for more than 72 hours without any visible errors in the Azure AD Connect health report, you must contact Microsoft Support to resolve the backend queue.

Where can I find detailed synchronization errors in Azure?

Synchronization errors can be found in the Azure portal by navigating to Azure Active Directory, selecting Azure AD Connect, and reviewing the detailed synchronization status and health reports provided on the dashboard.