dataflows-save-as-authoring-cli

To migrate Gen1 dataflows safely, use CLI-based REST API calls to run guarded saveAsNativeArtifact operations after passing a 7-point readiness check for storage, dependency, and permission constraints. This generates CI/CD-compatible Gen2.1 artifacts while preserving original dataflows.

Common Gen1 dataflow migration blockers include BYOSA custom storage configurations, DirectQuery connections, and insufficient permissions. The pre-migration risk assessment also flags warnings like incremental refresh policies and pipeline dependencies before executing the saveAs operation.

Yes, you can scan individual workspaces or an entire tenant to inventory all Gen1 dataflows using Power BI REST and Fabric APIs. This discovery process generates a machine-readable readiness snapshot for audit and CI/CD integration.

Yes, the migration process outputs CI/CD-compatible artifacts and machine-readable readiness snapshots. It executes idempotent saveAsNativeArtifact API calls via CLI, ensuring automated dataflow lifecycle management integrates seamlessly with existing pipelines.

If a dataflow fails the pre-migration risk assessment, the guarded execution prevents the saveAsNativeArtifact operation from running. This ensures only compatible dataflows are migrated to Gen2.1, avoiding broken dependencies or data loss.

No, original Gen1 dataflows are preserved during migration. The CLI-based guarded execution creates Gen2.1 copies using the saveAsNativeArtifact operation, ensuring your legacy dataflows remain intact in case of rollback or audit requirements.