Power BI connector
Deliver computed Genesys Cloud operational KPIs to Microsoft Power BI using streaming API push from your own Azure deployment. The same engine that feeds WFM and APIs keeps your dashboards accurate, timely and consistent with operations.
At a glance
Implemented- What it delivers
- Computed KPI batches pushed to Power BI streaming datasets on scheduler intervals.
- Who consumes
- Supervisors, operations leads and BI teams in Microsoft-centric enterprises.
- Source path
- Reactive Engine → scheduler → Global.Platform.Dispatcher → Power BI streaming API.
- Status
- Implemented and deployable today.
- Heritage
- Streamvane began as a Genesys-to-Power BI real-time platform.
KPI batches are pushed to Power BI streaming endpoints on scheduler intervals with retry handling for rate limits.
The dashboard number and the WFM feed number come from the same computed document.
Endpoint URLs resolve from your Key Vault; nothing is hosted on a vendor connector platform.
Queues, agents, campaigns and presence aggregates, mapped in KPI discovery.
Overview
Dashboards that agree with operations
The hard part of Genesys reporting in Power BI isn't drawing a chart — it's keeping operational metrics accurate, timely and consistent with what WFM and operations expect.
Streaming push from your own pipeline
The connector binds the Reactive Engine to Power BI streaming datasets. KPI batches are pushed on scheduler intervals with retry handling for rate limits, and endpoint URLs are resolved from Key Vault — never embedded in code or hosted by a vendor.
- Streaming API push, not manual Power Query refresh
- Rate-limit aware retries on the push path
- Endpoints and secrets resolved from your Key Vault
Power BI as one consumer among many
Because Power BI is just another sink on the Reactive Engine, the same KPI definition also reaches WFM feeds, REST APIs and message buses. You stop maintaining two definitions of service level — one in BI, one in operations.
- Same core feeds WFM, APIs and brokers
- Custom operational KPI logic, not generic CSV import
- Client-owned Azure instead of a hosted connector
Powered by the Reactive Engine
Every connector is a thin package on one proven core
This connector does not re-implement Genesys integration. It is a focused Global.Platform.* egress package bound to the same Reactive Engine that powers Power BI, operational HTTP feeds and the rest of the catalog. The hard part — correlating the Genesys event stream into trustworthy operational KPIs — is solved once and reused everywhere.
- One ingestion and reactive processing pipeline, many destinations
- Adding a sink is a connector, not a re-architecture
- Consistent KPI semantics across every downstream system
Architecture
From Genesys event to Power BI tile
Metrics are computed once and pushed continuously — and optionally persisted for APIs and feeds in parallel.
Genesys Cloud
Conversations, queues, agents
Service Bus ingress
Durable, ordered events
Reactive Engine
KPI compute
Scheduler
Consolidate & aggregate
Dispatcher
Global.Platform.Dispatcher
Power BI
Streaming datasets
Metrics can also persist to metrics store in parallel, so APIs and HTTP feeds serve the same numbers.
Platform capabilities
The engine guarantees behind every delivery
This connector inherits the correctness, durability and governance of the Reactive Engine — not just a pipe to a destination.
Deterministic reactive processing
The engine computes each KPI from the raw event stream with explicit, reviewable semantics — not opaque aggregates you can't reconcile.
Durable log & replay
An ordered, durable event log lets you recompute, backfill and audit any interval with confidence after a config change.
Idempotent delivery
Keyed envelopes with timestamps let every downstream consumer dedup safely on retry, replay or backfill.
Schema & version governance
Payload contracts are versioned per connector, so consumers upgrade on their own schedule without surprise breakage.
Backpressure & retry
Retry-with-backoff and dead-letter patterns keep transient downstream failures from ever losing a KPI.
Fan-out from one source
Mix real-time streaming and scheduled feeds to many destinations from a single, consistent source of truth.
Integration depth
How deep the integration goes
Integration is a spectrum, not a checkbox. Genesys operational truth is exposed through the Streamvane platform deployed in your Azure — from straightforward egress to a connector embedded in your processing path.
Compute & deliver
The default for most connectors: Genesys operational KPIs are computed once and delivered outward to your destination — streaming or scheduled.
- Read-oriented egress of computed metrics
- Streaming push or scheduled feed cadence
- Same KPI semantics as every other sink
Operational contracts
Schema-controlled, SLA-bound feeds with reconciliation and acceptance criteria — the contract-grade integration WFM and BPO programs depend on.
- Versioned payload schema with acceptance tolerances
- Interval discipline, timezone and latency contracted
- Reconciliation against Genesys source built in
Embedded in your platform
Streamvane is deployed plug-and-play — down to components and code — inside your own cloud subscription on Azure, AWS or GCP, sitting in the Genesys processing path. Genesys operational truth is exposed through our offering, not a brittle hand-built API scrape that drifts on every routing change. Prefer not to operate it? Run the same engine as a managed PaaS bridge instead.
- Deployed into your event mesh and data plane, on Azure, AWS or GCP
- Plug-and-play components, or fully managed as a PaaS
- Extensible with new Global.Platform.* packages
Security
Your data, your tenant, your keys
Security isn't an afterthought bolted onto an export — it's the architecture. Genesys operational data is processed and stored inside your own Azure subscription, under your governance.
Client-owned cloud & data residency
When embedded, Genesys data is ingested, computed and stored inside your own subscription and region — on Azure, AWS or GCP — never transiting or resting in a vendor-controlled cloud.
Encryption in transit & at rest
TLS 1.2+ to every endpoint and Azure storage encryption at rest, with customer-managed keys where your policy requires them.
Secrets in Key Vault, no creds in code
Connection strings, tokens and certificates live in your Key Vault and are read with Managed Identity — never embedded in configuration or source.
RBAC & least privilege
Every component runs with scoped Azure RBAC roles and the minimum permissions needed for its sink — auditable and reviewable.
Network isolation
Private endpoints, VNet integration and IP allow-listing or mTLS keep traffic on private paths where downstream security requires it.
Audit & observability
Diagnostic logs and Application Insights give you a full audit trail of what was produced, when, and to which destination.
DevOps & SecOps
Built to live in your software lifecycle
The connector is engineered, versioned and operated like any other service in your estate — provisioned as code, shipped through your pipelines, governed by your release process.
Infrastructure as Code
The whole footprint — Service Bus, the metrics store, Key Vault, workers and the connector — is provisioned from Bicep or Terraform you can review and own.
CI/CD pipelines
Build, test and deploy through your Azure DevOps or GitHub Actions pipelines, with the connector versioned like any other service.
Environment promotion
Dev, test and production parity with config-driven KPI profiles, so a feed proven in test promotes cleanly to production.
Config & secrets management
KPI profiles, schedules and endpoints are configuration — managed in App Configuration and Key Vault, not hard-coded redeploys.
Observability & SLOs
Health, lag and throughput are surfaced as metrics and alerts so operations teams trust the numbers and catch drift early.
Security in the pipeline (SecOps)
Dependency and static analysis run in the pipeline, with change control and SecOps gates aligned to your release process.
Technical reference
The details engineers will ask for
What gets decided in discovery and what delivery actually involves.
Streamvane vs. hosted BI connectors
If you only need standard Genesys → Power BI datasets with minimal IT involvement, evaluate AppFoundry connectors first. Choose Streamvane when you need client-owned Azure, custom KPI logic, or Power BI plus other sinks.
| Dimension | Hosted no-code connector | Streamvane Power BI |
|---|---|---|
| Setup speed | Very fast for standard datasets | Project-based; faster than SI greenfield |
| Hosting | Vendor connector platform | Your Azure workers |
| Multi-sink | Typically BI-focused | Same core feeds WFM, API, feeds |
| Custom KPI semantics | Standard aggregates + custom project | Reactive Engine native |
| Data ownership | Connector-dependent | the metrics store + your tenant |
Frequently asked
Is this import or streaming?
Streaming API push from computed KPI batches — not a manual Power Query refresh alone. Batches are pushed on scheduler intervals.
Do we need Power BI Premium?
It depends on your dashboard design and capacity model, which we confirm during discovery.
Can we use Fabric instead of streaming datasets?
That's a roadmap and project-scoping topic — see the connector roadmap.
Which metrics are available?
Queue and conversation observation metrics, agent activity and routing, campaign statistics and presence aggregates — exact mapping is defined in KPI discovery.
See this connector running on your Azure tenant
Book a scoping call and we'll map your KPI families to this destination — with the security, lifecycle and depth of integration your teams require.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys