Azure Microsoft Fabric
Required attributes
- Fabric Workspace Id — the GUID of the Fabric workspace that holds the
Notebooks, Spark Job Definitions, Data Pipelines and Dataflows Polysync
will discover and run.
Fabric is addressed through its own REST API — no Azure Subscription Id or
Resource Group Name is needed (or used) by Polysync for this platform.
Authentication methods
- Polysync Service Principal ⭐ (recommended) — no extra attributes; grant the Polysync Enterprise Application Contributor on the Fabric workspace. This is the standard method for all Polysync tenants.
- Service Principal — Tenant Id, Client Id, Client Secret. Use when you need a dedicated SPN per workspace. Rotate the secret regularly.
- Certificate — Tenant Id, Client Id, Certificate (upload the PFX), optional Certificate Password.
Granting Polysync access
Polysync Service Principal stores no credentials — it authenticates as the multi-tenant
Polysync enterprise application. The Setup editor shows that application's (client) ID beside
the auth-method hint: grant that application the role below on the resource.
- If it is not listed under Enterprise applications in your Entra tenant, an administrator must
consent to the Polysync application once. This happens automatically for a subscription bought
through Azure Marketplace.
- On a subscription that has never used this resource type, register its provider first —
az provider register --namespace <provider-namespace> --wait.
Permissions checklist
- The chosen identity must hold the Contributor role on the Fabric workspace (or an equivalent permission granting pipeline-run access).
- Ensure the Fabric capacity has the target workspace assigned and that the identity has access to the specific items (pipelines) it needs to trigger.
Supported jobs
Microsoft Fabric exposes four Polysync job types. See each dedicated page
for parameter handling, output binding, execution flow, monitor URL, and
troubleshooting: