Power BI API export returns 403 for semantic models while dataflow backup succeeds

Hello Microsoft Support Team,

I need help investigating a Power BI API behavior in our backup automation.

Summary

• We can successfully authenticate and list workspace inventory.
• Dataflow backup succeeds across multiple workspaces.
• Semantic model PBIX export fails with HTTP 403 in the same workspaces.

Observed behavior

• Endpoint used for semantic model export:
  /v1.0/myorg/groups/{workspaceId}/reports/{reportId}/Export?downloadType=IncludeModel&preferClientRouting=true
• Response for semantic model exports:
  HTTP 403 (consistently)
• Dataflows in the same workspace are downloaded successfully using:
  /v1.0/myorg/groups/{workspaceId}/dataflows and /dataflows/{id}

Example run evidence

• Workspace count processed: 29
• Example workspace:
  Hofu City Hall
  workspaceId: 15be756d-47e9-42e8-842e-1f0cb65fd441
• Result:
  dataflows found/downloaded successfully
  semantic models all failed with HTTP 403
• Another workspace also had a transient timeout on dataflow listing, but the persistent blocker is semantic model export 403.

What we already validated

• Token refresh and authentication are working.
• Workspace and report discovery are working.
• Dataflows can be listed and exported successfully.
• We added retry logic for transient network/API errors.
• Semantic model export still returns 403 consistently.

Request
Please help confirm:

1. Required tenant settings for PBIX export via report Export API with IncludeModel.
2. Required licensing/capacity/workspace configuration for this export path.
3. Required permission scopes/roles for delegated token use.
4. Whether this endpoint is restricted for certain semantic model/report configurations.

If needed, I can provide:

• Full request/response headers (sanitized)
• Correlation IDs / Request IDs from failed responses
• Workspace IDs list used in this run
• Timestamped logs and status CSV outputs

Thank you.