Microsoft Azure ACE Provisioning ManagementPartner

Name: ACE Provisioning ManagementPartner API
Brand: ACE Provisioning ManagementPartner
Availability: InStock

Browse all Azure APIs

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth26 Endpoints

Install Jentic One Beta

Connect the ACE Provisioning ManagementPartner to your agent

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

Step 1: 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

Step 2: 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 ACE Provisioning ManagementPartner API.

Retrieve the partner record currently associated with the tenant

Update an existing partner association to a different MPN ID

GET STARTED

Start building with ACE Provisioning ManagementPartner API

Explore with Jentic

View OpenAPI Document

For Agents

Register, look up, update, or remove the Microsoft Cloud Solution Provider partner identifier (MPN ID) linked to an Azure tenant.

Use for: Register MPN ID 1234567 as the partner of record on this Azure tenant, Check which Microsoft partner is currently linked to my subscription, Update the partner association to a new MPN ID after a reseller change, Remove the existing partner of record from the tenant

Not supported: Does not provision Azure resources, manage billing, or handle partner onboarding contracts - use only for binding and querying the MPN ID of record on an Azure tenant.

Use Cases

Patterns agents use ACE Provisioning ManagementPartner API for, with concrete tasks.

★ Claim Partner of Record on a Customer Tenant

When a Microsoft partner needs to be recognised on a customer's Azure tenant for Partner Admin Link, Partner Earned Credit, or co-sell attribution, they call PUT /providers/Microsoft.ManagementPartner/partners/{partnerId} with their MPN ID. The API binds that identifier to the tenant so downstream Azure billing and partner attribution systems see the relationship.

Audit Existing Partner Linkage

Operations and finance teams periodically audit which Microsoft partner is recognised on each Azure tenant to validate billing attribution and renewal contacts. GET /providers/Microsoft.ManagementPartner/partners returns the active partner record so reporting pipelines can flag missing or stale links across a tenant fleet.

Retrieve the active partner record for the tenant and report the MPN ID, state, and last update timestamp

Reseller Transition Cleanup

When a customer changes resellers, the outgoing partner association must be removed and the incoming one registered to keep Partner Earned Credit aligned. The DELETE and PUT operations on /providers/Microsoft.ManagementPartner/partners/{partnerId} make this a two-step transactional change instead of a manual portal task.

Delete partner record 7654321 and register replacement MPN ID 1234567 in a single workflow

Agent-Driven Partner Compliance Checks

An AI agent running tenant compliance reviews can confirm that every customer subscription has the correct partner link before billing close. Through Jentic, the agent searches for 'check Microsoft partner link', loads the GET schema, and returns the MPN ID per tenant without leaving the conversation. The Azure OAuth token is held in the credential vault.

Search Jentic for 'check Microsoft partner link', load GET /providers/Microsoft.ManagementPartner/partners, and return the linked MPN ID for the tenant

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for ace provisioning managementpartner, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/providers/Microsoft.ManagementPartner/partners

Get the active partner record

GET

/providers/Microsoft.ManagementPartner/partners/{partnerId}

Get a specific partner by id

GET

/providers/Microsoft.ManagementPartner/operations

List provider operations

GET

/providers/Microsoft.ManagementPartner/partners

Get the active partner record

GET

/providers/Microsoft.ManagementPartner/partners/{partnerId}

Get a specific partner by id

GET

/providers/Microsoft.ManagementPartner/operations

List provider operations

Why Jentic?

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

Credential isolation

Your Azure Active Directory credential is stored once, encrypted, by your own Jentic One instance, which mints short-lived scoped bearer tokens at execution time. The service principal secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check Microsoft partner link' or 'register a partner ID on an Azure tenant', and Jentic returns the matching ManagementPartner operation with its input schema so the agent skips the Azure REST docs.

Time to first call

FAQs

Specific to using ACE Provisioning ManagementPartner API through Jentic.

Why is there no official OpenAPI spec for ACE Provisioning ManagementPartner?

Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ACE Provisioning ManagementPartner 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 ACE Provisioning ManagementPartner API use?

The API uses Azure Active Directory OAuth 2.0 bearer tokens (the azure_auth scheme) sent in the Authorization header. Jentic stores the service principal credential in your Jentic One instance and mints scoped tokens at execution time, so agents never see the raw secret.

Can I register an MPN ID against an Azure tenant with this API?

Yes. Use PUT /providers/Microsoft.ManagementPartner/partners/{partnerId} where partnerId is your Microsoft Partner Network identifier. The tenant inherits Partner Admin Link visibility once the registration succeeds.

How do I check the current partner of record for a tenant?

Call GET /providers/Microsoft.ManagementPartner/partners. The response contains the active partner record including the MPN ID and state, which is the authoritative source for Partner Earned Credit eligibility.

What are the rate limits for this API?

Azure Resource Manager applies standard subscription throttling; this provider sees low call volume in practice because partner links rarely change. If you receive HTTP 429, honour the Retry-After header before retrying.

How do I audit partner links across many tenants through Jentic?

Run pip install jentic, then search Jentic with 'check Microsoft partner link'. Jentic returns GET /providers/Microsoft.ManagementPartner/partners with its input schema. Loop your tenant list and execute per-tenant; the OAuth token is resolved from the vault automatically.

Can I limit what my agent is allowed to do with the ACE Provisioning ManagementPartner API?

Yes. Because you run Jentic One yourself, your own rules decide which of this provider's operations the agent may call, so you can allow read-only access to the partner record through GET /providers/Microsoft.ManagementPartner/partners while withholding the operations that change the link. That means registering a partner with PUT or removing one with DELETE stays out of the agent's reach unless you explicitly add it. Since the partner id sits in the URL path, a rule can pin the agent to a specific partner record rather than the whole provider.