dataflows-consumption-cli

Use az rest with a GET request to the /v1/workspaces/{workspaceId}/dataflows endpoint, passing --resource "https://api.fabric.microsoft.com" for the correct token audience. Filter results client-side with JMESPath since there is no server-side name filter.

Call the getDefinition endpoint with a POST request (not GET), then base64-decode the mashup.pq part from the response. Large definitions may return 202 with a Location header, so poll the operation URL until it completes.

No. The skill is strictly read-only and refuses any create, update, or delete operation, including updateDefinition and Delete Dataflow calls. For authoring or persisting changes, use the dataflows-authoring-cli skill instead.

The executeQuery endpoint returns 200 with an Arrow stream even when the underlying source query fails, embedding the error JSON inside the stream's PQ Arrow Metadata. Always grep the saved Arrow file for an "Error" marker before parsing it with pyarrow.

A 401 usually means the token audience is wrong or the session expired. Run az login again and always pass --resource "https://api.fabric.microsoft.com" to az rest so the token is issued for the Fabric API.

The getDefinition operation requires Contributor role or higher (Read+Write) on the workspace; a Viewer role returns 403 Forbidden. Listing dataflows and reading job history work with lower-privilege read access.