Browsed by
Category: Power Platform

Getting Started with Databricks Free Edition

Getting Started with Databricks Free Edition

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…

Read More Read More

Baltic Summit 2026 was all about AI & Power Platform

Baltic Summit 2026 was all about AI & Power Platform

Baltic Summit 2026 just wrapped up in Gdynia, Poland, and I’m still working through my notes. Three days, a packed agenda, and honestly one of the best-organized conferences I’ve attended in a while. Registration was smooth, and the tracks were easy to follow. By the end, the whole event felt well thought out from start to finish. The overall theme across sessions was clear: AI, Copilot, Power Platform solutions, governance, and security. All of it was viewed from a dozen…

Read More Read More

Never Pay for the Same Dataverse Mistake Twice

Never Pay for the Same Dataverse Mistake Twice

GitHub Copilot showed me something new: GPT-5.6 Sol, plus a 30% discount. Yes, and I couldn’t resist trying it on a Dataverse task. Why not see the new model in action, right? As a result, that decision burned nearly a month’s budget before the task was even done. But here’s the thing: the expensive part isn’t the story worth telling. What came out of it was a GitHub Copilot custom skill – a reusable file that captures everything the agent…

Read More Read More

M365 Con DACH 2026 Recording Is Live

M365 Con DACH 2026 Recording Is Live

Missed my session at M365 Con DACH 2026? Good news – the recording is live. One note before you press play: it’s in German. On paper, my session covers Power Platform and document processing with AI Foundry Content Understanding. That’s the abstract I submitted. Reality had other plans. Shortly before the talk, my demo environment fell apart, and I had to rebuild it fast. So I turned to GitHub Copilot. It rebuilt the Dataverse tables, flows, and the Content Understanding…

Read More Read More

One Task Table to Rule Them All

One Task Table to Rule Them All

The backlog from my last post had one line I couldn’t ignore: status transitions weren’t implemented yet. Tables, views, the model-driven app – all done. The missing piece was the Dataverse Agent Task contract itself. In other words, the part that lets Power Platform and Azure talk to each other. That wasn’t a bug. It was a missing seam. Without an explicit contract, two teams can’t build independently. They can’t test independently either. Remember my post about project decomposition? I…

Read More Read More

GitHub Copilot Dataverse: MCP Limits, YAML, and PAC CLI

GitHub Copilot Dataverse: MCP Limits, YAML, and PAC CLI

My spec was done. The plan too. Time to build the Dataverse foundation: the piece everything in my Expense Management system would run on. I connected the Dataverse MCP server in VS Code, opened my prepared spec, and ran /speckit.implement in GitHub Copilot. The GitHub 🌱 SpecKit workflow with Copilot to implement my Dataverse solution felt ready. I expected it to just work. It didn’t. The MCP hit its limits fast. Cryptic errors, wrong solution placement, no model-driven app support….

Read More Read More

Spec-Driven Development: Project Decomposition

Spec-Driven Development: Project Decomposition

The Dataverse-first restart was done. However, my spec looked sharper. The data model had a center of gravity, and that part actually worked. Solving one problem, however, revealed another. One spec was still covering six very different concerns: different timelines, different risk profiles, and different people who would eventually build and own each piece. Nothing defined where one concern ended and another began. That’s not a spec problem. Instead, it’s a structure problem. In my previous post, I said the…

Read More Read More

Spec-Driven Development: When the Spec Is Too Big

Spec-Driven Development: When the Spec Is Too Big

I had a spec, I had GitHub Copilot Pro+! A new billing period with fresh credits has begun. So I started to refurbish my Expense Management system. In detail, I was building with a fresh spec that should rebuild the whole system in one run. And yes, that was the problem. Everything looked good. Copilot credits were melting away during implementation. Some hours later I had my first results. The Azure portal showed me what was there. Content Understanding analyzers:…

Read More Read More

Stop Coding. Start Building from Specs.

Stop Coding. Start Building from Specs.

I haven’t written a line of code since January. Not because I couldn’t. I stopped because spec-driven development showed me I was spending time on the wrong part of the job. Today, it is easy to type “build me XYZ” and get code in seconds. I did that too. Sometimes the result looked great. Then I ran the same prompt again and got something different. Logic shifted. Edge cases disappeared. The output stopped being predictable. The turning point came when…

Read More Read More

Copilot Studio Child Agents: ServiceNow Incident Pipeline

Copilot Studio Child Agents: ServiceNow Incident Pipeline

“The dangerous part starts when people try to build one agent for everything. Then you don’t have automation anymore – you have a very polite chaos machine.” Fellow MVP and friend Marcel Lehmann commented that on my last post. And yes – he was describing exactly what I had built at first. Until I started to split my agents and recombine them again with a new feature. This is the final part of my Teams ITSM Copilot series. You’ve seen…

Read More Read More