<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Microsoft on Gavin Warner</title>
    <link>http://localhost:1313/tags/microsoft/</link>
    <description>Recent content in Microsoft on Gavin Warner</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 02 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/microsoft/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint Lists vs Dataverse</title>
      <link>http://localhost:1313/posts/dataverse-vs-sharepoint-lists/</link>
      <pubDate>Sat, 02 May 2026 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/dataverse-vs-sharepoint-lists/</guid>
      <description>&lt;h1 id=&#34;sharepoint-lists-vs-dataverse&#34;&gt;&#xA;  SharePoint Lists vs Dataverse&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#sharepoint-lists-vs-dataverse&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;One of the most common decisions in the Microsoft ecosystem is whether to store your data in &lt;strong&gt;SharePoint Lists&lt;/strong&gt; or in &lt;strong&gt;Dataverse&lt;/strong&gt;. Both can work well, and both are capable of powering useful business solutions. The problem is that they often get treated like they are interchangeable when they really are not.&lt;/p&gt;&#xA;&lt;p&gt;In a lot of projects, the real question is not &amp;ldquo;Which one is better?&amp;rdquo; It is &amp;ldquo;Which one makes the most sense for the size and complexity of what I am building right now?&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Form vs Form</title>
      <link>http://localhost:1313/posts/form-vs-form/</link>
      <pubDate>Sat, 26 Jul 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/posts/form-vs-form/</guid>
      <description>&lt;h1 id=&#34;understanding-the-difference-between-sharepoint-forms-and-microsoft-forms&#34;&gt;&#xA;  Understanding the Difference Between SharePoint Forms and Microsoft Forms&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#understanding-the-difference-between-sharepoint-forms-and-microsoft-forms&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;When it comes to collecting information or input from users in the Microsoft ecosystem, two popular tools often come up, &lt;strong&gt;SharePoint Forms&lt;/strong&gt; and &lt;strong&gt;Microsoft Forms&lt;/strong&gt;. Because both are used to gather responses, they are often confused with one another. In practice, though, they solve very different problems. Here’s a quick breakdown of the key differences to help you choose the right tool for your needs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Building My First Copilot Studio Agent</title>
      <link>http://localhost:1313/projects/copilot-studio-bot/</link>
      <pubDate>Thu, 27 Mar 2025 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/projects/copilot-studio-bot/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;http://localhost:1313/projects/copilot-studio-bot/Images/microsoft-copilot.png&#34;&#xA;    alt=&#34;Copilot logo&#34; width=&#34;320&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h1 id=&#34;building-my-first-copilot-studio-agent&#34;&gt;&#xA;  Building My First Copilot Studio Agent&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#building-my-first-copilot-studio-agent&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;One of the tools I have been spending more time with recently is &lt;strong&gt;Microsoft Copilot Studio&lt;/strong&gt;. After getting hands-on with my first agent, I came away with a much better understanding of where it shines, where it still needs planning, and what I would do differently next time.&lt;/p&gt;&#xA;&lt;p&gt;This project page is a breakdown of that first build from a practical perspective.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
