fabric-operations-agentlisted

Use for the Microsoft Fabric Operations Agent item (preview) — `<Name>.OperationsAgent/` + `Configurations.json` — the autonomous LLM agent that queries one Eventhouse/KQL database or Ontology every 5 minutes, messages Teams, and can run a pipeline or notebook under its creator's delegated identity. Covers the draft-07 definition schema (`configuration`/`playbook`/`shouldRun` all required, `dataSource.type` KustoDatabase|Ontology, `action.kind` FabricJobAction|PowerAutomateAction with `connection` required iff the first, Recipient|TeamsChannel `messageDestination`, `identity.sponsor`), the ALM traps (Git integration lists it under Data Factory not RTI; `shouldRun: true` deploys a running 0.46 CU-hour/hour meter; `dataSources` accepts a `$(/ws/lib/var)` reference the variable-library docs omit; `jobArtifactId` is the target's byte-reversed `logicalId`), serializer artifacts (absent `playbook`, duplicate `kind` key, parameter values in `description`), state vs transition conditions, and `fab` reach.
wardawgmalvicious/agent-config · ★ 0 · AI & Automation · score 78

Install: claude install-skill wardawgmalvicious/agent-config

# Fabric Operations Agent: the definition file and its ALM consequences Everything below was verified **2026-09-02**. The item, its Git integration, its deployment-pipeline support and Investigator insights are all **preview** — re-check dated claims before relying on them. This skill is about the *file*. The portal click-path is documented and not repeated here; what is not documented is what `Configurations.json` means once it is committed. ## 1. Item identity | Fact | Value | | --- | --- | | `.platform` `metadata.type` | `OperationsAgent` | | Folder | `<Name>.OperationsAgent/` | | Definition part | `Configurations.json` — **plural, capital C**, not `<name>.json` | | Schema | `https://developer.microsoft.com/json-schemas/fabric/item/operationsAgents/definition/1.0.0/schema.json` | Two files per item and nothing else. **The REST docs do not list this item type.** [Item definition overview](https://learn.microsoft.com/rest/api/fabric/articles/item-management/definitions/item-definition-overview) enumerates ~30 types under *Definition Details for Supported Item Types* and Operations Agent is not among them. That is not evidence of "no item definition" — the schema above is live and returns 200. Same pattern as `fabric-realtime-dashboard` and `fabric-graph`: a hand-editable definition whose contract lives at a schema URL rather than in the API reference. **One item type, two front doors.** Real-Time Intelligence documents the general item; Data Factory documents [Operati