canonical: https://jentic.com/apis/azure.com/ace-provisioning-managementpartner

# Microsoft Azure ACE Provisioning ManagementPartner

Jentic publishes the only available OpenAPI specification for ACE Provisioning ManagementPartner, keeping it validated and agent-ready. This API manages the linkage between an Azure customer subscription and a Microsoft Cloud Solution Provider partner identifier (MPN ID), exposing operations to register, retrieve, update, and delete the partner association under Microsoft.ManagementPartner. It is the surface a partner uses to claim Partner Admin Link or Partner Earned Credit visibility on a customer tenant.

## For AI agents

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

## Scope

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.

## Capabilities

- Register a Microsoft Partner Network identifier against the current Azure tenant
- Retrieve the partner record currently associated with the tenant
- Update an existing partner association to a different MPN ID
- Delete a partner association when the relationship ends
- List the operations the Microsoft.ManagementPartner provider supports
- Verify partner link status before claiming Partner Earned Credit

## Use cases

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

Example prompt: Register MPN ID 1234567 against the current tenant via PUT /providers/Microsoft.ManagementPartner/partners/1234567

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

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

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

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

## Key endpoints

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

## Key resources

- **Partners** — Get, register, update, and delete the Microsoft Partner identifier linked to a tenant
- **Operations** — List the operations exposed by the Microsoft.ManagementPartner provider

## Why Jentic

- **Setup:** Wiring this Microsoft.ManagementPartner client by hand means registering an Azure AD app, acquiring and refreshing OAuth 2.0 bearer tokens for management.azure.com, and handling Azure Resource Manager throttling yourself. Through Jentic you install once, import the ACE Provisioning ManagementPartner API from the API Directory, store the Azure credential once, and your agent calls it.
- **Permission scoping:** This provider puts the partner id in the URL path (/providers/Microsoft.ManagementPartner/partners/{partnerId}), so a rule can pin your agent to reading the partner record of record. You choose the operations it may call, so ones that change the link like registering or deleting a partner association are not included unless you add them.
- **Credential handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Azure Resource Management Client** — Manages subscriptions, resource groups, and tags that the partner link applies to.
- **Azure Policy Client** — Defines and assigns governance policies that may include partner-link requirements.
- **Azure Advisor Management Client** — Surfaces cost and operational recommendations that partners often act on for customers.

## FAQ

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