Troubleshooting & support · Resolve access and availability
Troubleshooting Fabric access
Check personal access, the profile binding and the instance connection separately.
On this page
Before you start
- Know whether the failure is in Emplyr Reports, Settings → Fabric setup, or Microsoft Fabric itself.
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- Confirm the instance, active profile and workspace name. The workspace you need must be the profile’s mapped workspace.
- If Settings → Fabric setup is missing or Get access to workspace is unavailable, have your role checked for Fabric setup Settings access and explicit Fabric Access. The profile’s Fabric Access module must also be enabled.
- If tenant access is missing, have an administrator refresh your tenant status and send/complete the Microsoft invitation. Accept it with the intended Microsoft account.
- If Emplyr reports that the workspace is missing, ask an instance admin to refresh Admin → Fabric and verify the service principal’s workspace access and profile binding.
- If Microsoft Fabric opens in another tenant/account, switch to the intended Microsoft identity. The Emplyr login and Microsoft browser session can be different.

Check Fabric state, Emplyr access and event collection separately. This example capacity is activated and receiving events; amounts are fictional. - If the profile is paused or placement is rejected, check the enrolled instance’s subscription and activated/owned capacity placement before retrying.
What you should see
The issue is narrowed to role/module access, Microsoft membership, app connection, workspace binding or commercial placement.
If something goes wrong
You are a worker account
Direct Fabric tenant access is not available to workers. Ask the process owner which Emplyr task you should use.
An embedded report is missing but Fabric opens
Use reporting troubleshooting. Direct workspace access does not create Emplyr report grants.