Connecting Fabric
The setup wizard connects Fabric Link to your Microsoft Fabric workspace using an Entra service principal. It provisions mirrored tables via Open Mirroring and returns the SQL analytics endpoint.
Before you connect
Gather these values:
| Field | Source |
|---|---|
| Entra tenant ID | Azure portal → Microsoft Entra ID → Overview |
| Client ID | App registration for the service principal |
| Client secret | Certificates & secrets on the app registration |
| Fabric workspace ID | Fabric portal → workspace settings |
The service principal needs Contributor (or equivalent write) access to the target workspace. Mirrored databases require a Fabric capacity that supports Open Mirroring.
Run the wizard
- Open Jira admin → Apps → Fabric Link.
- Enter tenant ID, client ID, client secret, and workspace ID.
- Run Precondition checks — the wizard validates Entra auth, workspace access, and capacity.
- Click Provision to create the mirrored database and initial table schema.
On success, the wizard displays the SQL analytics endpoint for your mirrored database. You can query it immediately once the first sync completes.
-- Example: count mirrored issues (table names may vary by version)
SELECT COUNT(*) AS issue_count
FROM jira_issues;
Open Mirroring
Fabric Link writes change files to your workspace’s OneLake landing zone. Open Mirroring continuously applies those files to the mirrored database — no separate ETL job required on your side.
Connection failures
| Symptom | Likely cause |
|---|---|
| Entra auth failed | Wrong secret, expired secret, or missing admin consent |
| Workspace not found | Incorrect workspace ID or principal lacks access |
| Capacity error | Workspace not on a capacity that supports mirroring |
See Troubleshooting for dead-letter replay and health signals.