Data Factory parametrization via external mapping/config tables
Hitting a limits of 256 paramters in Data Factory, or maybe you are tired to parametrizing dozens of pipelines. If yes, this blog entry is for you.
Hitting a limits of 256 paramters in Data Factory, or maybe you are tired to parametrizing dozens of pipelines. If yes, this blog entry is for you.
I’ve been building Logic App workflows for AI agents lately-both autonomous and conversational patterns-and the experience is interesting. This post summarizes what I found from the current documentation and my own experiments.
Over the past decade, Azure Logic Apps has been my go-to for building reliable, scalable integrations without the hassle of custom code. Trust me, it’s transformed how I approach automation; let me share why.
This is the final wrap-up in our Unity Catalog migration series. These are the practical tips we landed on after the migration, the ones that would have saved us time if we had known them before we started.
The most important migration decision was not technical. It was about teams and roles. In Unity Catalog, the wrong role model makes the whole platform hard to operate.
In our platform, one of the first questions we answered was: what is a project in Unity Catalog? That decision shaped every later governance and onboarding choice.
One of the biggest surprises in our Unity Catalog migration was how much of the design depended on product limits. If you do not know which limits are soft and which are fixed, you can build a design that stops before it starts.
The most surprising part of our Databricks migration was this: without previews, we would not have finished. The features we used were not in plain sight, but they were the only path through several blockers.
This was the one part of the migration where the word “catalog” almost hid the real work. We were not just moving metadata; we were rebuilding a platform with Azure Landing Zone thinking and Unity Catalog governance baked in.
We spent the last two and a half years building a new Azure data platform from scratch using the Data Landing Zone approach. After migrating thousands of workloads and managing dozens of subscriptions, I thought it would be useful to share what actually worked, what we did differently, and the honest answer to the question: would I do it again?