fix: rename adx-cluster-grouping and remove missing image refs

- Rename adx-cluster-grouping.md to kusto-cluster-grouping.md to fix
  filename-incomplete warning (disallowed acronym)
- Remove 3 broken image references (media files never committed)
- Update toc.yml to point to renamed file

Co-authored-by: Copilot <[email protected]>

Author: craigshoemaker

…ticles/sre-agent/adx-cluster-grouping.md …cles/sre-agent/kusto-cluster-grouping.mdarticles/sre-agent/adx-cluster-grouping.md renamed to articles/sre-agent/kusto-cluster-grouping.md articles/sre-agent/adx-cluster-grouping.md renamed to articles/sre-agent/kusto-cluster-grouping.md

@@ -63,22 +63,16 @@ Ad-hoc queries work immediately with the connector. For Kusto tools, see [Kusto
 
 The ADX connector supports **multiple clusters in a single connector** through cluster groups. Each group shares a managed identity, so you don't need to create separate connectors for every cluster.
 
-:::image type="content" source="media/adx-cluster-grouping/step-03-add-clusters-form.png" alt-text="Screenshot showing the Add clusters step with group name, managed identity dropdown, and cluster URI fields.":::
-
 ### Cluster groups
 
 A cluster group is a collection of ADX cluster URIs that share the same managed identity. You can have multiple groups within one connector—each with its own identity—to handle clusters across different tenants or permission boundaries.
 
 For example, if your production clusters use one managed identity and your staging clusters use another, you create two groups within the same connector. The "(inherit)" option on each group uses the connector-level identity by default; override it per group when needed.
 
-:::image type="content" source="media/adx-cluster-grouping/step-03-add-clusters-empty.png" alt-text="Screenshot showing the Add clusters step with one cluster URI filled and an auto-added empty row.":::
-
 ### Per-cluster health checks
 
 The connector tests each cluster individually—both during setup and on an ongoing basis. If some clusters become unreachable after saving, the connector status calls out the failing clusters by name (for example, *"2 cluster(s) failed: cluster1, cluster2"*) so you know exactly which cluster needs attention.
 
-:::image type="content" source="media/adx-cluster-grouping/step-04-review-before-test.png" alt-text="Screenshot showing the Review and test connection step with connector summary and Test connection button.":::
-
 ### Edit connectors
 
 You can add or remove cluster URIs from an existing connector without recreating it. The edit dialog opens directly to the cluster configuration—update URIs, adjust group identities, and re-test.

articles/sre-agent/toc.yml

@@ -125,7 +125,7 @@ items:
           - name: Kusto tools
             href: kusto-tools.md
           - name: Azure Data Explorer connector
-            href: adx-cluster-grouping.md
+            href: kusto-cluster-grouping.md
           - name: MCP connectors
             href: mcp-connectors.md
       - name: Access