Merge pull request #3169 from MicrosoftDocs/main639198184568873807sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/graph/gql-language-guide.md

@@ -202,10 +202,10 @@ This query runs as follows:
 
 Now find people with specific characteristics. In this case, find everyone named Alice and show their names and birthdays.
 
-<!-- GQL Query: Checked 2025-11-17 -->
+<!-- GQL Query: Checked 2026-07-15 -->
 ```gql
 MATCH (p:Person)
-FILTER p.firstName = 'Annemarie'
+FILTER p.firstName = 'Alice'
 RETURN p.firstName, p.lastName, p.birthday
 ```
 
@@ -280,12 +280,12 @@ RETURN fullName, c.name AS companyName            -- Input: top 10 rows table
 
 This query runs as follows:
 
-1. **`MATCH`** finds people who work at companies with "Air" in their name.
+1. **`MATCH`** finds people who work at companies.
 1. **`LET`** creates full names by combining first and family names.
-1. **`FILTER`** keeps only Contoso employees.
+1. **`FILTER`** keeps only employees of companies with "Air" in their company name.
 1. **`ORDER BY`** sorts by full name.
 1. **`LIMIT`** takes the first 10 results.
-1. **`RETURN`** returns names and company locations.
+1. **`RETURN`** returns full names and company names.
 
 ### Variables connect your data
 
@@ -382,15 +382,15 @@ Start with basic relationship patterns:
 
 **Patterns with specific data:**
 
-<!-- GQL Pattern: Checked 2025-11-17 -->
+<!-- GQL Pattern: Checked 2026-07-15 -->
 ```gql
--- Find who works at Microsoft specifically
+-- Find employees named Alice
 (p:Person)-[:workAt]->(c:Company)
-WHERE p.firstName = 'Annemarie'
+WHERE p.firstName = 'Alice'
 
--- Find friends who are both young
+-- Find friends who both have birthdays after December 31, 1999
 (p:Person)-[:knows]->(f:Person)  
-WHERE p.birthday > 19950101 AND f.birthday > 19950101
+WHERE p.birthday > 19991231 AND f.birthday > 19991231
 ```
 
 **Label expressions for flexible entity selection:**

docs/real-time-intelligence/anomaly-detection.md

@@ -1,10 +1,10 @@
 ---
 title: Anomaly Detection in Real-Time Intelligence
 description: Learn how to set up and configure anomaly detection for your real-time data streams using Microsoft Fabric Real-Time Intelligence.
-ms.reviewer: tessarhurr, v-hzargari
+ms.reviewer: tessarhurr, hzargari-ms
 ms.topic: how-to
 ms.subservice: rti-anomaly-detector
-ms.date: 07/06/2026
+ms.date: 07/12/2026
 ms.search.form: Anomaly Detection How To
 ai-usage: ai-assisted
 ---
@@ -30,7 +30,7 @@ Anomaly detection runs natively on Eventhouse tables without copying data, opera
 - Role of **Admin**, **Contributor**, or **Member** [in the workspace](../fundamentals/roles-workspaces.md).
 - An [Eventhouse](create-eventhouse.md) in your workspace with a KQL database.
 - A Python plugin enabled on that same Eventhouse.
-  1. To enable the plugin, navigate to your Eventhouse.
+  1. To enable the plugin, go to your Eventhouse.
   1. In the upper toolbar, select **Plugins** and then enable the **Python language extension**.
   1. Select the Python 3.11.7 DL plugin and select **Done**.
 
@@ -82,11 +82,11 @@ You can start anomaly detection in **three** ways:
 
 ## [From the Create button](#tab/create)
 
-1. In the Fabric home page, select the ellipsis (⋯) icon and then the **Create** option.
+1. In the Fabric home page, select the ellipsis (⋯) icon and then select **Create**.
 
     :::image type="content" source="media/anomaly-detection/create-button.png" alt-text="Screenshot of the Create button in the left navigation pane.":::
 
-1. In the **Create** pane, select **Anomaly detection** under the **Real-Time Intelligence** section.
+1. In the **Create** pane, under the **Real-Time Intelligence** section, select **Anomaly detection**.
 
     :::image type="content" source="media/anomaly-detection/create-anomaly-detection.png" alt-text="Screenshot of the Create pane with Anomaly detection selected.":::
 
@@ -100,6 +100,24 @@ You can start anomaly detection in **three** ways:
 
 ----
 
+### View existing anomaly detection configurations
+
+Before you create a new anomaly detector, check whether an anomaly detection configuration already exists for the data source you selected. This view gives you quick visibility into how anomaly detection is currently set up for that data source. It helps you avoid duplicate work and better understand how others use the data.
+
+1. In your list of data sources, select the ellipsis **(...)** for the data source you want to analyze, and then select **Existing anomaly detector**.
+
+    :::image type="content" source="media/anomaly-detection/existing-anomaly-detector.png" alt-text="Screenshot of the Existing anomaly detector option in the ellipsis list." lightbox="media/anomaly-detection/existing-anomaly-detector.png":::
+
+1. In **View anomalies detected**, you can view all existing anomaly detection configurations for the selected data source and explore the details of each.
+
+    1. From the left navigation pane, select a configuration to explore the detected anomalies, or select **Open** to view it in full screen.
+
+    1. If the existing configurations don't meet your needs, select **New** to create a new anomaly detection configuration.
+
+    :::image type="content" source="media/anomaly-detection/existing-configuration-details.png" alt-text="Screenshot of the details view for an existing anomaly detection configuration." lightbox="media/anomaly-detection/existing-configuration-details.png":::
+
+This experience helps you move quickly from exploration to action, without leaving the context of your data source.
+
 ### Configure input columns for analysis
 
 Specify which columns to analyze and how to group your data.
@@ -191,7 +209,7 @@ For more information, see:
 
 ## Limitations and considerations
 
-Be aware of these current limitations:
+Be aware of these limitations:
 
 - Anomaly detection is disabled if the input table doesn't match the required schema (numeric value column, datetime column, and string column).
 - Sufficient historical data improves model recommendations and accuracy.
@@ -215,9 +233,9 @@ To avoid problems:
 
 For more information, see [Python Plugin](/kusto/query/python-plugin?view=microsoft-fabric&preserve-view=true).
 
-## Wait times for enabling the Python Plugin
+## Wait times for enabling the Python plugin
 
-When you start data analysis, the anomaly detector automatically enables the Python Plugin on your Eventhouse. Enabling the plugin can take up to one hour. Once enabled, the analysis starts automatically.
+When you start data analysis, the anomaly detector automatically enables the Python plugin on your Eventhouse. Enabling the plugin can take up to one hour. Once enabled, the analysis starts automatically.
 
 For more information, see [Enable Python plugin in Real-Time Intelligence](python-plugin.md).