Add limitations for using the integrations synchronization feature (#3538)

This PR adds a limitations section to the [Automatic integrations
synchronization](https://www.elastic.co/docs/reference/fleet/automatic-integrations-synchronization)
doc.

Resolves elastic/ingest-docs#1853

Author: vishaangelova

reference/fleet/automatic-integrations-synchronization.md

@@ -26,6 +26,13 @@ This feature is available only for certain subscription levels. For more informa
 * Remote clusters must be running the same {{es}} version as the management cluster, or a newer version that supports {{ccr}}.
 * To install integrations, remote clusters require access to the [{{package-registry}}](/reference/fleet/index.md#package-registry-intro).
 
+## Limitations
+
+These limitations apply when using the automatic integrations synchronization feature:
+
+- [Index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md) (ILM) policies and enrich policies referenced in custom component templates are not automatically synchronized. Synchronizing custom assets that include references to ILM or enrich policies may cause custom component templates to break.
+- Integrations installed on the management cluster are synchronized to the remote cluster regardless of the space they are installed in. On the remote cluster, the synchronized integrations are always installed in the default space.
+
 ## Configure {{ccr}} on the remote cluster
 
 In your remote cluster: