MarketplaceOrdering.Agreements

Name: MarketplaceOrdering.Agreements API
Brand: MarketplaceOrdering.Agreements
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth27 EndpointsREST

For Agents

Sign, cancel, and inspect Azure Marketplace plan agreements so deployments can proceed. Useful for automating marketplace consent before provisioning third-party software.

Connect the MarketplaceOrdering.Agreements to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MarketplaceOrdering.Agreements, 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 MarketplaceOrdering.Agreements API.

Retrieve the current marketplace agreement for a publisher, offer, and plan combination

Sign a marketplace agreement so the plan becomes deployable in the subscription

Cancel a previously signed marketplace agreement

List every signed marketplace agreement in a subscription for compliance review

GET STARTED

Start building with MarketplaceOrdering.Agreements API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for MarketplaceOrdering.Agreements, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for MarketplaceOrdering.Agreements, keeping it validated and agent-ready. The Azure Marketplace Ordering API manages the legal agreements that must be accepted before a marketplace plan can be deployed in a subscription. Use it to retrieve the current agreement for a publisher, offer, and plan combination, sign or cancel an agreement, and list every signed agreement in a subscription. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.

Use Cases

Patterns agents use MarketplaceOrdering.Agreements API for, with concrete tasks.

★ Automate marketplace agreement acceptance

Provisioning pipelines call this API before deploying any third-party marketplace VM or solution to ensure the legal terms have been accepted. The agent retrieves the current agreement for the publisher, offer, and plan, inspects the terms payload, and POSTs the sign endpoint when policy permits, allowing the downstream resource creation to succeed without a manual portal step.

GET /subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId} to fetch terms, then POST .../sign to accept.

Audit signed marketplace agreements

Compliance teams query the subscription-scoped list endpoint to inventory every accepted marketplace agreement and the plan, publisher, and timestamp behind it. The output drives quarterly reviews of which third-party publishers have legal commitments tied to the subscription, supporting renewal and cancellation decisions.

Call GET /subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements and emit a CSV of publisher, offer, plan, and acceptance timestamp.

Cancel an obsolete agreement

When a marketplace plan is no longer in use and the team wants to fully decommission its footprint, the agent calls the cancel endpoint to revoke the previously signed agreement. Existing deployments are unaffected, but new deployments of that plan in the subscription will need a fresh agreement before they can proceed.

POST /subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/cancel and verify with the matching GET that the agreement is no longer accepted.

Agent-driven deployment unblock

Through Jentic, an AI agent can intercept a marketplace deployment failure caused by a missing agreement, automatically retrieve and sign the agreement, and retry the deployment. The agent searches Jentic for 'sign azure marketplace agreement', loads the operation, and executes the sign call, all while Jentic injects the Azure AD bearer token at execution time.

Use Jentic search 'sign azure marketplace plan agreement', load MarketplaceAgreements_Sign, supply publisher, offer, and plan IDs, and execute.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for marketplaceordering.

METHOD

PATH

DESCRIPTION

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}

Get the current agreement for a plan

POST

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/sign

Sign a marketplace agreement

POST

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/cancel

Cancel a marketplace agreement

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements

List all signed agreements in a subscription

PUT

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/offerTypes/{offerType}/publishers/{publisherId}/offers/{offerId}/plans/{planId}/agreements/current

Create or update an agreement record

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}

Get the current agreement for a plan

POST

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/sign

Sign a marketplace agreement

POST

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/cancel

Cancel a marketplace agreement

GET

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements

List all signed agreements in a subscription

PUT

/subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/offerTypes/{offerType}/publishers/{publisherId}/offers/{offerId}/plans/{planId}/agreements/current

Why though Jentic?

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

Credential isolation

Azure AD client credentials are stored encrypted in the Jentic vault. Jentic exchanges them for a short-lived ARM-scoped bearer token at execution time so the agent only handles structured payloads.

Intent-based discovery

Agents search Jentic with intents like 'sign azure marketplace agreement' and Jentic returns the matching MarketplaceAgreements operation with its input schema.

Time to first call

Direct integration: 1-2 days to handle MSAL, the unusual offerType paths, and the sign or cancel POST patterns. Through Jentic: under an hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Marketplace RP Service

Curate which marketplace offers are admitted to a tenant private store.

Use Marketplace RP Service to control catalog visibility; use MarketplaceOrdering.Agreements to accept the legal terms before deployment.

Complementary

Compute Management Client

Provision Azure VMs from marketplace images once their agreements are signed.

Pair with MarketplaceOrdering.Agreements when deploying marketplace VM images that fail without a signed agreement.

Complementary

Subscription Client

Enumerate subscriptions that need marketplace agreements signed.

Use Subscription Client first to identify the subscription scope before signing agreements within it.

Alternative

Policy Client

Govern marketplace deployments via Azure Policy rather than agreement state.

Pick Policy when the goal is to block deployments by publisher; use this API when the goal is to accept terms so a deployment can succeed.

FAQs

Specific to using MarketplaceOrdering.Agreements API through Jentic.

Why is there no official OpenAPI spec for MarketplaceOrdering.Agreements?

Microsoft Azure does not publish a standalone OpenAPI specification for the marketplace ordering agreements API. Jentic generates and maintains this spec so that AI agents and developers can call MarketplaceOrdering.Agreements 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 Marketplace Ordering API use?

The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD application credentials are stored encrypted in the Jentic vault and exchanged for a short-lived bearer token at execution time.

Can I sign a marketplace agreement programmatically?

Yes. Call POST /subscriptions/{subscriptionId}/providers/Microsoft.MarketplaceOrdering/agreements/{publisherId}/offers/{offerId}/plans/{planId}/sign. The response confirms acceptance and the same agreement then satisfies subsequent deployments of that plan in the subscription.

What are the rate limits for the Marketplace Ordering API?

The endpoints inherit the standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Bulk sign or cancel calls should respect those headers and back off when remaining quota approaches zero.

How do I check if a marketplace agreement is signed through Jentic?

Search Jentic for 'get azure marketplace agreement', load MarketplaceAgreements_GetAgreement, supply publisher, offer, and plan IDs, and execute. The response includes an accepted boolean and signedDate that the agent can branch on.

Does cancelling an agreement affect existing deployments?

No. POST .../cancel revokes the agreement so new deployments of that plan require a fresh signature, but resources already provisioned under the previously signed agreement keep running. Decommission those resources separately through their resource provider APIs.

Is the Marketplace Ordering API free?

The control-plane endpoints themselves do not incur charges. Marketplace plans deployed under signed agreements bill against the publisher's terms in addition to standard Azure resource consumption charges.