Repo sync for protected branch

data-explorer/ingest-data-streaming.md

@@ -561,6 +561,7 @@ class Program
 * [Data mappings](/kusto/management/mappings?view=azure-data-explorer&preserve-view=true) must be [pre-created](/kusto/management/create-ingestion-mapping-command?view=azure-data-explorer&preserve-view=true) for use in streaming ingestion. Individual streaming ingestion requests don't accommodate inline data mappings.
 * [Extent tags](/kusto/management/extent-tags?view=azure-data-explorer&preserve-view=true) can't be set on the streaming ingestion data.
 * [Update policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true). The update policy can reference only the newly ingested data in the source table and not any other data or tables in the database.
+* For cascading [update policies](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true) that include a `join` operator, you must disable streaming ingestion on all upstream tables. For example, consider cascading update policies where Table1 updates Table2, Table2 updates Table3, and Table3 updates Table4. If Table4's update policy includes a join, you must disable streaming ingestion on Table1, Table2, and Table3.
 * When an update policy with a [transactional policy](/kusto/management/update-policy?view=azure-data-explorer&preserve-view=true#handling-failures) fails, the retries fall back to batch ingestion.
 * If streaming ingestion is enabled on a cluster used as a leader for [follower databases](follower.md), streaming ingestion must be enabled on the following clusters as well to follow streaming ingestion data. Same applies whether the cluster data is shared via [Data Share](data-share.md).
 

data-explorer/kusto/includes/applies-to-version/applies.md

@@ -2,4 +2,6 @@
 ms.topic: include
 ms.date: 08/11/2024
 ---
-Applies to:
+
+Select a service from the **drop-down list** to the left. <br/>
+Applies to:

data-explorer/kusto/management/update-policy.md

@@ -74,6 +74,8 @@ If the update policy is defined on the target table, multiple queries can run on
 
 * By default, the [Streaming ingestion policy](streaming-ingestion-policy.md) is enabled for all tables in the Eventhouse. To use functions with the [`join`](../query/join-operator.md) operator in an update policy, the streaming ingestion policy must be disabled. Use the `.alter` `table` *TableName* `policy` `streamingingestion` *PolicyObject* command to disable it.
 
+* For cascading update policies that include a [`join`](../query/join-operator.md) operator, you must disable streaming ingestion on all upstream tables. For example, consider cascading update policies where Table1 updates Table2, Table2 updates Table3, and Table3 updates Table4. If Table4's update policy includes a join, you must disable streaming ingestion on Table1, Table2, and Table3.
+
 * The update policy's query shouldn't reference any materialized view whose query uses the update policy's target table. Doing so might produce unexpected results.
 
 ::: moniker-end
@@ -360,4 +362,4 @@ Any ingestion to a table which matches the pattern (in local database) will trig
 ## Related content
 
 * [Common scenarios for using table update policies](update-policy-common-scenarios.md)
-* [Tutorial: Route data using table update policies](update-policy-tutorial.md)
+* [Tutorial: Route data using table update policies](update-policy-tutorial.md)