Microsoft Azure Azure Advisor Management Client
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth215 EndpointsREST
For Agents
List Azure Advisor cost, performance, reliability, and security recommendations, suppress them per resource, and trigger fresh generation.
Use for: List all Advisor cost recommendations for subscription 1111-2222-3333-4444, Trigger a fresh Advisor recommendation generation for the current subscription, Suppress the right-size VM recommendation on resource vm-prod-01 for 30 days, Get Advisor metadata describing supported recommendation categories
Not supported: Does not directly remediate resources, change SKUs, or apply security fixes — use only to read, suppress, and refresh Advisor recommendations on Azure subscriptions.
Jentic publishes the only available OpenAPI specification for Azure Advisor Management Client, keeping it validated and agent-ready. Azure Advisor analyses subscription telemetry and returns personalised recommendations across cost, performance, reliability, and security. This API exposes operations to list and act on those recommendations, suppress noise on specific resources, manage subscription-level Advisor configurations, and trigger fresh recommendation generation on demand.
Install Jentic One Beta
Connect the Azure Advisor Management Client to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Advisor Management Client, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Azure Advisor Management Client API.
List Advisor recommendations filtered by category and resource scope
Trigger on-demand recommendation generation for a subscription
Suppress an Advisor recommendation on a specific resource for a fixed window
Retrieve Advisor metadata such as supported recommendation types
Read and update subscription-level Advisor configuration
Check the status of a queued recommendation generation request
Use Cases
Patterns agents use Azure Advisor Management Client API for, with concrete tasks.
★ Automated Cost Optimisation Reviews
FinOps teams pull Advisor cost recommendations weekly to identify underutilised VMs, idle databases, and reserved instance opportunities. GET /subscriptions/{subscriptionId}/providers/Microsoft.Advisor/recommendations returns categorised recommendations with impact and savings estimates so the agent can rank them and feed the top items into a Jira backlog.
List Advisor cost recommendations for subscription 1111-2222-3333-4444, sort by impact, and emit the top 10 with resource id and estimated savings
Recommendation Noise Suppression
Operators suppress Advisor recommendations that do not apply to a specific resource (for example, a VM intentionally over-provisioned for burst). The Suppressions endpoints allow a per-resource, time-bounded suppression so the recommendation stops appearing in dashboards without disabling Advisor globally.
Create a 30-day suppression for recommendation rec-xyz on resource /subscriptions/1111/resourceGroups/prod/providers/Microsoft.Compute/virtualMachines/vm-prod-01
On-Demand Refresh Before a Review
Advisor refreshes recommendations on its own schedule, but teams running a quarterly architecture review want fresh data immediately. POST /subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations queues a fresh run, and the matching GET endpoint returns its status so the workflow waits for completion before downloading.
Trigger Advisor recommendation generation, poll the status endpoint until it reports succeeded, then list the resulting recommendations
Agent-Driven Optimisation Loops
An AI agent running monthly optimisation can pull Advisor recommendations, file tickets for high-impact ones, and suppress the rest with reasons through Jentic. Intent search returns the recommendation list, suppression, and generation endpoints with their schemas; the Azure OAuth token is held in the credential vault so the agent never sees the service principal secret.
Search Jentic for 'list Azure Advisor recommendations', execute against the production subscription, and create issues for every high-impact security recommendation
Key Endpoints
15 endpoints — jentic publishes the only available openapi specification for azure advisor management client, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/recommendations
List Advisor recommendations
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations
Generate Advisor recommendations
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations/{operationId}
Get generation status
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/suppressions
List suppressions
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/configurations
Read Advisor configurations
GET
/providers/Microsoft.Advisor/metadata
List Advisor metadata
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/recommendations
List Advisor recommendations
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations
Generate Advisor recommendations
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations/{operationId}
Get generation status
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/suppressions
List suppressions
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Advisor/configurations
Read Advisor configurations
GET
/providers/Microsoft.Advisor/metadata
List Advisor metadata
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure Active Directory OAuth 2.0 tokens are minted and rotated inside the Jentic vault (MAXsystem). Service principal client secrets stay encrypted; agents call Microsoft.Advisor with a short-lived scoped token only.
Intent-based discovery
Agents search by intent (e.g., 'list Azure Advisor recommendations') and Jentic returns the matching Advisor operation with its input schema, so the agent does not need to know the long Microsoft.Advisor path layout.
Time to first call
Direct ARM integration: 1-3 days for AAD app registration, token acquisition, retry/throttling, and pagination. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Azure Advisor Management Client API through Jentic.
Why is there no official OpenAPI spec for Azure Advisor Management Client?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Azure Advisor Management Client 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 Advisor API use?
The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) on management.azure.com. Through Jentic, the AAD app secret is stored in the MAXsystem vault and exchanged for a short-lived bearer token per call.
Can I trigger a fresh Advisor scan from the API?
Yes. Call POST /subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations to queue a fresh run, then poll GET /subscriptions/{subscriptionId}/providers/Microsoft.Advisor/generateRecommendations/{operationId} until status is 'succeeded' before listing recommendations.
How do I hide an Advisor recommendation that does not apply to a resource?
Create a suppression against the resource via the Suppressions endpoints with a TTL. The recommendation stops appearing in /recommendations responses for the duration without disabling Advisor for the rest of the subscription.
What are the rate limits for the Azure Advisor API?
Azure Resource Manager applies subscription-level throttling. Recommendation list calls are typically polled per minute or less; if you receive HTTP 429, back off using the Retry-After header. The generateRecommendations endpoint is rate-limited more strictly because it triggers a backend run.
How do I file Jira tickets for top Advisor recommendations through Jentic?
Run pip install jentic, then search Jentic with 'list Azure Advisor recommendations'. Load the recommendations endpoint, execute against your subscription, and pipe the result into a Jentic search for 'create a Jira issue'. Both calls are credentialed via the vault, so the agent never holds raw secrets.
GET STARTED