Fix Azure AD Connect Directory Synchronization Pending Disable Errors
Question details
The user needs to resolve an Azure AD Connect directory synchronization error that shows a pending disable state and prevents reinstalling the sync tool.

- Product
- Microsoft 365 / Azure AD Connect
- Device & OS
- not provided
- Scenario
- An administrator checks or reinstalls Azure AD Connect after directory synchronization changes and encounters a PendingDisable status.
- Observed behavior
- Directory synchronization remains in a PendingDisable state, and the change can take up to 72 hours before it completes.
Before changing any synchronization settings, run the Microsoft Online PowerShell commands to record the current DirectorySynchronizationEnabled and DirectorySynchronizationStatus values. Make sure the MSOnline PowerShell module is installed and you can connect with Microsoft 365 admin credentials.
Check the Microsoft 365 directory synchronization state with Microsoft Online PowerShell
Use this solution first to confirm whether directory synchronization is still enabled and whether the status is PendingDisable.
The Microsoft Online PowerShell cmdlets return the current tenant synchronization state. Do not reinstall Azure AD Connect until the status has finished updating.
On a Windows server or workstation with the MSOnline module installed, open Windows PowerShell as an administrator and connect using a Microsoft 365 global admin account.
Run (Get-MsolCompanyInformation).DirectorySynchronizationEnabled and (Get-MsolCompanyInformation).DirectorySynchronizationStatus, then review the returned values.
If DirectorySynchronizationEnabled returns True, directory synchronization is still active. If DirectorySynchronizationStatus returns PendingDisable, wait for the status to change to Disabled before reinstalling Azure AD Connect.

Disable directory synchronization and wait for the pending state to clear
Use this solution when DirectorySynchronizationEnabled is still True and you need to complete the pending disable process.
Escalate a stuck PendingDisable state to Microsoft Support
Use this solution if the directory synchronization status still shows PendingDisable after 72 hours.
Use WPS Office as a Free, Lightweight Microsoft 365 Alternative for Everyday Documents
While Azure AD Connect and Microsoft 365 directory synchronization issues can take up to 72 hours to resolve, WPS Office lets you continue working with Word, Excel, PowerPoint, and PDF files for free. It offers a familiar ribbon interface and strong format compatibility with Microsoft Office files.
- 1. Download WPS Office: Go to the WPS Office download page and click Download WPS Office Free.
- 2. Open existing Microsoft Office files: Launch WPS Office and open your DOCX, XLSX, or PPTX files from the File menu.
- 3. Edit and save in Microsoft-compatible formats: Edit the document and save it back to DOCX, XLSX, or PPTX as needed.

Frequently Asked Questions
What does directory synchronization PendingDisable mean in Microsoft 365?
It means Microsoft 365 has not finished processing a previous synchronization change. The status can remain PendingDisable for up to 72 hours before it changes to Disabled.
How do I check whether Azure AD Connect directory synchronization is still enabled?
Open Microsoft Online PowerShell, connect with a Microsoft 365 admin account, and run (Get-MsolCompanyInformation).DirectorySynchronizationEnabled. A result of True means directory synchronization is still enabled.
Can I reinstall Azure AD Connect while the status is PendingDisable?
No. Wait for (Get-MsolCompanyInformation).DirectorySynchronizationStatus to return Disabled, otherwise the reinstallation may continue to fail.
How long should I wait for the pending disable state to clear?
Wait up to 72 hours. If the status remains PendingDisable after that, collect the PowerShell command results and contact Microsoft Support for backend investigation.
What should I provide to Microsoft Support for a stuck PendingDisable status?
Provide the output of (Get-MsolCompanyInformation).DirectorySynchronizationEnabled and (Get-MsolCompanyInformation).DirectorySynchronizationStatus, plus the tenant details and the date the issue started.




