Approved Power BI workspaces
UsageVault connects through supported Microsoft interfaces using access authorized by your organization.
Security and data ownership
Your environment. Your access controls. Your history.
UsageVault is designed for a customer-controlled deployment. The standard architecture stores collected Power BI usage history in your SQL environment rather than a separately hosted UsageVault analytics service.
Data flow
A focused collection path with clear control points.
The exact services and controls depend on your approved architecture. During readiness review, the implementation path is documented before deployment.
Customer-hosted execution
Scheduled collection, validation, retries, and operational monitoring run within the approved customer environment.
Your SQL and Power BI
History is written to customer-controlled SQL and surfaced through the delivered semantic model and Power BI report.
UsageVault does not claim that self-hosting alone makes a deployment secure. Your organization's identity, network, host, database, backup, monitoring, and Power BI controls remain essential.
Shared responsibility
Security responsibilities remain explicit.
| Area | UsageVault implementation | Customer responsibility |
|---|---|---|
| Access | Configure the product to use the approved access method and documented scope. | Approve identities, permissions, workspace access, credential handling, and privileged administration. |
| Infrastructure | Install and configure the supported collection, database objects, monitoring, and report components. | Provide and secure compute, SQL, networking, endpoints, host controls, patching, and availability. |
| Data | Collect and validate available usage information from supported interfaces. | Determine lawful use, authorized scope, access, privacy treatment, retention, deletion, and internal policy. |
| Backup and recovery | Document relevant product data stores and operational considerations. | Configure, test, monitor, and retain backups and disaster-recovery procedures. |
| Report distribution | Deliver a Power BI semantic model and report for deployment into the approved tenant. | Manage Power BI workspace permissions, sharing, row-level security if added, and downstream exports. |
| Operations | Provide supported-product documentation and standard support. | Monitor customer infrastructure and coordinate changes to licensing, permissions, networks, or Microsoft services. |
Security review
Questions we address before implementation.
What user data is available?
Source availability varies. UsageVault can preserve available user-level activity when authorized, while the customer determines whether identifiable fields should be collected, restricted, or transformed.
How are credentials handled?
The deployment uses a customer-approved access method and customer-controlled secrets practice. The final approach is documented during readiness review.
How long is data kept?
The customer sets database retention based on internal policy and capacity. UsageVault does not impose a separate fixed retention period.
What certifications are claimed?
This page does not claim SOC 2, ISO 27001, FedRAMP, HIPAA, or other certification. Ask for the current security materials relevant to your review.
Technical review
Bring your security and architecture questions.
We can walk through the standard data flow, prerequisites, and shared responsibility boundary with your technical stakeholders.
Request a technical walkthrough
Use the subject line “UsageVault security review” for the right preparation.
Email the security questions