Browsed by
Category: Azure

One Task Table to Rule Them All
One Task Table to Rule Them All

One Task Table to Rule Them All

Comments 0 Comment

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

My Son Built an App with No IT Background
My Son Built an App with No IT Background

My Son Built an App with No IT Background

“Dad, can we build an app with AI?” That question started a spec-driven development experiment I’ll never forget. He was seventeen. No coding background, no CS classes. Just frustration with the school carpool situation: thirty parents in a WhatsApp thread, nobody knowing who was driving, every morning a small disaster. I said yes. But on one condition: we use GitHub 🌱 SpecKit. He looked puzzled. Fair enough. So I explained: it’s a framework for Spec-Driven Development. Describe the problem the…

Read More Read More

Spec-Driven Development: Project Decomposition
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

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

Spec-Driven Development: The Methodology Behind the Magic
Spec-Driven Development: The Methodology Behind the Magic

Spec-Driven Development: The Methodology Behind the Magic

Most developers I know have been here. They type a detailed prompt into their AI agent. The output looks right. They run it, tweak a detail, run it again – and somewhere around the third attempt, the whole thing has quietly shifted into something else. The problem is not the AI. The problem is the approach. Spec-driven development changes that. Before a single file gets created, you define intent. You build a shared understanding for your business stakeholders, your architect,…

Read More Read More

Stop Coding. Start Building from Specs.
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

Teams ServiceNow Integration with Copilot Studio Agents

Teams ServiceNow Integration with Copilot Studio Agents

Who doesn’t know such calls for help? “Can someone help me with Databricks? I can’t access my S3 bucket. Getting permission denied errors.” Just another Teams message. Another problem solved in minutes through quick collaboration. No ticket created. Then came the memo. Management wanted to shut down all support channels. Force everyone to use ServiceNow, our ITSM (IT Service Management) platform for tracking IT incidents and requests. Make compliance mandatory through restriction. I knew this would backfire. From my perspective, banning Teams…

Read More Read More

Hey Code, Specify!

Hey Code, Specify!

I was deep into spec-driven development with GitHub’s Spec Kit. Writing detailed specifications. Describing what I wanted AI agents to build. And I was typing. A lot. My fingers became the bottleneck. Then I thought: why am I typing when I could be talking? I opened Copilot Chat and looked for a microphone. Nothing. Turns out there’s a small extension you need: “VS Code Speech for Copilot.” I installed it and the microphone appeared. But then I discovered something better. The…

Read More Read More

Extracting Unified Workflow Metadata

Extracting Unified Workflow Metadata

Recently I stumbled upon a question that kept nagging me: How can I get unified workflow metadata? This came up while I was working on my demo for the blog post Lightweight Workflow Monitoring. In that demo, I reused my Try-Catch-Finally pattern originally developed for Power Automate Flows. I applied this pattern to an Azure Logic App. So far, so good. But then I hit an unexpected twist. In Power Automate, I rely heavily on the workflow() expression to access…

Read More Read More

Building an AI Agent That Generates Test Data

Building an AI Agent That Generates Test Data

Recently, I was creating an agent with the goal to identify potential incidents in Teams community of practice channels. I started building this agent to find problems such as “I need help” and create ServiceNow incidents from its information. Testing it meant feeding realistic support cases into the system. But here’s the problem: real support data contains sensitive information. Project names. Client issues. Internal struggles. You can’t demo that publicly. You can’t even use it safely in testing. This isn’t…

Read More Read More