ExportTo REST API fails with FeatureNotAvailableError for PPU workspace with DirectQuery datase

[Farzad1117]

I’m trying to export a Power BI report to PDF using the ExportTo REST API. Here are the details:

Workspace: PPU

User license: Premium Per User (PPU)

Dataset: All tables are DirectQuery (checked in Power BI Desktop)

Error received: FeatureNotAvailableError when calling the API

I wanted to ask:

1. Is there any way to make DirectQuery datasets exportable via the API?

2. Will moving the workspace to reserved Premium capacity (P1/P2/P3) allow the export for DirectQuery datasets?

3. Are there any other recommended workarounds for automating PDF exports in this scenario?

Any guidance or experiences would be greatly appreciated.

Thank you!

[v-hashadapu]

Hi @Farzad1117 , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.

[Farzad1117]

I’ve resolved this issue: the ExportTo REST API does not work on PPU workspaces. the report must be in a dedicated Premium/Fabric capacity. Using an Import dataset ensures the PDF exports correctly

[v-hashadapu]

Hi @Farzad1117 , Thank you for reaching out to the Microsoft Community Forum.

The ExportTo REST API only works when the report and all referenced semantic models are hosted on Fabric, Premium or Embedded capacity. A PPU workspace alone is not supported for REST-based PDF export and receiving FeatureNotAvailableError in that setup is expected. Moving the workspace to a dedicated capacity is therefore a required first step. That said, running on Fabric or Premium capacity does not reliably enable PDF export for DirectQuery only reports. While DirectQuery models are allowed to live on capacity, the export process requires the service to fully render report pages server-side within strict execution limits.

In practice, DirectQuery reports frequently fail export due to live query execution, backend latency or unsupported query patterns. This is a known product limitation rather than a configuration or licensing issue. If automated PDF export is a firm requirement, currently, the only reliable way is to use an Import or Dual-mode reporting layer, often as a snapshot or near-real-time replica built specifically for exports. Pure DirectQuery models remain unsuitable for reliable REST-based PDF automation, regardless of whether the workspace is on PPU or dedicated capacity.

[cengizhanarslan · Accepted solution]

The ExportToFile / exportToFile REST API is not supported for Premium Per User (PPU) workspaces. Microsoft calls this out explicitly in the Export-to-file docs. Microsoft Learn

So if your report lives in a PPU workspace, the API can fail even if everything renders fine interactively in the Service. So you need to move the workspace to Premium capacity (or Embedded / Fabric capacity) and keep using ExportToFile.

[GilbertQ]

Hi @Farzad1117 

you can actually export the Semantic model using Fabric Studio in Visual Studio Code. Here is a link to my blog post explaining how to do this: Download any Power BI Report from the Power BI Service - FourMoo | Microsoft Fabric | Power BI

[tayloramy]

Hi @Farzad1117, 

@Vinodh247 I don't believe that is correct. 

This feature requires a Fabric or Permium Capacity. 

Export Power BI embedded analytics reports API - Power BI | Microsoft Learn

• All related semantic models in the report you're exporting must reside on a Fabric, Premium or Embedded capacity, including semantic models with a Direct Query connection.

Unless you already have a P sku capacity sitting around, you will need to get an F sku capacity. Power BI Premium capacities are end of life and you can't buy them anymore. An F64 is roughly the same as a P1 capacity. 

[Vinodh247]

this is a hard limitation, not a bug.

1. Can DirectQuery datasets be exported via ExportTo REST API?
No. ExportTo (PDF/PPT) via REST API does not support DirectQuery datasets. That is exactly why you are getting FeatureNotAvailableError. PPU does not change this.

2. Will moving to Premium capacity (P1/P2/P3) fix it?
No. Even on dedicated Premium capacity, ExportTo REST API still does not support DirectQuery. Premium helps with scale and concurrency, not this feature gap.

3. Workarounds for automated PDF export
Only practical options today:

• Convert the dataset (or a reporting layer) to Import or Dual mode and export from that model.

• Use Power Automate “Export to PDF” (still has the same DirectQuery limitation in most cases, so test carefully).

• Build a snapshot Import model (scheduled or near-real-time) purely for reporting/export.

• Last resort: browser-based automation (Playwright/Selenium) to export via UI. Not supported, but used in practice.

If automated PDF export is a requirement, DirectQuery only models are a dead end today, regardless of PPU or Premium capacity.