<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Power Platform on Kacper Hajdamowicz</title>
    <link>https://kacperhajdamowicz.com/categories/power-platform/</link>
    <description>Recent content in Power Platform on Kacper Hajdamowicz</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 12 Jan 2026 10:00:00 +0200</lastBuildDate>
    <atom:link href="https://kacperhajdamowicz.com/categories/power-platform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Power Apps in 2026: Real Capabilities, Real Limitations, and the Rise of Vibe Coding</title>
      <link>https://kacperhajdamowicz.com/posts/powerapps-capabilities-limitations/</link>
      <pubDate>Mon, 12 Jan 2026 10:00:00 +0200</pubDate>
      <guid>https://kacperhajdamowicz.com/posts/powerapps-capabilities-limitations/</guid>
      <description>&lt;p&gt;Power Apps is one of those tools that generates strong opinions on both sides. Its advocates will tell you it cuts development time by 70%, empowers business users to build their own solutions, and eliminates the need for developers on internal tooling. Its critics will tell you it&amp;rsquo;s slow, inflexible, expensive at scale, and produces apps that look like they were designed in 2011.&lt;/p&gt;&#xA;&lt;p&gt;Both groups are partially right. The honest answer is more nuanced — and in 2026, the landscape has shifted enough that the question &amp;ldquo;should we use Power Apps?&amp;rdquo; deserves a harder look than it used to.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Copilot Studio in Your Organization: AI Agents That Actually Do Work</title>
      <link>https://kacperhajdamowicz.com/posts/copilot-studio-organization/</link>
      <pubDate>Sun, 22 Jun 2025 10:00:00 +0200</pubDate>
      <guid>https://kacperhajdamowicz.com/posts/copilot-studio-organization/</guid>
      <description>&lt;p&gt;Most conversations about AI in the workplace stop at the chatbot stage — a thing you ask questions, get answers from, and then close. &lt;strong&gt;Microsoft Copilot Studio&lt;/strong&gt; is something different. It lets you build agents that don&amp;rsquo;t just answer questions but take actions: generate documents, query databases, trigger workflows, call external APIs, and hand off tasks between specialized sub-agents.&lt;/p&gt;&#xA;&lt;p&gt;In this article I&amp;rsquo;ll walk through what Copilot Studio can actually do inside an organization, with concrete use cases drawn from real implementations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
