Aristo License Chargeback
Phoenix Halo · Intelligence & Research
Certification per Microsoft Marketplace.
Evidence tier Source Confirmed · 2 captures on record
What the publisher says
As described on Microsoft Marketplace.
The money to pay for AI is usually already in the Microsoft bill, pointed in the wrong direction. Every organization running Microsoft 365 Copilot pays for two kinds of idle seat — the ones somebody holds and never opens, and the ones nobody was ever given. Neither is visible on an invoice, because an invoice only knows what was bought.
Aristo License Chargeback counts both, from your own licence records, and turns them into the funding line for your AI programme — month after month, for a full year.
Show the rest of the publisher’s description (21 more lines)
The Frontier Firm Assessment is included
The engagement opens with the complete Aristo Frontier Firm Assessment: your Frontier score out of 100 (counted, never self-reported), Traffic Lights on every way you pay for AI, and the License Report. The assessment is not a separate purchase — it is the first thing that happens.
What you get, every month
- The License Report — every subscription you pay for: bought, assigned, and never assigned to anyone.
- A named reassignment plan — seat by seat, verified before it moves, approved by a sponsor in Microsoft Teams. Nothing moves automatically.
- Chargeback lights you define — each spending path watched against a floor you set, with the move already written when a light turns.
- Renewal counsel — a counted keep-or-release recommendation per seat, gathered before the renewal date so you walk in with evidence instead of a guess.
- The funding equation — idle spend set against what the AI programme costs, on one scale, so "who pays for this?" has an arithmetic answer.
- Board-ready exports, and a card in Microsoft Teams for the sponsors you name.
How it runs
- Day 0 — one read-only admin consent over your subscription list. Nothing is installed.
- Day 1 — the assessment lands, then the licence truth: idle seats named, the money counted, the plan attached.
- Every month — it re-runs itself. New joiners, new idle, a new plan to approve.
- Twelve months — a full budget cycle of counted chargeback, renewal counsel included.
Built for many tenants, starting with one
Consent is granted per tenant, so federated tenants, unfederated tenants and tenants in a different cloud are all counted the same way. Nothing depends on federation, and widening to the next tenant is a consent link rather than a project.
What exists today, and what a pilot builds
Ships today: the per-tenant layer — the counted License Report, the idle arithmetic and the reassignment plan, inside each tenant. The parent rollup and the multi-tenant fleet view do not exist yet; they are what a pilot builds. Better said now than found later.
Privacy by construction
Aristo reports org and team aggregates only. A team smaller than five people is never shown at all, and no person-level row ever leaves your tenant. Access is read-only throughout, and Aristo never stops or alters Microsoft billing — only Microsoft's own admin-centre spending limits do that.
See the finished report before you decide. It is published live on sample data at aristo.phoenixhalo.com.
Preview
2 images
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment · as of 2026-08-29
Plans and pricing as listed
1 listedSources
Publisher resources
1 linkLinked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.