Microsoft Azure AzureAnalysisServices
Browse all Azure APIs40
AI ReadinessFoundational (D-)40/100
Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligenceoauth216 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Provision, suspend, resume, and scale Azure Analysis Services tabular servers and inspect their SKUs and gateway state.
Use for: I need to provision an Azure Analysis Services server, Suspend an Analysis Services server to save cost, Resume a suspended Analysis Services server, List the SKUs available for an Analysis Services server
Not supported: Does not query tabular models, deploy model definitions, or process refresh - use for Analysis Services server lifecycle only.
Jentic publishes the only available OpenAPI specification for Azure Analysis Services, keeping it validated and agent-ready. The API provisions and lifecycle-manages Analysis Services servers - the SQL Server Analysis Services tabular engine running in Azure - letting agents create, suspend, resume, scale, and delete servers, list available SKUs, check name availability, and dissociate or query the on-premises gateway. It targets the Microsoft.AnalysisServices resource provider on Azure Resource Manager and is intended for BI infrastructure automation rather than for querying tabular models directly.
Install Jentic One Beta
Connect the AzureAnalysisServices to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AzureAnalysisServices, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazureanalysisservices" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazureanalysisservices" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AzureAnalysisServices API.
Provision an Azure Analysis Services tabular server in a region
Suspend a running server to stop billing without losing the model
Resume a suspended server when reporting workloads return
Scale a server up or down by patching its SKU
List all SKUs available for Analysis Services
Check that a proposed server name is available before creation
Dissociate or query the on-premises gateway attached to a server
Use Cases
Patterns agents use AzureAnalysisServices API for, with concrete tasks.
★ Cost-aware suspend and resume
Suspend an Azure Analysis Services server outside business hours and resume it before reporting workloads start. The POST /servers/{serverName}/suspend and /resume operations stop and restart compute without disturbing the deployed tabular model. Cuts costs significantly for workloads that only need to be online for part of the day.
POST /servers/{serverName}/suspend at 19:00 then /servers/{serverName}/resume at 07:00 on weekdays and verify the GET returns provisioningState=Succeeded
Provision a new tabular server
Create a new Azure Analysis Services server in a target region with a chosen SKU. The PUT /servers/{serverName} operation accepts the SKU tier, capacity, and admin members in a single call. The check-name-availability operation lets the workflow validate the proposed name before the create call.
POST /locations/{location}/checkNameAvailability with name=mybi-prod, then PUT /servers/mybi-prod with sku.name=S1 and verify provisioningState=Succeeded
Scale up before a heavy reporting day
Patch a running Analysis Services server to a larger SKU before a known peak (month-end close, fiscal report run) so query latency stays low under load. The PATCH /servers/{serverName} operation accepts the new SKU and applies it without dropping the model. Reverts to the smaller SKU after the peak with another PATCH.
PATCH /servers/{serverName} with sku.name=S2 capacity=2, wait for provisioningState=Succeeded, run the reporting workload, then PATCH back to S0
Inventory and SKU planning
Walk every Analysis Services server in a subscription and report its SKU and state, plus the SKUs available for a potential upgrade. The GET /servers/{serverName}/skus call returns available scaling options per server. Useful for capacity-planning and chargeback reporting.
Iterate every server under a subscription, GET its current sku and the per-server skus list, and emit a CSV of server name, current SKU, and upgrade options
Agent-driven BI infrastructure
Allow an AI agent to suspend, resume, or scale Analysis Services servers in response to a calendar event or workload signal without an operator hand-coding the long ARM URL. Through Jentic the agent searches by intent, loads the SKU schema, and executes the right operation. Removes a class of typos when constructing nested resource paths.
Search Jentic for 'suspend azure analysis services server', execute the POST against the named server, and confirm the operation status returns Succeeded
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for azure analysis services, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers
List servers in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Create or update a server
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Update server SKU or settings
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Delete a server
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/suspend
Suspend a server
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/resume
Resume a suspended server
POST
/subscriptions/{subscriptionId}/providers/Microsoft.AnalysisServices/locations/{location}/checkNameAvailability
Check whether a server name is available
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AnalysisServices/skus
List available SKUs
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers
List servers in a resource group
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Create or update a server
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Update server SKU or settings
DELETE
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}
Delete a server
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/suspend
Suspend a server
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.AnalysisServices/servers/{serverName}/resume
Resume a suspended server
POST
/subscriptions/{subscriptionId}/providers/Microsoft.AnalysisServices/locations/{location}/checkNameAvailability
Check whether a server name is available
GET
/subscriptions/{subscriptionId}/providers/Microsoft.AnalysisServices/skus
List available SKUs
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AzureAnalysisServices
- Foundational (D-)40/100
99
Foundational Compliance57
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
28%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
71%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Azure Analysis Services API by hand means registering an Azure AD app for OAuth2 bearer auth against management.azure.com, building the Microsoft.AnalysisServices server path, plumbing the SKU and admin body, and polling operationstatuses while a suspend, resume, or provision completes. Through Jentic you install once, import Azure Analysis Services from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The server sits in the URL path (/servers/{serverName}/suspend and /resume), so a rule can pin your agent to one server and let it suspend, resume, or scale only that server. You choose the operations it may call, so the DELETE that removes a server is not included unless you add it.
Credential isolation
Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'suspend an azure analysis services server' or 'scale a tabular server to a larger sku', and Jentic returns the matching Microsoft.AnalysisServices operation with its SKU and admin schema so the agent calls the right endpoint without memorising the ARM path.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AzureAnalysisServices API through Jentic.
Why is there no official OpenAPI spec for Azure Analysis Services?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure Analysis Services via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Azure Analysis Services API use?
The API uses Azure AD OAuth 2.0 with the implicit flow, scoped to user_impersonation against management.azure.com. Through Jentic, the bearer token is held in your Jentic One instance and exchanged for a scoped access token at execution time.
Can I suspend a server and resume it later through this API?
Yes. POST /servers/{serverName}/suspend stops compute without removing the model, and POST /servers/{serverName}/resume restarts it. Both are long-running operations that return 202 Accepted; track completion via the operationstatuses endpoint or Azure-AsyncOperation header.
What are the rate limits for this API?
Azure Resource Manager applies tenant-level throttling - typically 12,000 reads and 1,200 writes per hour per subscription. Server provisioning, suspend, and resume are long-running operations; poll /locations/{location}/operationstatuses/{operationId} for status.
How do I provision a server through Jentic?
Run pip install jentic, then search for 'create azure analysis services server'. Jentic returns the PUT /servers/{serverName} operation with the SKU and admin schema, and executes the call against the location and resource group you specify.
Does this API let me query the tabular model directly?
No. This API manages server lifecycle (create, scale, suspend, resume) only. To query a deployed tabular model, connect with the XMLA endpoint or the Analysis Services client libraries against the server's data plane.
Can I limit what my agent is allowed to do with the Azure Analysis Services API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which operations and credentials your agent may use. Since the server name sits in the URL path of operations like POST /servers/{serverName}/suspend and /resume, you can pin the agent to a single server and allow it to suspend, resume, or scale only that one. You choose the operations it may call, so the DELETE that removes a server is excluded unless you add it.
GET STARTED