Azure Addons Resource Provider

Name: Azure Addons Resource Provider API
Brand: Azure Addons Resource Provider
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth25 EndpointsREST

For Agents

Manage Canonical support plan addons attached to an Azure subscription, including listing available plan types and creating, retrieving, or deleting active plans. Supports the Microsoft.Addons resource provider control plane.

Connect the Azure Addons Resource Provider to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Azure Addons Resource Provider, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Azure Addons Resource Provider API.

List the Canonical support plan types available to an Azure subscription

Retrieve the current support plan assignment for a given provider and plan name

Create or update a Canonical support plan assignment in a subscription

Delete an active Canonical support plan from a subscription

GET STARTED

Start building with Azure Addons Resource Provider API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Azure Addons Resource Provider, keeping it validated and agent-ready.

The Azure Addons Resource Provider API manages Canonical Ubuntu Advantage support plans purchased through Azure as a third-party addon. It exposes the Microsoft.Addons resource provider operations for listing available support plan types, retrieving the current state of a plan in a subscription, and creating, updating, or deleting plan assignments. This is a control-plane API for governing third-party support entitlements alongside other Azure resources.

Use Cases

Patterns agents use Azure Addons Resource Provider API for, with concrete tasks.

★ Provision Canonical Ubuntu Advantage Support

Attach a Canonical Ubuntu Advantage support plan to an Azure subscription so that Ubuntu VMs running in that subscription receive Canonical-provided patching, kernel livepatch, and 24/7 support entitlements. The Addons Resource Provider exposes a single PUT to assign Essential or Standard plan types under the Canonical support provider, callable from infrastructure-as-code or an agent. Provisioning takes seconds; the plan then applies to all eligible Ubuntu workloads in the subscription.

Create a Canonical support plan with planTypeName=Standard under providerName=Canonical for subscription 1111-2222 via PUT /subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/Canonical/supportPlanTypes/Standard.

Audit Active Third-Party Support Entitlements

Read which Canonical support plans are currently assigned across a portfolio of Azure subscriptions to verify entitlement coverage during renewals or compliance reviews. The API returns the plan resource with its provisioning state so finance and operations teams can reconcile billing line items against active subscriptions. A single GET per subscription is enough to enumerate the assignment.

Retrieve the current Canonical Standard plan via GET /subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/Canonical/supportPlanTypes/Standard and report its provisioningState.

Deprovision Unused Support Plans

Cancel Canonical support plans on subscriptions that no longer run Ubuntu workloads to stop ongoing charges. The DELETE operation on the plan resource removes the assignment cleanly through the Microsoft.Addons resource provider, letting cost-management pipelines reclaim spend without portal access. This is typically driven by a tagging or usage report rather than ad-hoc human action.

Delete an unused Canonical Essential plan via DELETE /subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/Canonical/supportPlanTypes/Essential.

Agent-Driven Subscription Onboarding

When a Jentic agent provisions a new Azure landing zone for Ubuntu workloads, it calls the Addons Resource Provider as part of the bootstrap sequence to attach a Canonical support plan automatically. The agent enumerates available plan types via Operations_List, then issues the matching SupportPlanTypes_CreateOrUpdate call. This removes a manual portal step from every new subscription handoff.

List Microsoft.Addons operations, identify the SupportPlanTypes_CreateOrUpdate operation, and provision a Canonical Essential plan on the newly created subscription.

Key Endpoints

5 endpoints — the azure addons resource provider api manages canonical ubuntu advantage support plans purchased through azure as a third-party addon.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.Addons/operations

List available Microsoft.Addons operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes

List Canonical support plans for the subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Get a specific support plan assignment

PUT

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Create or update a support plan assignment

DELETE

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Delete a support plan assignment

GET

/providers/Microsoft.Addons/operations

List available Microsoft.Addons operations

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes

List Canonical support plans for the subscription

GET

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Get a specific support plan assignment

PUT

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Create or update a support plan assignment

DELETE

/subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/{providerName}/supportPlanTypes/{planTypeName}

Why though Jentic?

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

Credential isolation

Azure AD service principal credentials and tenant IDs are stored encrypted in the Jentic MAXsystem vault. The agent calls Microsoft.Addons endpoints with a scoped bearer token issued just-in-time, so secrets never leak into prompts, logs, or agent memory.

Intent-based discovery

Agents query Jentic with intents like "add canonical support plan to azure subscription" and Jentic returns the matching SupportPlanTypes operation with its full request schema, removing the need to navigate ARM provider docs.

Time to first call

Direct integration: about a day for AAD app registration, ARM token caching, and CreateOrUpdate polling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Microsoft Support

Opens and tracks Microsoft-side support tickets, complementary to third-party Canonical plans.

Use when the agent needs to file or query Microsoft support tickets rather than manage Canonical plan entitlements.

Complementary

Azure Consumption Management

Reports usage and charges that include Canonical addon line items.

Pair with this API when reconciling addon billing or attributing support-plan spend to subscriptions.

Alternative

Azure Cost Management

Cost reporting and budget control surface that surfaces addon spend at a portfolio level.

Choose this when the goal is cross-subscription cost visibility instead of plan provisioning.

FAQs

Specific to using Azure Addons Resource Provider API through Jentic.

What authentication does the Azure Addons Resource Provider API use?

Azure Active Directory OAuth 2.0 via the azure_auth scheme with the user_impersonation scope on https://management.azure.com/. Through Jentic, AAD client credentials sit in the MAXsystem vault and the agent receives a bearer token at execution time, never a raw secret.

Can I provision a Canonical support plan with this API?

Yes. Issue PUT /subscriptions/{subscriptionId}/providers/Microsoft.Addons/supportProviders/Canonical/supportPlanTypes/{planTypeName} with planTypeName set to Essential or Standard. The API returns the plan resource with its provisioningState once accepted.

What are the rate limits for the Azure Addons Resource Provider API?

Calls share Azure Resource Manager subscription throttling, typically 12,000 reads and 1,200 writes per hour per subscription. Honour 429 responses and the Retry-After header; the spec does not declare per-endpoint quotas.

How do I add a Canonical support plan through Jentic?

Search Jentic for "add canonical support plan azure", load the schema for SupportPlanTypes_CreateOrUpdate, then execute with subscriptionId, providerName=Canonical, and planTypeName. Sign up at https://app.jentic.com/sign-up to get an API key.

Which support providers are supported?

The 2017-05-15 spec only models Canonical (Ubuntu Advantage) as a support provider. Other vendors are not addressable through this resource provider, even though the path templates accept a {providerName} segment.

Does this API affect billing?

Yes. Creating a support plan via PUT enrols the subscription in the chosen Canonical plan, which generates monthly charges visible in Azure Cost Management. Deleting the plan stops future charges; consult the Marketplace agreement for proration rules.