Sign up & instance setup · BYOF: identity, access and monitoring
Install Fabric Capacity Metrics and optionally import usage history
Set up Microsoft’s monitoring app, then check whether its model can supply Emplyr’s optional one-time history import.
BYOF setup checklist · Task 5 of 5 · optional history
On this page
Before you start
- The installer needs capacity-admin authority and Power BI Pro, Premium Per User or an individual trial. Microsoft recommends a Pro-licensed workspace to avoid capacity-overload throttling.
- Complete live Eventstream monitoring first for Emplyr readiness. Installing this app does not replace the live connection. Use a compatible model and approved service-principal access if importing history.
Two monitoring tools with different jobs
On smaller screens, scroll the table sideways to see all columns.
| Tool | What it supplies |
|---|---|
| Live capacity Eventstream | Required ongoing operation + overview events for Emplyr readiness and usage. |
| Microsoft Fabric Capacity Metrics app | A separate Microsoft report/model; an optional source for compatible recent historical aggregates. |
Follow these steps
Screenshots use fictional training data. Names, dates and amounts are examples. Select an image to view it at full size.
- In the Power BI service open Apps → Get apps. Find Microsoft Fabric Capacity Metrics, choose Get it now and complete the installation prompts.
- Open the installed app. When prompted to connect your own data, select Connect.
- Set UTC_offset to your organisation’s offset (South Africa: 2). Current version 3.0 does not require the old CapacityID, DefaultCapacityID or RegionName inputs; use version-specific Microsoft instructions if those fields appear.
- Select Next. Use OAuth2 authentication and Organizational privacy, then Sign in and continue with the authorised capacity administrator.
- Select the intended Capacity Name. Allow the initial data load, refresh if necessary and verify the report shows that capacity’s usage.
- For optional Emplyr history, open the workspace created by the installation. Record its workspace ID from the browser URL after /groups/. Use Manage access → Add people or groups to add the Emplyr service principal as Member, as in the linked workspace guide. This supplies the workspace/model Read and Build access for this setup; content-workspace access alone is insufficient.
- Have the Fabric administrator enable Dataset Execute Queries REST API under tenant Integration settings for the approved scope. Check the model is compatible with service-principal queries; Microsoft does not support that identity with RLS/SSO-enabled models for this API.
- In Emplyr, after Verify events & continue succeeds, open Add usage history. Enter Capacity Metrics workspace ID to target this workspace, or leave it blank for discovery. Choose Import last 14 days once you have checked the model and expected data.

History import is optional. Enter the Metrics workspace ID or allow discovery, or choose Skip history & go to Emplyr. - Review the imported row count and UTC date range, then choose Go to Emplyr. If the app/model is unavailable or incompatible, use Skip history & go to Emplyr; investigate history separately while keeping live monitoring working.
Worked example
NovaNest’s administrator installs the Metrics app and confirms its report displays the Operations capacity. After the live Eventstream passes verification, they grant the application access to the Metrics model and import its available completed-day history once. They record the row count and UTC dates. If model compatibility fails, they skip history and retain the working live feed.
Provider references
What you should see
The Microsoft monitoring report displays the intended capacity. Emplyr either confirms its optional import with dates/row count or continues with live monitoring and history explicitly skipped.
If something goes wrong
The report works but Emplyr cannot find/import its model
Your interactive capacity-admin identity and the service principal have different access. Check Metrics workspace ID, model Read/Build, Execute Queries settings and model compatibility. A newer Microsoft model is not automatically guaranteed compatible with Emplyr’s existing history queries.
The import succeeds with zero rows
Check the target model, available history and activated capacity before importing. A successful zero-row import still completes the one-time import; it is not a trial run.
Can I repeat or extend the history import?
The current flow permits one successful import per instance for the previous 14 completed UTC days through yesterday. Failed attempts can be retried; completed imports are not a recurring refresh.
The historical report shows more detail than Emplyr
Emplyr imports daily item-level aggregates, not a reconstruction of every historical run. Past imported usage does not create retrospective commercial charges. Live events supply ongoing monitoring.