<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deployment on Alexander Arvidsson</title>
    <link>/tags/deployment/</link>
    <description>Recent content in Deployment on Alexander Arvidsson</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/deployment/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Microsoft Fabric Deployment Options: Choose What Your Team Can Own</title>
      <link>/posts/fabric-deployment-1/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/fabric-deployment-1/</guid>
      <description>There is more than one way to deploy in Microsoft Fabric, from editing directly in a workspace to fully automated environments. Each step up adds control, and each step adds something your team must understand when a release fails. I walk through the options, from deployment pipelines to FabricOps, and share where I usually start. The best choice is not the most powerful one. It is the one your team can still run after the consultant leaves.</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="/posts/fabric-deployment-1/cover.jpg" />
    </item>
    
  </channel>
</rss>
