Forum Discussion
Power BI Fabric Capacity
Hi krishna_vala03 , Thank you for reaching out to the Microsoft Community Forum.
The fixed price you see in Pay as you go is just the hourly rate of the capacity, not a fixed monthly charge. You are billed only for the time the capacity is running, not for the number of exports. Fabric is capacity based, not usage based, so if it’s running you pay, even if idle, but you can pause it anytime to stop billing.
For your Power Automate export, you can minimize cost by starting the capacity only when needed, running the export and stopping it right after. This way you only pay for a short duration instead of keeping it on all day.
Hi krishna_vala03 , Thank you for reaching out to the Microsoft Community Forum.
The Power Automate “Export to file for Power BI reports” action uses the Power BI ExportToFile API, which requires the report to be in a workspace backed by dedicated capacity. A PPU license alone isn’t sufficient for Power BI reports in this scenario. The supported options are Premium capacity (P-SKU), Embedded (A/EM) or Fabric capacity (F-SKU) assigned to the workspace.
You don’t need F64 specifically. The Fabric trial runs on F64, which is why it works there, but the requirement in Microsoft documentation is dedicated capacity, not a specific SKU size. So, if you purchase Fabric capacity such as F2 or higher and assign the workspace to it, the Power Automate export action should work. The main difference with smaller SKUs like F2 is performance and concurrency limits, not feature availability.
Export and Email a Report with Power Automate - Power BI | Microsoft Learn
Export Power BI embedded analytics reports API - Power BI | Microsoft Learn