Dataflows Authoring Cli
Create, update, delete, and refresh Fabric Dataflows Gen2 via write-side CLI against Fabric Items and Connections APIs. Builds mashup.pq + queryMetadata definitions, triggers parameterized refreshes, manages connections, and configures output destinations (Lakehouse, Warehouse, ADX, Azure SQL). Includes preview-driven authoring loop (executeQuery + customMashupDocument). For executing saved queries or reading refresh status, use `dataflows-consumption-cli`. Triggers: "create dataflow", "update dataflow", "delete dataflow", "trigger dataflow refresh", "refresh dataflow", "preview Power Query M", "preview mashup", "preview before save", "iterate dataflow M", "create Fabric data source connection", "create dataflow connection", "bind connection", "list supportedConnectionTypes", "dataflow output destination", "dataflow write to lakehouse", "dataflow write to warehouse", "dataflow write to ADX", "DataDestinations annotation", "author dataflow".
30-Second Summary
Dataflows Authoring Cli is an agent-readable workflow from microsoft/skills-for-fabric for dataflows authoring cli.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating dataflows authoring cli as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Dataflows Authoring Cli packages instructions from microsoft/skills-for-fabric into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around dataflows authoring cli and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match dataflows authoring cli, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to microsoft/skills-for-fabric. Risk boundary: git state, commit, branch, PR, or push actions require explicit repo-owner approval before mutation; CI/CD, deploy, release, rollback, and migration steps must start with read-only inspection and an approval gate; database, Fabric workspace, notebook, lakehouse, warehouse, or Power BI changes need credential and production-data approval; cloud resources, RBAC, credentials, tokens, and private keys must not be changed or exposed without a separate approval; Microsoft Fabric-specific workflow; do not describe it as a generic data engineering skill.