Modules
App Metering
Measure real usage of targeted applications and turn inventory into evidence.
Purpose
App Metering converts installation data into usage evidence. It measures launches, observed duration, last signal and usage frequency for explicitly targeted applications.
Practical workflow
Use a small, high-value list first: Adobe, Autodesk, Power BI Desktop, Visio, Project, Zoom or customer-specific business software.
Controls and validation
A valid signal combines observed period, target list, privacy level, workstation coverage and cost. Interpret low usage with business context.
Security and compliance
Wadyu is not an employee surveillance product. It does not read documents, capture screens or inspect file contents. It measures targeted application usage with the minimum signal required to support licence governance.
Common mistakes
Treat zero usage as an indicator, not an automatic removal instruction. Seasonality, leave, VIP profiles and rare critical tasks matter.
Current navigation
App Metering is organised into specialised views: Overview, Candidates, Applications, Users, Vendors and Collector coverage. This avoids one overloaded page and lets engineers move from ROI summary to application or user analysis without losing customer scope.
The main comparison joins Microsoft 365 entitlements with usage signals. Example: Microsoft 365 Business Premium grants Office app rights while the collector measures WINWORD, EXCEL, POWERPNT or OUTLOOK. Analysis must remain careful: no signal does not always mean no need, but it triggers a Reclaim review.