<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Copilot Capacity in Notebooks in Data Engineering</title>
    <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130209#M15405</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/1261780"&gt;@ndisch4&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may notice “Copilot in Fabric” usage due to one of the Copilot features linked to notebooks—such as inline completions, autocomplete, schema-aware suggestions, or the Copilot pane—being enabled somewhere. Additionally, as Copilot operates in the background and its CU usage is averaged over time, usage spikes may appear several minutes after the initial activity. The Capacity Metrics app will then attribute those CU seconds to “Copilot in Fabric”.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To better manage this, I recommend using a dedicated Copilot Capacity. If you need occasional access to Copilot but want to minimise its impact on data workloads, you can enable a small Copilot Capacity (F2+) and assign yourself to it. This approach ensures your Copilot usage is billed and tracked separately from the capacity supporting your notebooks, helping to prevent unexpected Copilot usage from affecting engineering tasks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For further details, please refer to the following link:&lt;/P&gt;&lt;P&gt;&lt;A title="https://learn.microsoft.com/en-us/fabric/enterprise/fabric-copilot-capacity" href="https://learn.microsoft.com/en-us/fabric/enterprise/fabric-copilot-capacity" rel="noreferrer noopener" target="_blank"&gt;Fabric Copilot capacity - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Mar 2026 17:38:12 GMT</pubDate>
    <dc:creator>deborshi_nag</dc:creator>
    <dc:date>2026-03-11T17:38:12Z</dc:date>
    <item>
      <title>Copilot Capacity in Notebooks</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130114#M15402</link>
      <description>&lt;P&gt;I am having an issue when running a notebook. When I run the notebook manually I get Copilot autocompletions even though they are turned off, and this seems to cause a Capacity spike. I was running a notebook with no obvious use of Copilot and about 10-20 mintues later capacity spiked to 100% even though it was just the notebook running. My question then becomes, why am I getting spikes for 'Copilot in Fabric' for my specific notebook even though I am not actively using Copilot?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2026 15:21:27 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130114#M15402</guid>
      <dc:creator>ndisch4</dc:creator>
      <dc:date>2026-03-11T15:21:27Z</dc:date>
    </item>
    <item>
      <title>Re: Copilot Capacity in Notebooks</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130209#M15405</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/1261780"&gt;@ndisch4&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You may notice “Copilot in Fabric” usage due to one of the Copilot features linked to notebooks—such as inline completions, autocomplete, schema-aware suggestions, or the Copilot pane—being enabled somewhere. Additionally, as Copilot operates in the background and its CU usage is averaged over time, usage spikes may appear several minutes after the initial activity. The Capacity Metrics app will then attribute those CU seconds to “Copilot in Fabric”.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To better manage this, I recommend using a dedicated Copilot Capacity. If you need occasional access to Copilot but want to minimise its impact on data workloads, you can enable a small Copilot Capacity (F2+) and assign yourself to it. This approach ensures your Copilot usage is billed and tracked separately from the capacity supporting your notebooks, helping to prevent unexpected Copilot usage from affecting engineering tasks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For further details, please refer to the following link:&lt;/P&gt;&lt;P&gt;&lt;A title="https://learn.microsoft.com/en-us/fabric/enterprise/fabric-copilot-capacity" href="https://learn.microsoft.com/en-us/fabric/enterprise/fabric-copilot-capacity" rel="noreferrer noopener" target="_blank"&gt;Fabric Copilot capacity - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2026 17:38:12 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130209#M15405</guid>
      <dc:creator>deborshi_nag</dc:creator>
      <dc:date>2026-03-11T17:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: Copilot Capacity in Notebooks</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130233#M15407</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the response, I have two follow-up questions.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Where would that "somewhere" be?&lt;OL&gt;&lt;LI&gt;I have now turned off Copilot for the Fabric tenant, so I will see if that will help at all. Is there another spot I should be checking?&lt;/LI&gt;&lt;/OL&gt;&lt;/LI&gt;&lt;LI&gt;Why would this start now, rather than a few months ago.&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Wed, 11 Mar 2026 18:09:08 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130233#M15407</guid>
      <dc:creator>ndisch4</dc:creator>
      <dc:date>2026-03-11T18:09:08Z</dc:date>
    </item>
    <item>
      <title>Re: Copilot Capacity in Notebooks</title>
      <link>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130329#M15414</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/1261780"&gt;@ndisch4&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) That is in&amp;nbsp;&lt;STRONG&gt;Copilot and Azure OpenAI Service&amp;nbsp;&lt;/STRONG&gt;settings -details of the settings can be found on this page&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-copilot" target="_blank"&gt;Copilot admin settings - Microsoft Fabric | Microsoft Learn&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) The change in AI related billing that happened in Feb is below - Notebook and Dataflow Gen2 items were affected by this. If you used AI functions it might answer yuor question!&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Billing updates: new operations for Fabric AI functions and AI services&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://blog.fabric.microsoft.com/en-gb/blog/billing-updates-new-operations-for-fabric-ai-functions-and-ai-services?ft=02-2026:date" target="_blank"&gt;Billing updates: new operations for Fabric AI functions and AI services | Microsoft Fabric Blog | Microsoft Fabric&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Mar 2026 20:48:37 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Data-Engineering/Copilot-Capacity-in-Notebooks/m-p/5130329#M15414</guid>
      <dc:creator>deborshi_nag</dc:creator>
      <dc:date>2026-03-11T20:48:37Z</dc:date>
    </item>
  </channel>
</rss>

