Fabric Connections

Fabric connections let Antares deploy converted Power BI reports and semantic models to Microsoft Fabric workspaces.

You do not need a Fabric connection to analyze Tableau workbooks. Configure Fabric when you want to deploy Converter outputs to Microsoft Fabric.

What a Fabric connection is used for

Fabric connections let Antares:

• List Fabric workspaces visible to the connection.
• Deploy Power BI reports.
• Deploy semantic models.
• Reuse saved authentication for conversion deployment.

Fabric connections do not manage workspaces, users, tenant settings, or Fabric administration.

Authentication methods

Antares supports two Microsoft Fabric authentication methods.

Method	Best for	Requires
Service Principal	Long-running automation and team deployments.	Entra ID app registration, Fabric admin setup, and workspace access.
User Auth	Quick setup with a Microsoft work or school account.	Interactive Microsoft sign-in.

Service Principal

Use Service Principal authentication when deployments should not depend on an individual user session.

Required values:

• Tenant ID.
• Client ID.
• Client Secret.

Before creating the connection:

1. Register an application in Microsoft Entra ID.
2. Create a client secret.
3. Enable service principals to use Fabric APIs in the Fabric Admin Portal.
4. Grant the service principal access to the target Fabric workspaces.

A Service Principal connection test verifies that Antares can access Fabric and shows the number of visible workspaces.

Note

Service Principal setup may require both an Entra ID administrator and a Fabric administrator.

User Auth

Use User Auth when you want to sign in with your Microsoft work or school account.

Antares uses device code authentication. The wizard opens Microsoft sign-in, shows a code, and waits for sign-in to complete.

User Auth access is limited to the workspaces your account can reach.

Note

User Auth sessions can stay active for an extended period, but tenant policy, revocation, or token expiry can require re-authentication. If access expires, re-authenticate the connection.

Connection wizard

The Fabric connection wizard has three steps.

Step	What you do
Basic Info	Enter a connection name, optional description, and authentication method.
Authentication	Enter Service Principal credentials or complete Microsoft User Auth sign-in.
Summary	Review the connection details and save the connection.

Testing and statuses

Run Test Connection to verify that Antares can access Fabric with the selected authentication method.

A successful test can show tenant ID, signed-in user or app identity, workspace count, and visible workspace names.

Fabric connections show one of these statuses:

Connected	The latest connection test succeeded.
Failed	The latest connection test failed.
Expired	A User Auth session has expired.
Untested	The connection has not been tested yet.

Managing Fabric connections

Open Connections and select the Microsoft Fabric tab to manage saved Fabric connections.

The list shows:

• Name and description.
• Tenant ID.
• Signed-in user or client ID.
• Authentication method.
• Status.
• Last tested time.

You can test or delete a Fabric connection from the Actions column.

User Auth connections can also show a re-authentication action when the session expires or the connection test fails.

Re-authentication

Re-authentication is available for User Auth connections.

Antares starts a new Microsoft device code flow. After sign-in completes, the saved connection is refreshed.

Service Principal connections do not use re-authentication. If a client secret expires, create a new secret and create a new connection with the updated credential.

Workspace access

A successful connection does not mean every Fabric workspace is available.

Antares can only deploy to workspaces visible to the authenticated user or service principal. If a workspace is missing, check workspace membership, service principal permissions, tenant settings, and capacity requirements.

For deployment steps, see Deploy Power BI Output to Fabric.