Integration
Microsoft Partner Center in IDA: sold versus actually used
Licences sold are one thing, licences assigned another. IDA puts the two side by side - so it stands out what a customer pays for without using, and where licences are missing.
What IDA reads from Microsoft Partner Center
- Subscriptions and licence quantities per customer tenant
- Assigned licences from the tenant
- The tenant mapping to the IDA customer
What IDA does with it
- Utilisation per customer: sold against actually assigned
- Unused licences become visible - a basis for a conversation rather than a hunch
- The tenant mapping is only written with proof, never on the strength of a name match
Who it is for
Microsoft partners with CSP customers who want utilisation and estate in their own system.
Setup: A service account with read rights through delegated administration (GDAP); IDA deliberately manages with read-only access.
Every integration in IDA has its own switch. Turn it off and it disappears completely - including the columns, filters and reports that belong to it. You only see what you actually use.
Vendor website: Microsoft Partner Center. Microsoft Partner Center is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- Microsoft Graph - Licensing & CSP
- Crayon Cloud iQ - Licensing & CSP
Questions about the Microsoft Partner Center integration
Does IDA need full admin rights in the customer tenant?
No. Read rights are enough; the integration is explicitly built for that and rejects an over-privileged account.
How does IDA know which tenant belongs to which customer?
From a confirmed mapping. A foreign identifier is never written on the strength of a similar name - that ends with the wrong companys data being queried every day.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.