Sign up & instance setup · BYOF: identity, access and monitoring
Grant the BYOF service principal its Fabric permissions
Create the scoped security group, enable the right tenant settings and grant capacity access, with optional Graph permissions explained separately.
BYOF setup checklist · Task 2 of 5
On this page
Before you start
- Create the app/service principal first and record its application name/client ID. Use authorised group and Fabric administrators; capacity settings must be changed by a person permitted to administer that capacity.
- Choose the required capabilities from the table. Fabric API settings, capacity rights, workspace roles and Graph application consent are separate checks. An Emplyr role or Azure purchasing role does not grant these rights.
Required rights by capability
On smaller screens, scroll the table sideways to see all columns.
| Capability | Required scope / right |
|---|---|
| Core Fabric API calls | Approved security-group membership plus the Fabric public API tenant setting. |
| Create/assign a workspace to capacity | Create-workspaces tenant setting when applicable, capacity contributor/Admin, and workspace Admin for reassigning an existing workspace. |
| List/embed/export profile reports | Workspace Member or Admin; embedding tenant settings. |
| Manage workspace user/group access through Emplyr | Workspace Admin for the app; directory permissions when the selected flow needs Graph. |
| Configure operation/overview sources | Human capacity admin plus Contributor or higher in the Eventstream workspace. |
| Optional Metrics-app history queries | Execute Queries tenant setting, model Read/Build and a compatible model. |
Follow these steps
- In Microsoft Entra admin center go to Entra ID → Groups → All groups → New group. Choose Security, a descriptive group name and Assigned membership. Keep the group as an ordinary security group; Fabric scoping does not require Entra role assignment to the group.
- Create the group, open it and choose Members → Add members. Search for the app/service-principal name, select the enterprise application and confirm. Verify the application appears in Members; adding your own user account instead will not authorise Emplyr.
- As a Fabric administrator, open OneLake catalog → Govern → Configurations → Tenant settings → Developer settings. Tenants with the older navigation expose the same tenant settings under the gear menu → Admin portal.
- Open Service principals can call Fabric public APIs (older labels can refer to using Fabric/Power BI APIs). Enable it for Specific security groups, select the approved group and apply the change.
- If Emplyr will create workspaces, also enable Service principals can create workspaces, connections, and deployment pipelines for that group. If embedding reports, configure Embed content in apps for the approved scope.
- For each intended capacity open OneLake catalog → Govern → Capacities → the capacity, or Admin portal → Capacity settings → Fabric capacity → the capacity. Under Contributor permissions choose Specific users or security groups and add the approved group. Save/apply the setting.
- Have the capacity owner grant capacity Admin only if the application’s agreed task requires it. Capacity contributor is the normal assignment/create-workspace capability; the person configuring the capacity event sources must separately be a capacity admin.
- Follow the workspace guide to assign Member or Admin on the actual content workspace. If optional history import is required, also enable Dataset Execute Queries REST API in Integration settings and arrange model Read/Build access.
- Return to Emplyr and verify the Fabric connection. In Connect live usage or Admin / Global → Fabric → Capacities use Refresh and confirm the intended capacity is discovered. If permissions were just applied, allow propagation and refresh again.
Optional: grant Microsoft Graph permissions for directory features
Only add these when the organisation will use the corresponding directory features. Power BI service-principal embedding does not require a list of Power BI API permissions on this app.
On smaller screens, scroll the table sideways to see all columns.
| Setting | What to select |
|---|---|
| Check status | Microsoft Graph → Application permissions → User.Read.All |
| Invite to tenant | Microsoft Graph → Application permissions → User.Invite.All |
| Search/create groups or update group membership | Microsoft Graph → Application permissions → Group.ReadWrite.All; User.Read.All when resolving users |
- Open Entra ID → App registrations → the application → API permissions → Add a permission.
- Choose Microsoft Graph → Application permissions. Search for and select only the approved permissions from the table, then Add permissions.
- Have an administrator authorised for those Graph application permissions review and grant admin consent for the tenant. Do not assume every application administrator can consent to every Graph permission.
- Check each approved permission is listed as Application and has consent granted for the intended directory. Test the specific directory feature in Emplyr.
Provider references
What you should see
The application is in the scoped security group, required Fabric settings are enabled, intended capacities are accessible, and the remaining workspace checks are explicit.
If something goes wrong
The app is in the group but cannot read a workspace
Tenant API enablement does not grant workspace access. Assign the correct role on that workspace too.
Contributor permissions lets the app assign workspaces but not create event sources
Capacity contributor and capacity admin are different. Use a human capacity admin to configure the required operation-event source.
Directory checks or tenant invitations return Graph 403
Review the optional Graph capability/permission/consent mapping in this guide. A Fabric setting does not grant Microsoft Graph application permissions.