stopped-server-down azure ad connect

Question

I am in the process of moving azure ad connect from one domain to another as part of a domain migration. A colleague recommended that after I stop synchronization on the old ad connect server that I shut it down and proceed with the new aad connect install in the target domain. I hard matched the accounts and synchronization was running properly. The old aad connect server was brought back online the next day and and it displayed a series of synchronization errors. I stopped synchronization on the old aad connect server using the command Set-ADSyncScheduler -SyncCycleEnabled $FALSE. I then uninstalled aad connect on the older server. At this point on the new server a stopped-server-down error was observed in the sync service manager on the new aad connect install. My assumption is that disabling sync on the old aad connect server prior to uninstallation is the cause. When I attempt to restart synchronization using Set-ADSyncScheduler -SyncCycleEnabled $TRUE on the new aad connect server I get the error below:

Set-ADSyncScheduler -SyncCycleEnabled $TRUE
Set-ADSyncScheduler : Microsoft.Online.Coexistence.ProvisionException: An error occurred. Error Code: 15. Error Description: Identity synchronization is not yet activated for this company. To activate Identity synchronization, click the Activate button on
the Identity synchronization page in your Admin Portal. Tracking ID: 5c69bcdd-2978-44bd-8fe6-5a5343c23985 Server Name: . ---> System.ServiceModel.FaultException`1[Microsoft.Online.Coexistence.Schema.AdminWebServiceFault]: Identity synchronization is not
yet activated for this company. To activate Identity synchronization, click the Activate button on the Identity synchronization page in your Admin Portal.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:

I am thinking this is because synchronization has not stopped per the 72 hour SLA instituted by Microsoft but I would like confirmation. Has anyone experienced this before?

Answer 1

@jpcapone Thanks for reaching out. Yes that pretty much shows that you have to wait for 72 hours.
Here are the important things to note :

1) If you enabled directory synchronization for the first time, activation may require up to 24 hours.
2) If you re-enabled directory synchronization, activation may require up to 72 hours. For more information, see Can't manage or remove objects that were synchronized through the Azure Active Directory Sync tool.
3) If you disabled directory synchronization, deactivation may require up to 72 hours.

You can read more about here : https://learn.microsoft.com/en-us/office365/troubleshoot/active-directory/pending-state-issue-with-directory-synchronization

---

If the suggested response helped you resolve your issue, do click on "Mark as Answer" and "Up-Vote" for the answer that helped you for benefit of the community.