Microsoft Azure AzureAnalysisServices

Name: AzureAnalysisServices API
Brand: Azure Analysis Services
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligenceoauth216 EndpointsREST

For Agents

Provision, suspend, resume, and scale Azure Analysis Services tabular servers and inspect their SKUs and gateway state.

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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

GET STARTED

Start building with AzureAnalysisServices API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Azure AD OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens at execution time — service principal client secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'suspend azure analysis services server') and Jentic returns the matching Microsoft.AnalysisServices operation with its SKU and admin schema, so the agent does not need to memorise the long ARM resource path.

Time to first call

Direct ARM integration: 2-3 days for AAD app registration, async polling, and SKU plumbing. Through Jentic: under 1 hour — search, load, execute.

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 at https://app.jentic.com/sign-up.

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 the Jentic vault 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.

Microsoft Azure AzureAnalysisServices

Connect the AzureAnalysisServices to your agent

Capabilities

Start building with AzureAnalysisServices API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs