Microsoft Azure MarketplaceOrdering.Agreements

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Microsoft Azure Marketplace Ordering API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, so you can grant it just the read (get and list agreements) and sign operations while leaving out cancelling an agreement entirely. Since the subscription, publisher, offer, and plan all sit in the request path, a rule can pin the agent to a specific plan and refuse anything outside it. Your Azure AD credential stays with your instance and is exchanged for a short-lived token only at execution time, never entering the agent's prompt or logs.