Topic starter
12/06/2026 9:50 pm
TL;DR: Install counts alone are masking software spend waste, because leadership cannot tell whether users actually open Microsoft 365 or Adobe apps before renewal decisions, according to JumpCloud. App-level discovery and foreground usage tracking shift license management from guesswork to measurable governance, and that matters wherever SaaS cost control depends on real adoption.
Editorial analysis by NHI Mgmt Group, based on content published by JumpCloud: “How to Spot and Reclaim Wasted Microsoft 365 and Adobe Licenses”.
Key questions
Q: How should teams govern SaaS licences when installation data does not show real use?
A: Treat install counts as discovery only and require usage evidence before renewals, tier changes, or budget approvals.
Q: Why do installed desktop apps create bad renewal decisions for software spend?
A: Because an installed app can look productive even when it is never opened or is only present in the background.
Q: What are the signs that SaaS spend controls are failing?
A: The most common signs are duplicate tools for the same use case, licences that remain unassigned after demand drops, and subscriptions that renew after the team stops using them.
Practitioner guidance
- Define app-level usage as the renewal signal Base Microsoft 365 and Adobe licence reviews on app open behaviour, not on whether the suite is installed on a device.
- Separate foreground use from background presence Use foreground activity to distinguish real work from apps that launch at startup or sit open without user interaction.
- Re-tier users by actual app dependence Move people who only use Outlook, Acrobat Pro, or a single desktop app to web-only or single-app plans where the licence model allows it.
Bottom line: Installed software is not the same as active software, and treating those signals as equivalent leads to waste in expensive suite licensing.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
13/06/2026 12:12 am
App-level usage data is the missing control in software spend governance: installation inventory tells you what exists, while usage telemetry tells you what is actually consuming budget. Suite licensing becomes inefficient when those two signals are collapsed into one, because procurement assumes value where none may exist. The practical consequence is that governance must move from presence-based reporting to consumption-based entitlement review.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: When should organisations move users from full suite licences to lower tiers?
A: Do it when app-level usage shows that the user only needs a web version or a single application such as Outlook or Acrobat Pro. The right trigger is sustained low engagement with the rest of the suite, not the presence of the software on the device. That is how spend governance becomes operational instead of speculative.
👉 Read our full editorial: Software spend governance needs app-level usage data, not install counts
This post was modified 6 days ago by NHI Mgmt Group