Microsoft Azure Microsoft.Support
Browse all Azure APIs44
AI ReadinessFoundational (D)44/100
Agent-ready OpenAPI document · curated by JenticCRMCustomer Supportoauth214 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Open and update Microsoft Azure support tickets, post communications, and browse the support service and problem classification catalog. Covers 14 endpoints across services, problem classifications, support tickets, communications, and name availability checks.
Use for: I need to open an Azure support ticket for a virtual machine that will not start, Post a follow-up message on support ticket 12345 with new diagnostic logs, List all open support tickets in my Azure subscription, Get the catalog of Azure support services available for a billing issue
Not supported: Does not handle billing payment, customer-facing support tickets for your own product, or non-Azure incidents - use for opening and managing Microsoft Azure engineering support cases only.
Jentic publishes the only available OpenAPI specification for Microsoft.Support, keeping it validated and agent-ready. The Microsoft Azure Support Resource Provider lets customers create and manage Azure technical and billing support tickets entirely through code. The API exposes the catalog of Azure support services and problem classifications, lets agents file new tickets with severity and contact details, posts follow-up communications back into a ticket thread, and reads ticket state across a subscription. Ticket creation is gated on the subscription having an active support plan such as Developer, Standard, Professional Direct, or Premier.
Install Jentic One Beta
Connect the Microsoft.Support to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Microsoft.Support, 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%2Fmicrosoft-support" | 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%2Fmicrosoft-support" | 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 Microsoft.Support API.
Create technical, billing, quota, or subscription management support tickets
Post follow-up communications into an existing ticket thread
Update ticket severity, contact details, and status
Browse the Azure support service catalog and matching problem classifications
List all support tickets in a subscription and filter by status or creation date
Check whether a support ticket name or communication name is available
Retrieve the full conversation history for a single support ticket
Use Cases
Patterns agents use Microsoft.Support API for, with concrete tasks.
★ Programmatic Azure ticket creation
Operations teams that detect critical failures in their monitoring stack can open Azure support tickets without leaving their incident response workflow. The API requires an active support plan, a service identifier, a problem classification, contact details, and a severity. Tickets are typically acknowledged within minutes for critical severity on Premier plans and within four hours on Standard plans, removing the manual portal click-through that previously delayed escalation.
Create a technical support ticket for service Microsoft.Compute with problem classification VM Deployment, severity moderate, title VM web01 failed to provision, and primary contact engineer at example.com.
Two-way ticket communication automation
Customer support and DevOps teams attach diagnostic logs, screenshots, and reproduction steps to support tickets via the communications subresource. The API accepts a communication body and subject and posts it as a customer reply on the ticket thread. Reading the same subresource lets internal tooling pull Microsoft engineer responses directly into Slack, Teams, or a ticket aggregation system.
Post a communication on support ticket case-99887 with subject Updated logs and body containing the URL of a fresh log bundle uploaded to blob storage.
Service catalog discovery for ticket routing
Before opening a ticket, an agent can list Azure support services and their problem classifications to pick the most accurate routing target. The catalog returns service GUIDs and problem classification GUIDs that the API requires when creating a ticket, ensuring the case lands in the correct Microsoft engineering queue and reduces back-and-forth on misrouted tickets.
List Azure support services, find the entry for Virtual Machines running Linux, list its problem classifications, and return the GUID for the Cannot connect via SSH classification.
Agent-assisted incident escalation
AI agents can use Jentic to discover Microsoft.Support operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing the Azure REST docs. An on-call agent reading a paging alert can open a critical support ticket, attach the failure summary as an initial communication, and report the ticket number back to the on-call channel within seconds.
Search Jentic for create an azure support ticket, load the input schema, and execute it for a critical severity case against Microsoft.Network with the alert summary as the description.
Key Endpoints
14 endpoints — jentic publishes the only available openapi specification for microsoft.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}
Create a new Azure support ticket
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets
List support tickets in a subscription
PATCH
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}
Update an existing support ticket
GET
/providers/Microsoft.Support/services
List Azure support services
GET
/providers/Microsoft.Support/services/{serviceName}/problemClassifications
List problem classifications for a service
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Support/checkNameAvailability
Check support ticket name availability
PUT
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}
Create a new Azure support ticket
GET
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets
List support tickets in a subscription
PATCH
/subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName}
Update an existing support ticket
GET
/providers/Microsoft.Support/services
List Azure support services
GET
/providers/Microsoft.Support/services/{serviceName}/problemClassifications
List problem classifications for a service
POST
/subscriptions/{subscriptionId}/providers/Microsoft.Support/checkNameAvailability
Check support ticket name availability
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.
M
Microsoft.Support
- Foundational (D)44/100
72
Foundational Compliance63
Developer Experience & Jentic Compatibility21
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
72
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
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.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
21
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
85%
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 Microsoft.Support by hand means implementing Azure AD OAuth 2.0, minting an ARM-scoped bearer token for management.azure.com, resolving service and problem classification GUIDs from the catalog, and modelling the ticket and communication threading schema yourself. Through Jentic you install once, import Microsoft.Support from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
The API puts the subscription and support ticket name in the URL path, so a rule can pin your agent to reading and updating support tickets in one subscription and nothing else. You choose the operations it may call, so you can limit the agent to filing tickets and posting communications while updates such as changing severity or closing a ticket are not included unless you add them.
Credential isolation
Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'open an Azure support ticket' or 'list Azure support services', and Jentic returns the matching Microsoft.Support operation with its input schema so the agent supplies the service, problem classification, and severity and executes.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Microsoft.Support API through Jentic.
Why is there no official OpenAPI spec for Microsoft.Support?
Microsoft Azure does not publish an OpenAPI specification for the Microsoft.Support Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call Microsoft.Support 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 Microsoft Azure Support API use?
The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential.
Can I create a new support ticket through the Microsoft Azure Support API?
Yes, provided the subscription has an active Developer, Standard, Professional Direct, or Premier support plan. Call PUT /subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName} with a service ID, problem classification ID, severity, title, description, and contact details. Subscriptions without a paid support plan can only file billing and subscription management tickets.
What are the rate limits for the Microsoft Azure Support API?
The API follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations such as listing services or problem classifications are limited to 1200 requests per hour per subscription. Ticket creation is gated by both ARM throttling and the support plan tier, so most teams see no practical limit.
How do I post a communication on an existing ticket through Jentic?
Search Jentic for post azure support ticket communication, load the schema for PUT under supportTickets/{supportTicketName}/communications/{communicationName}, and execute it with the ticket name, communication name, subject, and body. Jentic handles the AAD token exchange and returns the new communication record.
Does the Microsoft Azure Support API allow closing a ticket?
Yes. PATCH /subscriptions/{subscriptionId}/providers/Microsoft.Support/supportTickets/{supportTicketName} with a status of Closed transitions the ticket to a closed state. The same endpoint accepts severity changes and updated contact details, so a single call can both downgrade severity and close the case.
Can I limit what my agent is allowed to do with the Microsoft Azure Support API?
Yes. Because you run Jentic One yourself, your own rules decide which Microsoft.Support operations and credentials the agent may use, and since the subscription and support ticket name sit in the URL path, a rule can pin the agent to reading and updating tickets in a single subscription and nothing else. You can allow it to file tickets and post communications while leaving out operations like changing severity or closing a ticket unless you add them. The stored Azure AD credential is exchanged for a short-lived, scoped bearer token at execution time, so the agent only ever acts within the operations you granted.
GET STARTED