<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Adam</title>
    <description>The latest articles on DEV Community by Adam (@adammarczak).</description>
    <link>https://dev.to/adammarczak</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3990993%2F2e97703c-b7bb-4d20-91df-06d1c81185c4.jpg</url>
      <title>DEV Community: Adam</title>
      <link>https://dev.to/adammarczak</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/adammarczak"/>
    <language>en</language>
    <item>
      <title>Creating Microsoft Fabric Sandbox Capacities Chatbot using Azure Logic Apps</title>
      <dc:creator>Adam</dc:creator>
      <pubDate>Tue, 07 Jul 2026 07:43:41 +0000</pubDate>
      <link>https://dev.to/adammarczak/creating-microsoft-fabric-sandbox-capacities-chatbot-using-azure-logic-apps-4n7n</link>
      <guid>https://dev.to/adammarczak/creating-microsoft-fabric-sandbox-capacities-chatbot-using-azure-logic-apps-4n7n</guid>
      <description>&lt;p&gt;In every company I've worked at, I've always set up Azure Sandbox environments. The goal is simple. To provide a way for employees to learn and test Azure solutions, through an easy to use interface like Microsoft Teams. &lt;/p&gt;

&lt;p&gt;To make this easy on myself, I've always leveraged architecture based on Azure Logic Apps. In my opinion low-code fits perfectly for such scenario. It lets me get everything up and running in half a day, and benefiting from it almost immediately. &lt;/p&gt;

&lt;p&gt;In this post I go over this architectural pattern, with an example of Logic App that does exactly that. I explain pros and cons, multi-tenant setup, and enterprise features you might want to add as the adoption grows. &lt;/p&gt;

&lt;p&gt;If this sounds interesting, here is my post about it: &lt;a href="https://lnkd.in/d9pwV_vE" rel="noopener noreferrer"&gt;https://lnkd.in/d9pwV_vE&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Enjoy!&lt;/p&gt;

</description>
      <category>azure</category>
      <category>fabric</category>
      <category>logicapps</category>
    </item>
    <item>
      <title>Creating Azure Sandbox Chatbot with Azure Logic Apps</title>
      <dc:creator>Adam</dc:creator>
      <pubDate>Wed, 01 Jul 2026 07:58:00 +0000</pubDate>
      <link>https://dev.to/adammarczak/creating-azure-sandbox-chatbot-with-azure-logic-apps-56kj</link>
      <guid>https://dev.to/adammarczak/creating-azure-sandbox-chatbot-with-azure-logic-apps-56kj</guid>
      <description>&lt;p&gt;In every company I've worked at, I've always set up Azure Sandbox environments. The goal is simple. To provide a way for employees to learn and test Azure solutions, through an easy to use interface like Microsoft Teams. &lt;/p&gt;

&lt;p&gt;To make this easy on myself, I've always leveraged architecture based on Azure Logic Apps. In my opinion low-code fits perfectly for such scenario. It lets me get everything up and running in half a day, and benefiting from it almost immediately. &lt;/p&gt;

&lt;p&gt;In this post I go over this architectural pattern, with an example of Logic App that does exactly that. I explain pros and cons, multi-tenant setup, and enterprise features you might want to add as the adoption grows. &lt;/p&gt;

&lt;p&gt;If this sounds interesting, here is my post about it: &lt;a href="https://marczak.io/posts/2026/07/azure-sandbox-chatbot-with-azure-logic-apps/" rel="noopener noreferrer"&gt;https://marczak.io/posts/2026/07/azure-sandbox-chatbot-with-azure-logic-apps/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Enjoy!&lt;/p&gt;

</description>
      <category>azure</category>
      <category>logicapps</category>
      <category>mvp</category>
    </item>
    <item>
      <title>The evolution of Azure Data Platforms, and the future with Databricks- and Fabric-centric architectures</title>
      <dc:creator>Adam</dc:creator>
      <pubDate>Tue, 23 Jun 2026 07:52:30 +0000</pubDate>
      <link>https://dev.to/adammarczak/the-evolution-of-azure-data-platforms-and-the-future-with-databricks-and-fabric-centric-2ei</link>
      <guid>https://dev.to/adammarczak/the-evolution-of-azure-data-platforms-and-the-future-with-databricks-and-fabric-centric-2ei</guid>
      <description>&lt;p&gt;I'd like to share my thoughts on the evolution of Azure Data Platforms and the what future platform design could look like with Fabric and Databricks-centric architectures. &lt;/p&gt;

&lt;p&gt;Hope you will like it 😊&lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://marczak.io/posts/2026/06/evolution-of-azure-data-platforms/" rel="noopener noreferrer"&gt;https://marczak.io/posts/2026/06/evolution-of-azure-data-platforms/&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Databricks #MicrosoftFabric #Azure #MVPBuzz
&lt;/h1&gt;

</description>
    </item>
    <item>
      <title>Azure/Fabric Data Factory pipeline parametrization via external mapping/config tables</title>
      <dc:creator>Adam</dc:creator>
      <pubDate>Thu, 18 Jun 2026 13:33:56 +0000</pubDate>
      <link>https://dev.to/adammarczak/azurefabric-data-factory-pipeline-parametrization-via-external-mappingconfig-tables-2ph2</link>
      <guid>https://dev.to/adammarczak/azurefabric-data-factory-pipeline-parametrization-via-external-mappingconfig-tables-2ph2</guid>
      <description>&lt;p&gt;Hey all!&lt;/p&gt;

&lt;p&gt;Recently I've had an urge to start sharing again, so I wrote a short blog post about a simple and repeatable pattern of data factory pipeline parametrization via external config tables. One of my favourite ways to manage parameters at scale in my data factories estates. &lt;/p&gt;

&lt;p&gt;Link: &lt;a href="https://marczak.io/posts/2026/06/data-factory-parametrization-with-config-tables/" rel="noopener noreferrer"&gt;https://marczak.io/posts/2026/06/data-factory-parametrization-with-config-tables/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Hope you will like it. 😊&lt;/p&gt;

</description>
      <category>azure</category>
      <category>fabric</category>
    </item>
  </channel>
</rss>
