<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rene Fürstenberg &#8211; World of Azure Cloud</title>
	<atom:link href="https://renefuerstenberg.de/author/admin/feed/" rel="self" type="application/rss+xml" />
	<link>https://renefuerstenberg.de</link>
	<description></description>
	<lastBuildDate>Sat, 16 May 2026 08:29:40 +0000</lastBuildDate>
	<language>de</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>

<image>
	<url>https://renefuerstenberg.de/wp-content/uploads/2024/01/cropped-logo_neu-32x32.png</url>
	<title>Rene Fürstenberg &#8211; World of Azure Cloud</title>
	<link>https://renefuerstenberg.de</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Save Costs in Microsoft Fabric by Automating Capacity Start &#038; Stop with Azure Logic Apps</title>
		<link>https://renefuerstenberg.de/microsoftfabric/how-to-save-costs-in-microsoft-fabric-by-automating-capacity-start-stop-with-azure-logic-apps/</link>
		
		<dc:creator><![CDATA[Rene Fürstenberg]]></dc:creator>
		<pubDate>Sat, 16 May 2026 07:15:55 +0000</pubDate>
				<category><![CDATA[Microsoft Fabric]]></category>
		<guid isPermaLink="false">https://renefuerstenberg.de/?p=1630</guid>

					<description><![CDATA[Introduction I get asked quite often how to save costs efficiently in Microsoft Fabric. One of the biggest levers is pausing your Fabric capacity when it’s not in use. What’s important to understand here: storage costs continue, even when the capacity is stopped. You’re only saving on compute. That’s still a huge win, especially if [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1630" class="elementor elementor-1630">
				<div class="elementor-element elementor-element-12150eb e-flex e-con-boxed e-con e-parent" data-id="12150eb" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-818142b elementor-widget elementor-widget-heading" data-id="818142b" data-element_type="widget" data-e-type="widget" data-widget_type="heading.default">
				<div class="elementor-widget-container">
					<h2 class="elementor-heading-title elementor-size-default">Introduction</h2>				</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-6fad98e e-flex e-con-boxed e-con e-parent" data-id="6fad98e" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-34aa6d9 elementor-widget elementor-widget-text-editor" data-id="34aa6d9" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p>I get asked quite often how to save costs efficiently in Microsoft Fabric. One of the biggest levers is pausing your Fabric capacity when it’s not in use.</p><div><p>What’s important to understand here: storage costs continue, even when the capacity is stopped. You’re only saving on compute. That’s still a huge win, especially if your workloads are not running 24/7.</p><p>In this article, I’ll walk through what this can look like in practice and how you can set up a proper solution to stop and start your capacity.</p><p>Let’s quickly look at the available options:</p><ul><li>Manually start and stop the capacity</li><li>Automatically start and stop using a Logic App</li><li>Automatically start and stop using Azure Automation</li><li>With Semantic Link Labs</li></ul><p>Technically, all of these work. But let’s be honest, manually starting and stopping your capacity every day isn’t something anyone wants to deal with in the long run.</p><p>That’s why automation is the only approach that really makes sense.</p><p>In my case, I decided to go with <strong>Azure Logic Apps</strong>, and I’ll show you how to set this up step by step. It’s lightweight, reliable, and easy to maintain, exactly what you want for something that should just run in the background without any manual effort.</p><p>Let’s get into it.</p></div>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-da524b4 e-flex e-con-boxed e-con e-parent" data-id="da524b4" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-ea34132 elementor-widget elementor-widget-read-more" data-id="ea34132" data-element_type="widget" data-e-type="widget" data-widget_type="read-more.default">
				<div class="elementor-widget-container">
					</div></div></div></div></div> <a href="https://renefuerstenberg.de/microsoftfabric/how-to-save-costs-in-microsoft-fabric-by-automating-capacity-start-stop-with-azure-logic-apps/#more-1630" class="more-link elementor-more-link">Weiterlesen</a>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Materialized Lake Views in Microsoft Fabric</title>
		<link>https://renefuerstenberg.de/microsoftfabric/materialized-lake-views-in-microsoft-fabric/</link>
		
		<dc:creator><![CDATA[Rene Fürstenberg]]></dc:creator>
		<pubDate>Thu, 16 Apr 2026 15:24:05 +0000</pubDate>
				<category><![CDATA[Microsoft Fabric]]></category>
		<guid isPermaLink="false">https://renefuerstenberg.de/?p=1468</guid>

					<description><![CDATA[Introduction In this article, i want to focus specifically on Materialized Lake Views (MLVs in order to better understand how they work and where they can be applied. MLVs are still relatively new in Microsoft Fabric and, at first glance, do not fully align with what Microsoft has strongly promoted so far, namely a strict [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1468" class="elementor elementor-1468">
				<div class="elementor-element elementor-element-89b9422 e-flex e-con-boxed e-con e-parent" data-id="89b9422" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-2fcaca9 elementor-widget elementor-widget-text-editor" data-id="2fcaca9" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<h5><span style="text-decoration: underline;"><span style="font-size: 1.5em;">Introduction</span></span></h5><div><p>In this article, i want to focus specifically on Materialized Lake Views (MLVs in order to better understand how they work and where they can be applied.</p><p>MLVs are still relatively new in Microsoft Fabric and, at first glance, do not fully align with what Microsoft has strongly promoted so far, namely a strict separation of the individual layers. Nevertheless, they represent a very interesting alternative, especially when it comes to reducing complex ETL processes.</p><p>In my projects, I generally follow the Medallion architecture, where I use a separate Lakehouse for each of the Bronze, Silver, and Gold layers. Alternatively, the Gold layer can also be implemented as a Fabric Warehouse.</p><p>This is exactly where Materialized Lake Views come into play, as they enable a different approach:</p><p>Instead of operating multiple Lakehouses for the individual layers, Bronze, Silver, and Gold can be represented via separate schemas within a single Lakehouse. The individual layers are logically separated while being technically created within the same Lakehouse.</p></div>								</div>
				</div>
					</div>
				</div>
		<div class="elementor-element elementor-element-d87d9f2 e-flex e-con-boxed e-con e-parent" data-id="d87d9f2" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-b8070df elementor-widget elementor-widget-read-more" data-id="b8070df" data-element_type="widget" data-e-type="widget" data-widget_type="read-more.default">
				<div class="elementor-widget-container">
					</div></div></div></div></div> <a href="https://renefuerstenberg.de/microsoftfabric/materialized-lake-views-in-microsoft-fabric/#more-1468" class="more-link elementor-more-link">Weiterlesen</a>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SAP Mirroring in Microsoft Fabric with SAP Datasphere Step by Step Guide</title>
		<link>https://renefuerstenberg.de/microsoftfabric/sap-mirroring-in-microsoft-fabric-with-sap-datasphere-step-by-step-guide/</link>
		
		<dc:creator><![CDATA[Rene Fürstenberg]]></dc:creator>
		<pubDate>Mon, 16 Mar 2026 08:57:28 +0000</pubDate>
				<category><![CDATA[Microsoft Fabric]]></category>
		<guid isPermaLink="false">https://renefuerstenberg.de/?p=1209</guid>

					<description><![CDATA[Introduction In this article, I walk through the complete process of replicating data from an SAP S/4HANA system into Microsoft Fabric. The goal was to build an end-to-end setup that connects the SAP landscape with modern analytics capabilities in Fabric. To achieve this, I combined several components from both SAP and Microsoft: the SAP Cloud [&#8230;]]]></description>
										<content:encoded><![CDATA[		<div data-elementor-type="wp-post" data-elementor-id="1209" class="elementor elementor-1209">
				<div class="elementor-element elementor-element-b09db5b e-flex e-con-boxed e-con e-parent" data-id="b09db5b" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-8b1a49d elementor-widget elementor-widget-text-editor" data-id="8b1a49d" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><strong style="color: #444444; font-size: 1.75em;">Introduction</strong></p><div><p>In this article, I walk through the complete process of replicating data from an SAP S/4HANA system into Microsoft Fabric. The goal was to build an end-to-end setup that connects the SAP landscape with modern analytics capabilities in Fabric. To achieve this, I combined several components from both SAP and Microsoft: the SAP Cloud Connector, SAP Datasphere, Azure Data Lake Storage Gen2, and finally the Mirrored SAP Database item inside Microsoft Fabric.</p><p>The article is based on the exact steps I carried out in my own environment. Along the way, I encountered a few challenges on the SAP side, especially when configuring the connection through the SAP Cloud Connector. Once this part was working, the remaining setup in Microsoft Fabric was straightforward. In the end, the result is a working replication pipeline that allows SAP data to be used directly in Fabric and prepared for further analytics scenarios.</p></div>								</div>
				</div>
				<div class="elementor-element elementor-element-4b7944b elementor-widget elementor-widget-read-more" data-id="4b7944b" data-element_type="widget" data-e-type="widget" data-widget_type="read-more.default">
				<div class="elementor-widget-container">
					</div></div></div></div></div> <a href="https://renefuerstenberg.de/microsoftfabric/sap-mirroring-in-microsoft-fabric-with-sap-datasphere-step-by-step-guide/#more-1209" class="more-link elementor-more-link">Weiterlesen</a>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
