Expecta Connector
EXPECTA SRL · Intelligence & Research
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 7 captures on record
What the publisher says
As described on Microsoft Marketplace.
The Expecta Connector is an MCP (Model Context Protocol) server that lets Claude Desktop, Claude Code, and other MCP-aware LLM clients ask business-language questions against your Power BI semantic models — and return grounded, audited answers.
## What you install
Show the rest of the publisher’s description (24 more lines)
The offer deploys into a managed resource group in your Azure subscription:
- An Azure Container App running the connector
- A small Azure SQL serverless database for connector configuration
- An Azure Key Vault for the OAuth client cert
- A per-install Azure Container Registry
- A Log Analytics workspace (or routing to your existing one)
- An Entra ID app registration for OAuth client authentication
Total cost: typically $25–40/month, dominated by ACR + serverless SQL + Container App consumption.
## Why this design
- **Your data never leaves your tenant.** No Expecta-controlled service has standing access. The audit log lands in your Log Analytics workspace; the configuration database is in your subscription.
- **Per-user authorisation.** Every query runs as the calling user via OAuth On-Behalf-Of — the connector cannot see workspaces or datasets the user doesn't already have Power BI access to. No privilege escalation.
- **Modern auth.** Certificate-based OAuth client auth; no long-lived client secrets in transit or at rest.
- **Tenant-scoped audit.** Every tool invocation, every OAuth handshake, every DAX query lands as a structured event in your Log Analytics with the calling user's identity and the resources touched.
- **Zero-ops install.** One required field — your admin email; every other setting defaults to a locked-down, single-tenant install (your tenant only, deny-by-default). ~10 minutes, no post-install scripts for the common case.
## What you can do with it
- "What were Q3 net sales by segment?"
- "Show me retention trends for the last 12 months."
- "Reconcile this number against management accounts."
- "Render a dashboard for the sales analysis."
- Custom analyses configured via the connector's `/admin` web UI.
## Read more
See the [documentation site](https://github.com/expecta-team/expecta-connector-docs) for install guide, architecture, security posture, and operations runbook.
## Support
Engineering support is provided directly by Expecta. Reach out at waddah.alhajar@expecta.io
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Sources
Publisher resources
2 linksLinked repositories
1 repoUnknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.