Quick start
Deploy a first Wadyu customer and obtain a reliable first ROI signal without skipping the security steps.
Product documentation
Wadyu Docs
Wadyu documentation centralises deployment guides, functional modules, security rules, production operations and MSP governance arguments.
Customer tenant onboarding
Connect a Microsoft 365 customer tenant to Wadyu while keeping the relationship strictly scoped to the current MSP.
Intune collector
Deploy the Wadyu App Metering collector through Intune Proactive Remediation.
Script Builder
Configure the collection profile, privacy level, discovery mode, catalogue targets and collector command.
Security
Understand tenant isolation, encryption, sessions, collector keys, CSP and production controls.
Troubleshooting
Diagnose visible Wadyu issues through scope, Microsoft consent, collector activity and permissions.
Purpose
Wadyu answers a simple question that native administration tools rarely cover: are paid licences actually used? Intune shows what is installed. Wadyu shows what is used. The difference is what turns a technical inventory into a financial and governance decision.
Practical workflow
The documentation surface is intentionally separated from app.wadyu.tech. It is static, public, does not carry Wadyu application sessions and does not proxy the API. The authenticated MSP console remains the only place for customer data, secrets and operational actions.
Controls and validation
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.
Security and compliance
Start with one pilot customer, a short list of expensive applications, a controlled Intune group and a clearly documented observation window. Expand only after the consent flow, collector, costs, reports and reclaim decisions have been validated end to end.
Common mistakes
Client secrets, Graph tokens, MSAL caches, webhooks and collector keys must never be exposed in documentation, screenshots, exports or support messages.