Approved Power BI workspaces
Only the workspaces and Usage Metrics sources your organization approves are in scope.
Implementation without the mystery
Know the boundary before the work begins.
UsageVault is installed in customer-controlled infrastructure. This page explains what must be ready, what UsageVault configures, what is validated, and what your administrators own after handoff—without publishing proprietary product internals.
Buyer-level architecture
Four controlled stages from source to decision.
The public architecture describes trust boundaries and responsibilities. Detailed product mechanics are supplied only to authorized implementers and reviewers.
Customer-controlled compute
A scheduled product component collects available evidence using a customer-approved identity.
Your SQL environment
Historical usage is retained under your access, backup, privacy, and retention controls.
Your Power BI tenant
The semantic model and report are deployed where your team already shares analytics.
Readiness checklist
What should exist before installation.
Exact supported versions and settings are confirmed against the current compatibility matrix during readiness review.
Microsoft access
Power BI licensing, Usage Metrics availability, approved workspace scope, an approved noninteractive identity, and the required tenant/workspace permissions.
Compute and network
Supported customer-managed compute with outbound Microsoft connectivity, database connectivity, service administration, patching, and monitoring.
SQL and storage
An approved SQL environment, least-privilege access, capacity planning, encryption choices, backups, restoration testing, and retention ownership.
People and decisions
Power BI, identity, infrastructure, SQL, security, privacy, and business owners who can approve scope and accept the handoff.
Shared responsibility
A clear split between product work and customer operations.
| Area | UsageVault | Customer |
|---|---|---|
| Scope | Document supported product boundary and configured workspace scope. | Approve workspaces, owners, privacy, retention, and business audiences. |
| Identity | Configure the supported access path and validate product access. | Own identities, credentials, tenant settings, rotation, and revocation. |
| Infrastructure | Install and configure supported product components. | Provide, secure, patch, monitor, back up, and recover compute, SQL, and network services. |
| Data | Collect and validate available source evidence. | Determine lawful use, access, masking, retention, deletion, and internal policy. |
| Analytics | Deliver the supported semantic model, report, definitions, and handoff. | Manage Power BI distribution, audience permissions, and approved customization. |
| Support | Support the product within the agreed boundary. | Operate customer infrastructure and coordinate environmental changes. |
Implementation stages
From readiness decision to administrator handoff.
The sequence is fixed enough to control risk and flexible enough to respect customer change processes.
Confirm
Scope, prerequisites, privacy, responsibilities, compatibility, and success criteria.
Configure
Approved product components, access, workspace scope, storage, schedule, and reporting.
Validate
Access, collection, history, data quality, isolation, refresh, monitoring, and recovery steps.
Hand over
Administration, workspace onboarding, troubleshooting, backups, upgrades, and support path.
Acceptance evidence
What should be demonstrated before handoff.
- Source accessOnly approved workspaces are accessible and the expected source fields are available.
- Historical writesExpected periods and measures reach the approved SQL environment without uncontrolled duplication.
- Operational healthFailures are visible, repair steps are documented, and the agreed notification path works.
- Audience isolationBusiness and administrative views follow the approved access boundary.
- Power BI deliveryThe semantic model refreshes and the report answers the agreed validation questions.
- Administrator readinessNamed customer operators can run the documented onboarding and recovery process.
Readiness review
Test the prerequisites before committing to a deployment.
Bring your workspace count, licensing, infrastructure, security, privacy, and operating constraints. The goal is to identify a fit or disqualifier early.
30-minute technical walkthrough
No source code or tenant access is needed for the first conversation.
Request a walkthrough