Skip to main content
The List License Subscriptions tool allows Neo Agent to query your marketplace provider for the subscriptions behind a specific license, showing subscription IDs, billing terms, commitment terms, and current seat counts.

​
What It Does

When enabled, the agent can:
  • List all provider subscriptions for a given license SKU
  • Show the marketplace subscription ID for each subscription
  • Show the billing term (payment frequency — e.g., Monthly, Annual) for each subscription
  • Show the commitment term (contract duration — e.g., Monthly, 1-Year) for each subscription
  • Show the marketplace seat quantity per subscription — the number of seats purchased/billed on that subscription record
  • Show the marketplace seat total — the sum of seats across all of the provider’s subscriptions for the SKU
  • Show the renewal date — the date the subscription’s current term ends — and whether it auto-renews
  • Return the SKU ID and SKU part number so the agent can line the marketplace records up with the tenant’s Microsoft 365 licenses
  • Identify which marketplace provider was queried (Pax8, D&H, Ingram Micro, Sherweb, TD SYNNEX ION, TD SYNNEX Stellr, OpenText Secure Cloud, or Microsoft Partner Center)

​
Finding the Marketplace Product

A Microsoft license and a marketplace product rarely share a name. Microsoft calls its CSP variant of Power BI Pro “Power BI Pro Dept” (POWER_BI_PRO_DEPT); Pax8 sells the same thing as “Power BI Pro”. Neo resolves the two in this order:
  1. By Microsoft SKU ID, where the marketplace publishes it. Pax8 records the Microsoft SKU on a product only where that field is set, and some Pax8 products leave it empty; Microsoft Partner Center returns it directly. Where the ID is there, Neo matches on it exactly. This is the reliable path: it does not depend on the two catalogs agreeing on a name.
  2. By product name, as a fallback. It runs only when no subscribed product publishes the requested SKU ID. A match on step 1 skips it. Sherweb, Ingram Micro, TD SYNNEX ION, TD SYNNEX Stellr and OpenText Secure Cloud always take this path; Pax8 takes it when none of the company’s products carry the ID.
Step 1 returns every subscribed product that carries the ID, so an annual and a monthly offer of the same license are both reported. A product with an empty mapping is a different case: if the company holds one offer with the SKU and a second offer without it, only the first is reported, and the marketplace seat total omits the second offer’s seats. Set the missing mapping in the Pax8 portal to bring it back into the count.
If a Pax8 product repeatedly fails to resolve, check its Microsoft SKU mapping in the Pax8 portal. A product with the correct Microsoft SKU is matched exactly and never depends on the name.

​
When nothing matches

Some Microsoft licenses have no marketplace product at all — free and promotional SKUs such as Power BI (free), Microsoft Power Automate Free, Windows Store for Business and Teams Exploratory are assigned by Microsoft and are not sold by any marketplace. When no product matches on Pax8, Sherweb, Ingram Micro, TD SYNNEX ION, TD SYNNEX Stellr, OpenText Secure Cloud or Microsoft Partner Center, the tool returns no subscriptions and a no_matching_product note, and does not fail. A reconciliation agent that goes through every license a tenant holds therefore continues past the free ones. On Pax8, Sherweb, Ingram Micro, TD SYNNEX ION and TD SYNNEX Stellr, the note says which Microsoft license was requested (name, SKU part number and SKU ID) and lists the marketplace products the company subscribes to. The list is capped at 30 names so it stays short enough for a technician note; above that, the message says how many products it left out and asks the technician to read the full catalog in the marketplace portal. The agent passes that on to a technician instead of ordering seats against a product it guessed at. On OpenText Secure Cloud, the note names the requested license and lists the customer’s Microsoft 365 products only; a customer with no current Microsoft 365 subscription gets a note that says so, with no product list. Read the list to decide which applies:
  • The right product is in the list under a different name → on Pax8, correct the product’s Microsoft SKU mapping. Sherweb, Ingram Micro, TD SYNNEX ION and TD SYNNEX Stellr publish no Microsoft SKU, so there is no mapping to correct — buy against the product you identified.
  • The message says products were left out → check the full catalog in the marketplace portal before you conclude the product is missing. An omitted name is not an absent product, and buying one you already own gives you a duplicate subscription.
  • The right product is missing → buy it in the marketplace portal, then re-run.
  • The license is a free Microsoft SKU → nothing to buy; assign it in Microsoft 365.
Microsoft Partner Center and D&H report a no-match differently. Partner Center’s note says only which SKU it could not find (No subscriptions with SKU <id> (<name>) found in Microsoft Partner Center) — no product list, so open the Partner Center catalogue yourself to see what the company holds. D&H does not yet have a technician-facing message for this case at all: the call fails and the agent reports the failure. On either provider, read the company’s subscriptions in the provider portal rather than expecting the capped list above.

​
Seat Counts and Reconciliation

The marketplace seat quantity on each subscription is an explicit seat count for that one subscription record — it is not a count of subscription records, and not the number of seats currently assigned to or used by end users. A single license SKU can have seats spread across several subscription records (or even several marketplace providers), so the marketplace seat total for a SKU can legitimately differ from the seat total Microsoft 365 reports for the same SKU. The agent reconciles the two using the returned SKU ID / SKU part number and treats each subscription record independently when purchasing or cancelling seats, rather than assuming the marketplace and Microsoft totals are identical.

​
Renewal Dates

The renewal date is the date the subscription’s current term ends, exactly as the marketplace reports it. If the subscription auto-renews, that is the date it renews; if it does not, that is the date it lapses. This is what lets an agent act only on subscriptions renewing inside a window — “reduce unused seats, but only within 7 days of renewal”, for example. Not every provider exposes it: Where a provider does not return a value, the field is empty and the agent treats it as unknown — not as “this subscription is not renewing”. An agent whose rules depend on the renewal date should say what to do when the date is unavailable (usually: leave the subscription alone and tell a technician). This tool reports what the marketplace knows. Microsoft publishes its own renewal date per subscription, which the Microsoft 365 tools read under Licensing — use that for SKUs bought outside your marketplace, or where the table above shows no renewal date. Ask for both when you want full coverage.

​
When It’s Used

This tool is called by the agent before it adds or removes license seats, so it can get the marketplace subscription ID for the target subscription. It’s auto-enabled as a dependency of Change License Seats.
You don’t need to enable this tool manually — it’s automatically enabled when you enable Change License Seats.
In a chat conversation the tool waits up to 60 seconds for the marketplace. When the marketplace is slower, the agent says so and tries again later, and nothing changes.

​
Billing Term vs Commitment Term

Microsoft’s New Commerce Experience (NCE) has multiple subscription types for each license. Two subscriptions can share the same billing term but differ in commitment: The commitment term is the key differentiator — it tells you whether a subscription is month-to-month (cancel anytime) or locked into an annual contract.

​
Example Output

For a company with both month-to-month and annual-commitment subscriptions for Microsoft 365 Business Basic: Here the marketplace seat total is 100 (80 + 20). The agent uses the subscription ID to target the correct subscription when purchasing or cancelling seats, and reconciles the marketplace seat total against the tenant’s Microsoft 365 seat count via the SKU part number.