Paginated Reports with Fabric capacity

[Mike-TDSyynex]

Besides from being a little redundant how can I verify that a Fabric F2 with a reservation is sufficent to export Paginated Reports via Power Automate without actually commiting to a year-long reservation?

SEE: learn.microsoft.com/en-us/power-bi/collaborate-share/service-automate-paginated-integration

• At least one workspace in your Power BI tenant backed by a reserved capacity. This capacity can be any of the A4/P1 – A6/P3 SKUs. 
• At least one workspace in your Power BI tenant backed by a reserved capacity. This capacity can be any of the A4–A6 or P1/F2 and above SKU. 
  
  

[v-saisrao-msft]

Hi @Mike-TDSyynex,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.

Thank you.

[Mike-TDSyynex]

The response (pasted below) is sufficient for my customer for now.  They are a financial org, and this is a subset of their reporting group looking to automate report distrubution.  They are working on testing this now and expect to hear back from them with verification. 
The main apprehension we had was the large disparity of cost from what used to be required for this capability to work and the much lower cost that one would have with the Fabric F2 SKU.  

------------

Yes, a Fabric F2 SKU with reservation does support exporting Paginated Reports via Power Automate. According to the official documentation on Exporting Paginated Reports with Power Automate, an eligible capacity must be backed by a reserved SKU, which includes: 

At least one workspace in your Power BI tenant backed by a reserved capacity. This capacity can be any of the A4–A6 or P1/F2 and above SKU 

[v-saisrao-msft]

Hi @Mike-TDSyynex,

We haven’t heard back from you regarding your issue. If it has been resolved, please mark the helpful response as the solution and give a ‘Kudos’ to assist others. If you still need support, let us know.

Thank you.

[v-saisrao-msft]

Hi @Mike-TDSyynex,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-saisrao-msft]

Hi @Mike-TDSyynex,

Thanks for the update! I'm glad the information was helpful and that your customer is testing the Fabric F2 SKU for their automation needs. 

If this response answers your question, kindly mark it as "Accept as Solution" to help others in the community. We would also appreciate a “Kudos” if you found this helpful! 

Thankyou. 

[v-saisrao-msft · Accepted solution]

Hi @Mike-TDSyynex,

Thank you for reaching out to the Microsoft Froum Community. 

The suggestions provided by @nilendraFabric, and @rohit1991, give great insight into testing the F2 Fabric capacity for exporting Paginated Reports via Power Automate without committing to a long-term reservation. 

In addition to the options they’ve shared, I’d like to suggest a few more points to ensure you’re able to fully evaluate the F2 capacity: 

• After configuring your test with the F2 capacity (using either the trial or PAYG options), it is advisable to actively monitor the capacity performance through the Capacity Metrics in the Power BI Admin Portal. This will provide you with real-time data on resource utilization and help identify any potential bottlenecks early. 
• Based on your workload, it may be beneficial to distribute various tasks, such as Paginated Report exports, data refreshes, or other queries, across multiple workspaces within the F2 capacity to evaluate the system's scalability. 
• If you are particularly interested in evaluating the F2 capacity without a long-term commitment, the Pay-As-You-Go (PAYG) model offers a flexible solution. This approach allows you to test the F2 SKU's performance for a short duration and adjust your usage as necessary. 

For more details, please refer to the below link:

Paginated reports capacity planning for Power BI Premium - Power BI | Microsoft Learn 

If this response resolves your query, please mark it as “Accept as Solution” to help others in the community find it easily. We would also appreciate a “Kudos” if you found this helpful!

Thank you.

[Mike-TDSyynex]

Perhaps I should simplify the question on just a licensing level based on DOCs at link here:
Export paginated reports with Power Automate - Power BI

Q: Will a Fabric F2 SKU with reservation support Paginated Reports via Power Automate?

*In the past the only 2 options were Azure Embedded A4 SKU (minimum) of Power BI premium Capacity P1 SKU minimum.  Both of those options were =+ $4995.00/Month USD.  The F2 SKU is like $151/month with Reservation so kind of a big departure 
Export paginated reports with Power Automate - Power BI | Microsoft Learn

[v-saisrao-msft]

Hi @Mike-TDSyynex,

Thanks for clarifying your question. Yes, a Fabric F2 SKU with reservation does support exporting Paginated Reports via Power Automate. According to the official documentation on Exporting Paginated Reports with Power Automate, an eligible capacity must be backed by a reserved SKU, which includes: 

At least one workspace in your Power BI tenant backed by a reserved capacity. This capacity can be any of the A4–A6 or P1/F2 and above SKU 

Since F2 is explicitly mentioned, it meets the licensing requirements for exporting Paginated Reports via Power Automate when using a reserved capacity. 

If you are considering a long-term commitment, but want to validate performance before reserving, you may explore Pay-As-You-Go (PAYG) F2 capacity as a temporary testing option. This allows flexibility to assess real-world usage before making a reservation. 

For more details, refer to: 
Paginated Reports Capacity Planning for Power BI Premium 

If this response answers your question, kindly mark it as "Accept as Solution" to help others in the community. We would also appreciate a “Kudos” if you found this helpful! 

Thankyou. 

[rohit1991]

Hi @Mike-TDSyynex ,

To verify whether an F2 reserved capacity is sufficient for exporting Paginated Reports via Power Automate without committing to a year-long reservation, you can:

• Use a Fabric F2 Trial

  • Check if your tenant allows an F2 trial under Power BI Admin settings.
  • Create a trial workspace backed by F2 capacity and test Power Automate workflows.

• Check Capacity Metrics in Power BI Admin Portal

  • Go to Power BI Service → Admin Portal → Capacity Metrics.
  • Monitor query refresh times and report execution load to estimate feasibility.

• Use a Pay-As-You-Go (PAYG) Option

  • Consider short-term pay-as-you-go Fabric capacity instead of an annual reservation.
  • Deploy F2 PAYG, test Paginated Report exports, and analyze performance.

• Contact Microsoft Support for Capacity Testing

  • Open a support request to confirm F2 capacity limitations for Paginated Reports.
    
    

"The goal is to turn data into information, and information into insight." – Carly Fiorina

🔗 Need Power BI help? Connect on LinkedIn: Rohit Kumar’s LinkedIn

[nilendraFabric]

@Mike-TDSyynex 

There are 2 options:

Either you can go for 60-day trial of Fabric capacities, which includes an F64 capacity (64 Capacity Units). This trial allows you to test various workloads, including exporting paginated reports, without any financial commitment.

But if  you specifically want to try F2

Opt for Pay-As-You-Go (PAYG)
Instead of committing to a reserved capacity, you can purchase an F2 capacity on a PAYG basis. This option allows you to test the performance of the F2 SKU for as little as $0.36/hour, and you can scale up or down as needed. PAYG provides flexibility to pause or adjust capacity usage, making it ideal for short-term testing before deciding on a long-term reservation

if this is helpful, please accept the answer and give kudos