@bijectionhq/connectors/azure-analysis-services entrypoint to declare Azure Analysis Services resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Named model query
xmla: Typed DAX, MDX or schema discovery through the customer’s ADOMD.NET bridge
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:azure-analysis-services/query/xmla/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: azure-analysis-services. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Verification scope
Each evidence category has independent scope. A matching recorded pass applies only to its exact artifacts and configuration. Installed connections report their own identity, authority and current status.
Provider guidance
azureAnalysisServices.query.xmla({ query, maxRows? }) reads a named DAX,
MDX or schema-discovery query through the customer’s
ADOMD.NET bridge.
Bind its HTTPS root as endpoint and install the bridge bearer with
azureAnalysisServices.credential(name).
The customer configures the bridge’s fixed asazure:// server, catalog and
Entra identity. Microsoft documents ADOMD.NET connectivity
and service-principal connection strings.
Use adapters/xmla/appsettings.azure-analysis-services.example.json as a
configuration template, and supply its connection string and bearer through
the customer’s secret provider. The HTTP caller supplies only a query name;
it cannot choose another server, catalog, role, effective user or query text.
Native acquisition retains the original query ID and sealed typed CSV.
Integer/decimal text, null versus empty text, binary and temporal values retain
the bridge’s exact type tags. A failed or expired session never starts a
replacement query. Results are bounded observations keyed by session and row
index, without CDC or complete-population coverage. Larger transformations use
external Compute and Dataset publication.
The shared bridge’s protocol fixtures and controlled-reader lifecycle checks
are separate from live Azure Analysis Services qualification. No Azure server
authentication, cancellation or query execution is established by these fixtures.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:312df597437fd0bd236f3d409990aede65071f793d1110f86a7a09838be9569c.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.