# Microsoft Fabric Destination

<p>RudderStack now supports <a href="https://www.rudderstack.com/docs/destinations/warehouse-destinations/microsoft-fabric/" >Microsoft Fabric</a> as a warehouse destination. You can load event data from your sources into a Fabric Warehouse.</p>

<blockquote class="announcement">
  <div class="tip-quote">
    
    <div class="tip-text"><p><strong>The Microsoft Fabric destination is in Private Beta.</strong></p>
<p>Reach out to <a href="mailto:support@rudderstack.com" >Customer Success</a> if you&rsquo;re interested in enabling this destination for your workspace.</p>
</div>
  </div>
</blockquote>

<!-- end-chunk -->
<!-- begin-chunk -->
<h2 id="why-we-built-this-integration">Why we built this integration</h2><p><a href="https://learn.microsoft.com/en-us/fabric/fundamentals" >Microsoft Fabric</a> is an analytics platform for data engineering, data warehousing, and business intelligence. This destination loads your event data into a Fabric Warehouse so you can query it with the rest of your Fabric data.</p>
<p>Each sync stages files in a Lakehouse on <a href="https://learn.microsoft.com/en-us/fabric/onelake" >OneLake</a>, then loads them into the Warehouse. The Lakehouse and the Warehouse need to be in the same region. Tables follow the <a href="https://www.rudderstack.com/docs/destinations/warehouse-destinations/warehouse-schema/" >Warehouse Schema</a>, so the column layout matches your other warehouse destinations.</p>
<!-- end-chunk -->
<!-- begin-chunk -->
<h2 id="key-features">Key features</h2><ul>
<li><strong>Service principal authentication</strong>: You connect with a Microsoft Entra service principal. That is the only supported account type.</li>
<li><strong>Schema updates</strong>: The namespace schema is created when it doesn&rsquo;t exist. Tables are created and altered as the event schema evolves. You can&rsquo;t change the namespace after you create the destination.</li>
<li><strong>Append or merge</strong>: Warehouse append is on by default. Turn it off to merge rows and avoid duplicates. Merging can increase warehouse operation time.</li>
<li><strong>Scheduled syncs</strong>: The default frequency is every 3 hours. You can set a UTC start time and an exclude window. The 5-, 10-, and 15-minute options are available only on certain plans.</li>
<li><strong>Cloud mode</strong>: Every source type connects in <a href="https://www.rudderstack.com/docs/destinations/rudderstack-connection-modes/" >cloud mode</a>. You can also configure consent management providers.</li>
<li><strong>Case-sensitive names</strong>: Fabric&rsquo;s default collation keeps the original case of schemas, tables, and columns. Use the same capitalization when you query them.</li>
</ul>
<!-- end-chunk -->
<!-- begin-chunk -->
<h2 id="get-started">Get started</h2><ol>
<li>Create a Fabric Warehouse and a staging Lakehouse in the same region.</li>
<li>Register a Microsoft Entra app and record the Tenant ID, Client ID, and client secret Value.</li>
<li>Ask your Fabric administrator to allow service principals to use Fabric APIs, and assign the app the Contributor role or higher on each workspace that contains the Warehouse or Lakehouse.</li>
<li>In RudderStack, add <strong>Microsoft Fabric</strong> as a destination, connect it to your source, and select the workspace and Lakehouse.</li>
</ol>
<p>See the <a href="https://www.rudderstack.com/docs/destinations/warehouse-destinations/microsoft-fabric/" >Microsoft Fabric</a> documentation for the full access setup and connection settings.</p>