skills.rest
weiflycc-cmd
weiflycc-cmdCOMMUNITY
Explore all skills by this author →
GitHub

dataflows-save-as-authoring-cli

Migrate Power BI Gen1 dataflows to Fabric Gen2.1 with guarded save-as operations.

Updated Jun 1, 2026
Search Tags:#fabric cli#dataflow migration#gen1 to gen2#save-as assessment#power bi rest api#dataflow risk signals#cicd dataflows
One-click install
npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill dataflows-save-as-authoring-cli-weiflycc-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dataflows-save-as-authoring-cli
Source: https://github.com/weiflycc-cmd/skills-for-fabric/tree/main/plugins/fabric-authoring/skills/dataflows-save-as-authoring-cli
Command: npx skills add https://github.com/weiflycc-cmd/skills-for-fabric --skill dataflows-save-as-authoring-cli-weiflycc-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migrating Power BI Gen1 dataflows to Fabric Gen2.1 carries significant risk of breaking downstream workloads, storage configurations, and refresh schedules without prior assessment of migration blockers like BYOSA storage, DirectQuery connections, or upstream dependencies. This Skill eliminates guesswork by providing a structured, guarded workflow for safe dataflow migration.

Core Features & Use Cases

  • Gen1 Dataflow Discovery: Scan individual workspaces or entire tenants to inventory all Gen1 dataflows using Power BI REST APIs.
  • 7-Point Risk Assessment: Evaluate each Gen1 dataflow for migration blockers (BYOSA storage, DirectQuery, insufficient permissions) and warnings (incremental refresh, pipeline dependencies, linked entities, external triggers) to classify readiness as Safe, Manual followups, or Blocked.
  • Guarded Save-As Execution: Run the saveAsNativeArtifact API with built-in guardrails for idempotency, permission validation, and Windows CLI compatibility to create Gen2.1 copies without disrupting original Gen1 dataflows.
  • Post-Migration Validation: Verify new artifact integrity and generate markdown/JSON readiness snapshots for CI/CD integration.
  • Use Case: A data engineer managing a Fabric tenant with 100+ Gen1 dataflows can use this Skill to automatically flag 20% of dataflows with BYOSA storage as blocked, safely save the remaining eligible dataflows, and produce a readiness report for stakeholder review.

Quick Start

Use the dataflows-save-as-authoring-cli skill to scan your Fabric workspace for Gen1 dataflows, assess their save-as readiness, and create Gen2.1 copies via Azure CLI.

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 safely migrate Power BI Gen1 dataflows to Fabric Gen2.1?▼

To safely migrate Gen1 dataflows to Fabric Gen2.1, you need a guarded workflow that first identifies migration blockers like BYOSA storage and DirectQuery, then executes save-as operations via Azure CLI and Power BI REST APIs to create copies without disrupting originals.

What are the blockers for Power BI dataflow migration to Gen2?▼

Common Power BI dataflow migration blockers include BYOSA storage configurations, DirectQuery connections, and insufficient permissions. A 7-point risk assessment evaluates these blockers alongside warnings like incremental refresh and linked entities to classify readiness as Safe, Manual, or Blocked.

How do I assess dataflow save-as readiness across a Fabric tenant?▼

You can assess dataflow save-as readiness across a Fabric tenant by using Power BI REST APIs to inventory all Gen1 dataflows, then running a 7-point risk signal check to generate markdown and JSON readiness snapshots classifying each dataflow's migration eligibility.

Can I automate Gen2.1 dataflow copy creation using Azure CLI?▼

Yes, you can automate Gen2.1 dataflow copy creation using Azure CLI by calling the saveAsNativeArtifact API with built-in guardrails for idempotency and permission validation, ensuring Windows CLI compatibility while safely creating Gen2.1 copies of eligible Gen1 dataflows.

What happens to downstream workloads during Gen1 dataflow migration?▼

Without prior assessment, Gen1 dataflow migration risks breaking downstream workloads, storage configurations, and refresh schedules. A guarded save-as workflow prevents this by validating post-save-as artifact integrity and flagging upstream dependencies before executing any migration.

Does the dataflow save-as process support CI/CD integration?▼

Yes, the dataflow save-as process supports CI/CD integration by generating markdown and JSON readiness snapshots that document migration risks and post-migration validation results, enabling automated pipelines to consume the artifact integrity checks for stakeholder review.

Related Skills

Explore More Data & Analytics Skills→
rritecrritec
3

dataflows-save-as-authoring-cli

Assess Gen1 dataflow readiness and create Gen2.1 copies via Power BI and Fabric REST APIs.

Community
Advanced
microsoftmicrosoft
952

dataflows-save-as-authoring-cli

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

Official
Advanced
pingqLINpingqLIN

power-bi-devops-alm-best-practices

Automate Power BI CI/CD pipelines with Azure DevOps and Fabric REST API.

Community
Advanced
patrikboroschpatrikborosch
14

dataflows-save-as-authoring-cli

Migrate Power BI Gen1 dataflows to Gen2.1 via CLI-based REST API calls.

Community
Advanced