canonical: https://jentic.com/apis/azure.com/microsoft-support

# Microsoft Azure Microsoft.Support

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Services** — Azure service catalog used to scope a support ticket to a specific Microsoft service such as Virtual Machines or SQL Database.
- **Problem Classifications** — Subcategories of issues under each service used to route tickets to the correct support engineering team.
- **Support Tickets** — Top-level support case resource with severity, contact details, status, and attached problem classification.
- **Communications** — Threaded follow-up messages posted by the customer or Microsoft engineers on an existing ticket.

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Microsoft Resource Health** — Reports the platform health of Azure resources that may motivate opening a support ticket.
- **Azure Advisor** — Surfaces Azure best-practice recommendations that can be addressed without opening a support case.
- **Zendesk Support** — Third-party customer support ticketing for non-Azure issues.

## FAQ

### 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.