<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Low Code Builder</title><link>https://thelowcodebuilder.com/tags/power-platform/</link><description>Power Platform Tips Tutorials and Insights</description><language>en-us</language><item><title>Enhanced Data Models and Bootstrap 5 Transform Power Pages Portals</title><link>https://thelowcodebuilder.com/posts/2026-06-03-enhanced-data-models-and-bootstrap-5-transform-power-pages-portals/</link><pubDate>Wed, 03 Jun 2026 12:48:09 +0000</pubDate><description>&lt;h2 id="faster-smarter-portals-whats-new-in-power-pages"&gt;Faster, Smarter Portals: What&amp;rsquo;s New in Power Pages&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;ve ever struggled with slow portal development or clunky UIs that break on mobile, you&amp;rsquo;re not alone. Dynamics 365 Portals have long been a cornerstone of customer self-service, but their limitations in data modeling and front-end flexibility often forced developers into custom coding traps. Microsoft has just changed that with two major updates: the &lt;strong&gt;Enhanced Data Model&lt;/strong&gt; and &lt;strong&gt;Bootstrap 5 integration&lt;/strong&gt; for Power Pages. Let&amp;rsquo;s explore how these changes are reshaping portal development.&lt;/p&gt;</description></item><item><title>Microsoft Copilot Studio &amp; MCP: Revolutionizing Agent Integration</title><link>https://thelowcodebuilder.com/posts/2026-05-30-microsoft-copilot-studio-mcp-revolutionizing-agent-integration/</link><pubDate>Sat, 30 May 2026 05:53:55 +0000</pubDate><description>&lt;h2 id="the-problem-fragmented-integration-in-agent-workflows"&gt;The Problem: Fragmented Integration in Agent Workflows&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;ve ever tried to connect a chatbot to a CRM system or an IoT sensor, you know the headache of juggling disparate APIs, security protocols, and data formats. Traditional agent workflows often require custom code for every integration, leading to delays, security gaps, and rising costs. This is where &lt;strong&gt;Microsoft Copilot Studio&lt;/strong&gt; and its new &lt;strong&gt;MCP (Microsoft Copilot Protocol)&lt;/strong&gt; come in — transforming how agents interact with external systems.&lt;/p&gt;</description></item><item><title>How Microsoft Copilot Studio and MCP Transform AI Integration</title><link>https://thelowcodebuilder.com/posts/2026-05-29-how-microsoft-copilot-studio-and-mcp-transform-ai-integration/</link><pubDate>Fri, 29 May 2026 06:11:34 +0000</pubDate><description>&lt;h2 id="the-problem-fragmented-ai-integration"&gt;The Problem: Fragmented AI Integration&lt;/h2&gt;
&lt;p&gt;If you&amp;rsquo;ve ever tried to connect an AI agent to a legacy system or enterprise tool, you know the frustration. Each integration feels like starting from scratch—custom coding, security hurdles, and endless API configuration. This is where &lt;strong&gt;Microsoft Copilot Studio&lt;/strong&gt; and the &lt;strong&gt;Model Context Protocol (MCP)&lt;/strong&gt; step in. Together, they redefine how AI agents interact with the world, turning complex integrations into streamlined workflows.&lt;/p&gt;
&lt;h2 id="what-is-model-context-protocol-mcp"&gt;What is Model Context Protocol (MCP)?&lt;/h2&gt;
&lt;p&gt;MCP is Microsoft&amp;rsquo;s answer to the chaos of AI integration. At its core, it&amp;rsquo;s a &lt;strong&gt;standardized framework&lt;/strong&gt; that lets AI agents communicate with external systems via &lt;strong&gt;RESTful APIs, gRPC, or custom protocols&lt;/strong&gt;. Think of it as a universal translator for AI: it exposes tools and data through predefined endpoints, which &lt;strong&gt;Copilot Studio agents&lt;/strong&gt; consume using the platform&amp;rsquo;s built-in connector infrastructure.&lt;/p&gt;</description></item></channel></rss>