ApivomApivom
Get Demo

Microsoft Partner Center API Connector

Microsoft Partner Center REST API for Cloud Solution Provider partners — customers, subscriptions, orders and carts, users and licences, invoices and reconciliation line items, Azure usage, service requests, agreements, webhooks and audit records — registered in Apivom Atlas as 196 routes for CSP direct and indirect partners.

What you can do

  • Customers: create, list and manage CSP customers, their users, directory roles, subscribed SKUs, verified domains and relationship requests (121 customer routes)
  • Subscriptions, orders and carts: 27 subscription routes incl. upgrades, transitions and transfers; orders, carts, offers, products and promotion eligibility
  • Billing: invoices, line items by product type, statements and receipts, estimates links, usage summaries and rate cards
  • Operations: service requests and incidents, agreements and templates, webhooks, audit records, fraud events, device batches and policies
  • 196 routes (127 read-only) on api.partnercenter.microsoft.com, documented in the AI integration guide (llms.txt)

Use cases

  • Customer and licence inventory in the CRM — Mirror CSP customers, their subscriptions and licence counts next to the account record so renewals and seat changes are visible where the account is managed.
  • Invoice reconciliation — Pull monthly invoices and reconciliation line items by product type into your billing system and match them to what each customer was charged.
  • Audit and change tracking — Read audit records and subscribe to Partner Center webhooks to log who changed which subscription, and when, across the partner tenant.

Partner Center is the portal and API through which Microsoft Cloud Solution Provider partners sell and operate Microsoft 365, Azure and Dynamics for their customers, and Apivom Atlas catalogues its REST surface — 196 routes, 127 of them read-only — from Microsoft's own reference, since Microsoft publishes no verified OpenAPI or Postman collection for it. The customer family covers the whole CSP relationship: create customers and relationship requests, manage their users, directory roles and licences, read subscribed SKUs and verified domains, and run the licence-based and usage-based subscription lifecycle with carts, orders, upgrades, transitions and transfers. The billing family returns invoices, reconciliation line items by product type, statements and receipts, usage summaries and rate cards; the operations family handles service requests and incidents, agreements, webhooks, audit records and device management. Authentication follows Microsoft's Secure Application Model: the caller holds the partner tenant's app registration and exchanges it for an Entra token. No Apivom product workflow uses Partner Center today — Apivom's existing partner-licensing automation is built on Autodesk — so the connector is available to CSP partners and distributors, with product workflows scoped per customer.

Authentication

Entra token for the CSP partner tenant: tenant id, app registration client id + secret, exchanged by the caller at login.microsoftonline.com/{tenantId}/oauth2/token (resource api.partnercenter.microsoft.com, Secure Application Model), sent as Bearer. Secret encrypted in your Iris tenant.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Which Partner Center account does this need?

An active Cloud Solution Provider enrolment (direct bill or indirect) with an app registration in the partner tenant set up for the Secure Application Model. National-cloud variants (21Vianet) use a different host and are not in this catalogue.

Is this the same as Autodesk Partner Center?

No. This is Microsoft's Partner Center for CSP partners. Autodesk's partner programme is covered by the separate Autodesk PWS integration, which Apivom products use in production today.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.