Notifications
Clear all
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.
NHIMG editorial — based on content published by JumpCloud: Microsoft 365 and Adobe desktop discovery with app usage tracking
Questions worth separating out
Q: How should teams decide whether an expensive software licence is still justified?
A: Teams should base licence renewal on actual application use, not on whether the software is installed.
Q: Why do installed apps create poor evidence for software spend decisions?
A: Installed apps create poor evidence because many suites are deployed broadly, auto-launch at startup, or remain idle in the background.
Q: What breaks when teams treat a software suite as a single entitlement?
A: What breaks is precision.
Practitioner guidance
- Build renewal decisions on observed app use Require app-level usage evidence before renewing Microsoft 365 or Adobe top-tier licences.
- Separate inventory from engagement reporting Report installed software and active software as different governance metrics.
- Use component-level recertification for bundled suites Review Microsoft 365 and Adobe at the individual application level instead of treating each suite as one entitlement.
What's in the full article
JumpCloud's full how-to covers the operational detail this post intentionally leaves for the source:
- Step-by-step reporting workflow for identifying users with premium suites installed but not actively opened
- Operational examples for distinguishing foreground use from background app activity on managed endpoints
- Practical downgrade paths from full suites to web-only or single-app licences based on observed usage
- Admin-level detail on what the JumpCloud Agent tracks and what it does not capture
👉 Read JumpCloud's guide to app-level Microsoft 365 and Adobe usage tracking →
App-level usage tracking: what it means for SaaS license governance?
Explore further
13/06/2026 12:12 am
Software spend governance fails when installation is mistaken for entitlement value. The article exposes a familiar control weakness: organisations renew expensive suites because they can see the software, not because they can prove the software is used. That is not a tooling gap alone, it is a governance gap in how value is measured. Practitioners should treat app usage evidence as part of entitlement validation, not as a nice-to-have telemetry feed.
A few things that frame the scale:
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to The State of Secrets in AppSec.
- Organisations maintain an average of 6 distinct secrets manager instances, creating fragmentation that undermines centralised control, according to The State of Secrets in AppSec.
A question worth separating out:
Q: Who should own app usage-based licence governance in an organisation?
A: Ownership should be shared across IAM, endpoint management, and finance, with one team accountable for the policy and another for the usage data. The programme works best when entitlement reviews, cost controls, and device telemetry are aligned instead of managed as separate processes.
👉 Read our full editorial: Software spend governance needs app-level usage data, not install counts
