Can't disable EntraID Connect Sync (Pending state)

Question

Can't disable EntraID Connect Sync (Pending state)

Dzenan Celhasic 0

$tenantID = (Get-EntraContext).TenantId
Set-EntraDirSyncEnabled -EnableDirsync $false -TenantId $tenantID -Force

Error: Requested change of DirSync status is not allowed. Cannot Disable DirSync while enable is pending

Thanmayi Godithi 11,905 Reputation points Microsoft External Staff Moderator

2026-03-13T18:52:08.08+00:00
Hey @Dzenan Celhasic, it looks like you're trying to disable EntraID Connect Sync but are running into a "pending state" issue. This can happen when there’s an ongoing process for enabling DirSync that hasn’t finished yet.

Here’s what you can do:

Verify the Status: Before trying to disable DirSync, check the current status to see if the enable process is still pending. You can do this with:
Get-EntraDirSyncStatus -TenantId $tenantID

Wait for Completion: If the status indicates that the enable process is pending, you might need to wait for it to complete. Sometimes this can take a few hours depending on the system load.

Retry Disabling: After confirming that there’s no longer a pending operation, you can try executing your original command again:
Set-EntraDirSyncEnabled -EnableDirsync $false -TenantId $tenantID -Force

Force the Process: If you continue to have issues after the status has confirmed that the enable process is complete, you might want to consider reaching out to Microsoft support for further assistance.

Hope this helps! If you need more specific steps or face any further issues, let me know!

1 answer

Your answer

Thanmayi Godithi 11,905 Reputation points Microsoft External Staff Moderator

2026-03-13T18:52:08.08+00:00

Hey @Dzenan Celhasic, it looks like you're trying to disable EntraID Connect Sync but are running into a "pending state" issue. This can happen when there’s an ongoing process for enabling DirSync that hasn’t finished yet.

Here’s what you can do:

Verify the Status: Before trying to disable DirSync, check the current status to see if the enable process is still pending. You can do this with:
Get-EntraDirSyncStatus -TenantId $tenantID

Wait for Completion: If the status indicates that the enable process is pending, you might need to wait for it to complete. Sometimes this can take a few hours depending on the system load.

Retry Disabling: After confirming that there’s no longer a pending operation, you can try executing your original command again:
Set-EntraDirSyncEnabled -EnableDirsync $false -TenantId $tenantID -Force

Force the Process: If you continue to have issues after the status has confirmed that the enable process is complete, you might want to consider reaching out to Microsoft support for further assistance.

Hope this helps! If you need more specific steps or face any further issues, let me know!

Answer 1

The error indicates that a previous operation to enable directory synchronization (DirSync) is still in a pending state, so a disable request is blocked until that operation completes.

Behavior from the cmdlet documentation:

Set-EntraDirSyncEnabled turns directory synchronization on or off for the tenant.
Deactivating DirSync may take up to 72 hours, depending on the number of objects in the subscription.
Once a DirSync state change is in progress, it cannot be canceled and must complete before any further action (including re-enabling or disabling DirSync) can be taken.

In this situation:

Wait for the current DirSync state change (the pending enable) to fully complete. This can take significant time depending on tenant size.

After the enable operation has finished and the tenant is in a stable state, run the disable command again:

   Connect-Entra -Scopes 'OnPremDirectorySynchronization.ReadWrite.All', 'Organization.ReadWrite.All'
   $tenantID = (Get-EntraContext).TenantId
   Set-EntraDirSyncEnabled -EnableDirsync $false -TenantId $tenantID -Force

If BlockCloudObjectTakeoverThroughHardMatch is enabled and DirSync is later re-enabled, on-premises to cloud object takeover/updates for Microsoft Entra ID–mastered objects will be blocked until that setting is set to false.

References: