Where Curiosity Meets Practice

Notes from real projects. What worked, what didn't, and why — no marketing spin.

Featured

Featured

Copilot Managed Runtime: The Runtime Becomes the Governance Boundary

Microsoft now hosts the code that Copilot and other AI tools build. For architects, that moves governance from the build tool to the runtime. Here is what that changes, what it does not solve, and what to design before the first AI-built app goes viral.

Agents With Their Own Accounts: What Changes When Copilot Studio Agents Stop Borrowing Your Identity

Microsoft's October 15, 2026 announcement gives Copilot Studio agents their own accounts, shared business process memory, and triggers. I argue that organizations should treat each agent like a service account with a job description and decide early which agents they want to own.

Agent FinOps in the Microsoft Ecosystem - Rev1

Part two of a short, living series on Copilot and agent costs. Where Microsoft 365 Copilot services, Copilot Studio, and Foundry agents show their costs, which controls stop spending, and how to build chargeback across three admin experiences.

Understanding Microsoft Copilot Licensing - Rev1

Part one of a short, but living series on what Copilot and agents cost. What the Copilot license costs, how Copilot Credits work, which features use them, and what Microsoft has announced next.

Understanding Microsoft Power Platform Licensing Rev.6

A practitioner's reference for Power Platform core, Copilot Studio, Dataverse, Dynamics 365 Contact Center, and Dynamics 365 Customer Service.

Copilot Managed Runtime: The Runtime Becomes the Governance Boundary

Microsoft now hosts the code that Copilot and other AI tools build. For architects, that moves governance from the build tool to the runtime. Here is what that changes, what it does not solve, and what to design before the first AI-built app goes viral.

Agents With Their Own Accounts: What Changes When Copilot Studio Agents Stop Borrowing Your Identity

Microsoft's October 15, 2026 announcement gives Copilot Studio agents their own accounts, shared business process memory, and triggers. I argue that organizations should treat each agent like a service account with a job description and decide early which agents they want to own.

Agent FinOps in the Microsoft Ecosystem - Rev1

Part two of a short, living series on Copilot and agent costs. Where Microsoft 365 Copilot services, Copilot Studio, and Foundry agents show their costs, which controls stop spending, and how to build chargeback across three admin experiences.

Understanding Microsoft Copilot Licensing - Rev1

Part one of a short, but living series on what Copilot and agents cost. What the Copilot license costs, how Copilot Credits work, which features use them, and what Microsoft has announced next.

Understanding Microsoft Power Platform Licensing Rev.6

A practitioner's reference for Power Platform core, Copilot Studio, Dataverse, Dynamics 365 Contact Center, and Dynamics 365 Customer Service.

Prompt Libraries Are Reusable Text - Skills Are Reusable Expertise

Custom skills replace the prompt library as the way organizations package know-how in Microsoft 365 Copilot. Here is what a skill actually is, why it beats a prompt, and why Agent Builder is enough for most of them - no Copilot Studio required.

Hello, I’m Holger

I connect enterprise AI architecture with practical implementation, and share what I learn along the way.

I’m a Principal Architect at NTT DATA, Microsoft MVP and Microsoft Certified Trainer (MCT), based in Berlin. My work focuses on agentic AI, intelligent automation, and the Microsoft ecosystem. I help organizations move from promising demonstrations to secure, scalable, well-governed solutions. That means connecting technology choices with business processes, enterprise data, operational ownership, and measurable outcomes.

About me