Deploy Power BI Output to Fabric

Fabric deployment is available for Power BI conversion output. It lets Antares publish converted Power BI reports and semantic models into a Microsoft Fabric workspace from the conversion detail page.

Databricks AI/BI conversions do not use this Fabric deployment page.

Before you deploy

Create and test a Microsoft Fabric connection before deploying converted Power BI output.

For connection setup, authentication methods, testing, statuses, and workspace access requirements, see Fabric Connections.

The Fabric connection must be able to see the target workspace. A successful connection test verifies authentication, but deployment still depends on workspace permissions, tenant settings, and capacity requirements.

When deployment is available

The Deploy panel appears only when the conversion produced Power BI output that Antares can deploy.

Deployment may be unavailable when:

• the conversion is still running
• the conversion failed before output generation
• the selected target is not Power BI
• the job produced documentation only
• the output requires manual review before deployment

Deployment workflow

Open the completed Power BI conversion and review the result guidance before deploying.

1. Open the conversion detail page.
2. Confirm the conversion result is ready for deployment.
3. Select a Fabric connection.
4. Select the target workspace.
5. Start deployment.
6. Review deployment logs after the job completes.

Antares records deployment activity on the conversion detail page so you can see what was imported and whether any step failed.

Supported Power BI output

Antares supports deployment flows for converted PBIX and PBIP output.

For large PBIX files, Antares can select the appropriate Microsoft import method based on file size and Fabric capacity requirements.

After deployment

Deployment is not the final validation step. Review the deployed report and semantic model in Fabric before sharing the result with end users.

Depending on the conversion result, you may need to:

• configure an on-premises data gateway for external data sources
• update file paths for file-based data sources
• refresh the semantic model
• review generated .tmdl files
• validate report pages, filters, calculations, and interactions

Deployment issues

If deployment fails, start with the deployment logs on the conversion detail page.

Common causes include missing workspace access, expired User Auth, insufficient Fabric capacity, unsupported output state, or data source configuration that needs manual work.

Re-authentication

User-authenticated Fabric connections may expire. Use re-authentication from the Fabric connection management page to refresh access without recreating the connection.