Microsoft Azure ACE Provisioning ManagementPartner
Browse all Azure APIs56
AI ReadinessFoundational (C)56/100
Agent-ready OpenAPI document · curated by JenticCloud InfrastructureComputeoauth26 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
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.
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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Face-provisioning-managementpartner" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Face-provisioning-managementpartner" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
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.
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.
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
ACE Provisioning ManagementPartner
- Foundational (C)56/100
73
Foundational Compliance61
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience94
Agent Usability35
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
89%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
67%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
35
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
35%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 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.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED