This page provides important notes and lists limitations of the sync process:

Services on the target domains will be unavailable for a period of a few minutes or more during synchronization.
It is the user's responsibility to reroute traffic to other devices (e.g. by providing pre/post customer supplied scripts).

It is the user's responsibility to verify the functionality of the target domain, as failure in synchronization may leave the domain in an inconsistent state.

Sync is only supported for devices with firmware levels higher than 7.2.0.0
This Sync feature does NOT replace DevOps tools, it is not aimed for promoting configuration from one environment to another
This Sync feature will NOT synchronize services in the "default" domain
This Sync feature will NOT synchronize API Connect domains
It is the user's responsibility to create the target domains; The Sync feature will not create them automatically.
This sync feature does NOT support IDG Docker containers
This sync feature will only synchronize persisted configuration
The target domain will be deleted and no objects will be imported if there are errors in the supplied deployment policy
Sync is done on a domain level (entire domains only)
This sync feature will NOT synchronize key material (certificates, Kerberos keytabs, etc.)
Password map/alias synchronization is available only when both source and target devices have a firmware level of 7.5.2.4 or above and the Password map/alias synchronization is available only when both source and target devices have a firmware level of 7.5.2.4 or above and the passphrase in both source and target match

Browser not supported