FinOps Copilot Seat Licences: One Cost View, One Usage View
A seat licence screen has to answer two questions, and they are asked by different people. Finance asks what the seats cost and what can be reclaimed. A team lead asks who is actually using them. ZopNight now answers each in its own view.
Cost Reports → AI Spend → Seat licences shows what seats cost and what can be reclaimed. AI Gateway → Seat licences shows who uses them. Typing in a price by hand is no longer offered, so the cost view reads its numbers from billing.
A split-question screen is one where each view is built around the single question its reader came with. The sections below show what each view holds and how a missing number is handled.
A Cost View for Reclaiming and a Usage View for Asking Who
| View | Where it lives | Question it answers |
|---|---|---|
| Cost | Cost Reports → AI Spend → Seat licences | What do seats cost, and what can be reclaimed? |
| Usage | AI Gateway → Seat licences | Who uses the seats? |
The seat list in either view can be sorted, filtered by status and searched, and the whole view is kept in the link, so a filtered list can be sent to a colleague as it is. Each status is explained on the page, and every app a seat uses is listed against it.
Usage Follows the Range You Pick
Usage covers Microsoft’s 7, 28 or 90 day windows, or any range up to 180 days. A fixed window is a choice made for you. A free range lets the person match the question to the review period, such as a quarter that ends on a date that is not a window boundary.
Behind the scenes, the 7 and 90 day usage reports and a 90 day tenant trend window were added, and a range read is cached for 5 minutes. That cache keeps repeated page loads from asking the store the same question again.
This works once the data exists. The 7 and 90 day figures arrive only after the first nightly metrics sync, so a newly connected account shows the 28 day view first. That is a timing limit, not a gap in the numbers. Earlier Copilot seat report fixes covered the trial versus renewal case.
A Missing Price Now Says Why
The price used to be an input a person could type. It now comes only from billing, and when it is missing the screen says why.
A typed price cannot be reconciled to anything. If it drifts from what an invoice says, the savings figure built on it is wrong in a way no one can trace. A price read from billing can be checked against the invoice.
With no billing access, a Grant access button shows the steps, and the permissions banner and drawer list the Billing account reader role without raising an alert. The old manual price routes, service and screen were removed. The table that held typed prices stays, unused.
