A quiet activity report leaves a question for the owner: does this person still need the capability?
The report cannot answer that question alone.
Start by reconciling what the business purchased, what it assigned, which capabilities are enabled, and what activity the selected report observes. Keep those quantities separate before proposing a change.
This SaaS license utilization review is a proposed read-only method. It uses a fictional ten-seat subscription to show the arithmetic and decision work. It authorizes no account changes and makes no savings forecast.
Name the Population Before Counting It
Write the supplier, product, plan, subscription identifier, purchasing channel, and review owner at the top of the worksheet. Use an internal reference instead of exposing private billing details.
Then define the population. One subscription for one named product is a useful starting boundary. Do not add unlike plans together because the billing dashboard displays them on adjacent lines.
Define four quantities in plain language:
Purchased seats are the subscription quantity confirmed by the chosen subscription record at the review cutoff.
Assigned seats are purchased licenses allocated to identities in that same subscription snapshot.
Enabled capability records whether the particular service under review is available to an assigned identity in the snapshot.
Observed-active identities are identities with qualifying activity under a named report definition during a named window.
These definitions are the worksheet's conventions. Verify how the actual product names and measures each state. A license bundle can require more detailed capability rows than this example uses.
Use a business metric dictionary to keep the denominator, observation rule, and cutoff attached to any percentage. A bare label such as “utilization” conceals too many choices.
Record What the Report Can Observe
Microsoft's Microsoft 365 apps Active users documentation offers a scoped example. It lists seven-, thirty-, ninety-, and one-hundred-eighty-day trends. It describes reporting freshness in the twenty-four-to-forty-eight-hour range. Selecting a particular day has a separate table limit of up to twenty-eight days from the current date. See Microsoft's Active users report documentation, checked 2026.10.28.
The same documentation says user-specific details are hidden by default. Hidden identifiers create an identity-matching gap. They do not establish absence of activity.
Record the selected report, window, report refresh information, filters, and product scope before interpreting a result. This article does not recommend changing privacy settings to populate a worksheet.
For the fictional example, assume an authorized reviewer has a dated snapshot covering 2026.09.01 through 2026.09.30. The cutoff is 2026.10.03. The reviewer has already verified the allowed identity mapping in a controlled record.
Those invented dates illustrate the worksheet. They make no claim about an actual Microsoft export or tenant. Real reviews must preserve the report's displayed dates and known reporting limits.
Reconcile a Fictional Ten-Seat Subscription
The fictional subscription contains ten purchased seats for a single product. Each row below represents one unit of purchased capacity. Seat labels are worksheet references, not vendor-issued seat identifiers.
“Observed” means the fictional report contains qualifying activity for the assigned identity during the chosen window. “Not observed” leaves business need open. An unassigned seat has no identity to assess.
| Worksheet seat | Assigned identity | Capability enabled at cutoff | Activity in window | Owner context to verify |
|---|---|---|---|---|
| 01 | Role A | Yes | Observed | Current recurring work |
| 02 | Role B | Yes | Observed | Current recurring work |
| 03 | Role C | Yes | Observed | Current recurring work |
| 04 | Role D | Yes | Observed | Current recurring work |
| 05 | Role E | Yes | Observed | Current recurring work |
| 06 | Role F | Yes | Not observed | Approved leave reported by owner |
| 07 | Role G | Yes | Not observed | Seasonal task proposed for next period |
| 08 | Role H | No | Not observed | Required capability and enablement need review |
| 09 | Unassigned | Not applicable | Not applicable | Approved future starter proposed |
| 10 | Unassigned | Not applicable | Not applicable | No current purpose identified yet |
The snapshot reconciles as follows: ten purchased seats equal eight assigned seats plus two unassigned seats. Eight assigned seats equal five observed-active identities plus three identities with no observed activity.
Seven assigned identities have the selected capability enabled at the cutoff. One assigned identity has it disabled. Do not add that disabled identity as an eleventh seat. It already belongs to the eight assigned identities.
The five observed-active identities form a subset of the seven enabled identities in this invented snapshot. That relationship is stipulated for this example. A current enablement snapshot does not always describe the whole historical reporting window.
Calculate Three Ratios Without Overstating Them
Under this worksheet's definitions, the assignment ratio is eight divided by ten, or eighty percent.
Observed activity among assigned identities is five divided by eight, or sixty-two point five percent. Observed activity relative to purchased capacity is five divided by ten, or fifty percent.
Those last two ratios have different denominators. Label each explicitly. Neither ratio states how much work the product completed, whether a person performed well, or how much capacity the business should remove.
Do not calculate activity for unassigned seats as though those seats were people who failed to use the software. Record them as capacity without an assignment.
The arithmetic creates review questions. It does not settle the decision. The two unassigned seats need purpose checks. The three assigned identities without observed activity need context checks. The disabled capability needs a configuration and requirement check.
Keep the underlying row references with any summary. If a later correction changes an identity match, revise the affected total and note the reason. Preserve the original snapshot used for the earlier decision.
Ask the Owner About Future and Intermittent Work
Review the five candidate rows with the responsible owner. Ask about approved future starters, leave, seasonal work, dependencies, and required capabilities before deciding what each row means.
For Role F, the fictional owner confirms approved leave and a continuing need on return. Record the confirmation without copying private leave details into a broadly shared worksheet. The next review can follow the authorized return-planning process.
For Role G, the owner identifies a seasonal task but has not confirmed its next date. Keep the requirement unresolved until there is enough evidence to judge the needed access period.
For Role H, ask whether the disabled capability is intentional. A lack of activity could be consistent with a configuration boundary. Verify the required capability before classifying this row as excess capacity.
For seat 09, ask whether a future starter is approved, when access is required, and whether the proposed plan matches the role. An informal hiring possibility should remain a proposal.
For seat 10, “no purpose identified yet” means the owner review is incomplete. It becomes a quantity-review candidate only after the relevant owners confirm the absence of a current or approved requirement.
Check Workflow Dependencies Beyond the Activity Row
A narrow product report can leave parts of a workflow outside its scope. Ask which tasks the subscription supports, which outputs other people rely on, and what evidence covers those tasks.
Use the operator tech stack review to connect a seat question to the business process. Keep the review centered on required capability, rather than whether an identity looks busy.
For the fictional seasonal role, suppose the owner says a periodic document review needs access to historical work. Record that as an owner statement awaiting verification. Ask what must remain accessible, who needs it, and when.
Do not assume the answer requires the current license. Do not assume the answer permits removal either. Assign the product-specific access and continuity question to an authorized reviewer.
Keep shared workflow dependencies distinct from account sharing. A team depending on one person's output does not establish that multiple people may use that person's account. Verify the actual arrangement under the applicable terms.
Separate Assignment Changes From Quantity Changes
Unassigning a license and reducing purchased quantity describe different actions. Changing one number in the worksheet changes neither account state nor the bill.
Microsoft's business license quantity documentation requires available unassigned capacity before reducing quantity. It describes a limited reduction window for Microsoft Customer Agreement subscriptions and different handling for other billing arrangements. Reseller purchases also need channel-specific handling.
That product documentation does not authorize this fictional review to change an account. Record the applicable terms, eligibility, effective date, authorized administrator, and evidence needed before any real action.
Keep a candidate assignment change separate from a proposed quantity change in the decision record. A seat can be unassigned while purchased quantity remains unchanged. A proposed reduction can remain unavailable under the current commitment.
If an account-specific rule is unclear, record the question. Obtain an authorized clarification rather than inferring an invoice outcome from the activity ratio.
Build an Evidence-to-Decision Worksheet
Use a finding row for each distinct question. Preserve evidence gaps instead of replacing them with a confidence score.
For seat 10, assume the relevant owners now confirm no current or approved future requirement. Billing eligibility remains unknown.
| Candidate finding | Evidence gap | Fictional owner decision | Authorized next action |
|---|---|---|---|
| Role F has no observed activity | Continuing need initially unconfirmed | Retain assignment based on confirmed return requirement | Record requirement; no account change |
| Role G has no observed activity | Seasonal task date unconfirmed | Unresolved | Confirm task date and capability with process owner |
| Role H has disabled capability | Intended setup and role need unconfirmed | Unresolved | Ask authorized administrator for a read-only setup review |
| Seat 09 is unassigned | Starter approval initially missing | Reserve provisionally after owner confirms approved start | Record approval reference and revisit before access date |
| Seat 10 is unassigned | Billing eligibility unknown; need review completed | Candidate for quantity review | Obtain terms clarification; no quantity change authorized |
The fictional review therefore produces one retained assignment, one provisional capacity reservation, two unresolved assigned rows, and one quantity-review candidate. The five observed-active rows receive no proposed change in this exercise.
These categories reconcile to all ten worksheet seats: five unchanged, one retained, one reserved, two unresolved, and one candidate. “Candidate” describes work remaining. It is not a removal instruction.
Close With an Owned Decision
Give the worksheet a review date, evidence references, selected decisions, approver, and next action owners. Keep private identity mapping and personnel records in their controlled locations.
If a proposed change requires a broader trade-off, attach a business case decision memo. Explain the required capability, available alternatives, unresolved terms, and continuity conditions.
After any separately authorized action, verify the resulting account state and applicable billing evidence. Keep the confirmation distinct from the earlier recommendation. A review record is complete when it accurately records what was decided and what remains open.
Leave the account unchanged until the authorized owner decides.
Sources
- Microsoft Learn: Microsoft 365 apps Active users report. Reporting windows, freshness, selected-day table limit, and hidden user details. Checked 2026.10.28.
- Microsoft Learn: Buy or remove licenses for a Microsoft business subscription. Assignment prerequisite, billing-account distinctions, and purchasing-channel limits. Checked 2026.10.28.