In the previous post, I built a Power Automate flow that uploads a document into a Databricks volume. It works. But it runs on my personal access token, and I called that a shortcut right away. Time to fix that with a Databricks service principal in Power Automate. Why does that matter? The token belongs to my user account. It expires. And if my access changes, the flow breaks. That’s fine for a demo. However, it’s not fine for a…
In the previous post, I signed up for Databricks Free Edition and built a catalog, a schema, and a volume named dropzone. That volume is empty, though. Now it’s time to upload files to Databricks, and that’s where my two hats (Data Platform Architect and Power Apps MVP) actually have to talk to each other. My plan was simple: trigger a Power Automate flow from Dataverse, and have it upload a document straight into that volume. So I opened a…
I wear two hats. My profession is Data Platform Architect, where Databricks, Delta tables, and Unity Catalog are just another Tuesday. My hobby – if you can call it that – is being a Microsoft MVP for Power Apps, living inside Dataverse, Power Automate, and low-code. It is how it is. These two worlds rarely meet. This post is where I make them. If you’ve followed my spec-driven development series, you know I already extract receipts and invoices using Azure…