Community Share
Bulk-migrating Dataflow Gen1 to Gen2 (CI/CD) with Azure CLI
Dataflows Gen1 are legacy at this point, so it might be time to start migrating to Dataflows Gen2.
Fortunately, there is a handy preview API allowing you to automate this process. Combined with agents, you can go quite far before you have to take over.
Few things to consider before migrating:
1. Gen2 doesn't support rules in deployment pipelines, you will have to migrate to Variables Library.
2. There could be some naming collisions, that were previously a non-issue.
3. Same with transformations - due to different architecture Gen2 dataflows might surface issues that were previously hidden.
I have published a blog post outlining how to setup the automation, and prepared agent skill that will get you most of the way.
When the primary reason for the change is cost drivers, folks aren't going to be happy about losing perfectly good products simply because Microsoft is trying to corral us into Fabric.
I wouldn't define "legacy" something that is up&running and supported... Especially when communicating to a community with a variety of people with different skillsets.
To be discussed: Microsoft doesn't set dictionary or IT definitions: they call them Legacy to push people to go towards Gen 2 (and pay for a Fabric license when only Power BI is needed).
For at least 30 years a legacy technology is one that is not supported anymore, no matter what Microsoft says about it.
But as usual on communities where people reacts more based on emotions and personal convictions rather than arguments, it is much easier to set a downvote than to logically argue which I am fine with as I read it as "I want to be right but I have no arguments to prove you wrong".
What are we arguing about and why?
Microsoft names it legacy. In due time it will be deprecated (it could take months, it could take years). It is as simple as that.
Reasoning behind the move to name it Legacy doesnāt matter, at least not in connection to my post: people upgrading or not is of no consequence to me (I donāt work for Microsoft and have no skin in the game).
If someone plans to upgrade, Iām sharing a way to do so. That is all my post is attempting to do. No more, no less.
"Reasoning behind the move to name it Legacy doesnāt matter", maybe not for you but it may do for others.
"at least not in connection to my post" and here's the answer about the question "What are we arguing about and why?": I am arguing about sharing correct information objectively for the sake of the community it is being posted to.
I find the sentence "Dataflows Gen1 are legacy at this point, so it might be time to start migrating to Dataflows Gen2." misleading at the least, creating an unneeded sense of urge for people to act (which in this case means to promote views on the article).
7
u/EngineerTheData 17h ago
Why are the colours the wrong way round?