dataflows-save-as-authoring-cli

Migrate Gen1 Power BI dataflows to Gen2.1 CI/CD artifacts via az rest.

952|267|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/microsoft/skills-for-fabric --skill dataflows-save-as-authoring-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dataflows-save-as-authoring-cli
Source: https://github.com/microsoft/skills-for-fabric/tree/main/skills/dataflows-save-as-authoring-cli
Command: npx skills add https://github.com/microsoft/skills-for-fabric --skill dataflows-save-as-authoring-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the discovery, readiness assessment, and guarded migration of Gen1 dataflows to Gen2.1 CI/CD copies via CLI, preserving the original dataflows.

Core Features & Use Cases

  • Gen1 → Gen2.1 Save-As via az rest / CLI: create upgraded artifacts while leaving Gen1 intact.
  • 7-signal readiness assessment: evaluate risk signals (incremental refresh, BYOSA storage, external triggers, downstream dependencies, linked entities, DirectQuery, and owner permissions) and produce a markdown + JSON snapshot.
  • Tenant/workspace discovery: scan workspaces or tenants to enumerate Gen1 dataflows and initiate safe upgrades.
  • Guardrails & validation: guard execution, validate post-save-as state, and provide remediation guidance.

Quick Start

Scan a workspace for Gen1 dataflows and perform a guarded Save-As to Gen2.1 using az rest.

Frequently Asked Questions about dataflows-save-as-authoring-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Power BI Gen1 dataflows to Gen2.1 via CLI?

You can migrate Power BI Gen1 dataflows to Gen2.1 by using az rest and REST APIs to perform a guarded save-as operation, which creates upgraded CI/CD artifacts while preserving the original Gen1 dataflows.

What are the readiness risk signals for Power BI dataflow migration?

Readiness assessment evaluates seven risk signals: incremental refresh, BYOSA storage, external triggers, downstream dependencies, linked entities, DirectQuery, and owner permissions to determine migration viability.

Can I scan an entire tenant for Gen1 dataflows before upgrading?

Yes, tenant and workspace discovery scans enumerate Gen1 dataflows across your environment using REST APIs, allowing you to identify candidates and initiate safe upgrades to Gen2.1.

Does the Gen1 to Gen2.1 save-as process modify the original dataflow?

No, the Gen1 to Gen2.1 save-as process creates upgraded CI/CD copies while leaving the original Gen1 dataflows completely intact and untouched in the workspace.

How do I validate a dataflow migration after save-as execution?

Post-save-as validation checks the upgraded artifact state, verifies ownership and idempotency, and provides remediation guidance while outputting a readiness snapshot in markdown and JSON formats.