Start
Quick start
Deploy a first Wadyu customer and obtain a reliable first ROI signal without skipping the security steps.
Purpose
A successful first deployment follows the same sequence every time: secure the MSP sign-in, onboard one customer tenant, add real costs, configure a targeted profile, deploy the collector to a pilot group, observe data for several days and then qualify reclaim candidates.
Practical workflow
Use app.wadyu.tech over HTTPS, confirm MSP SSO is tenant-scoped, create at least one owner/admin user and keep Microsoft placeholders out of production environment files. On the customer side, confirm that the account used for consent can grant the required Microsoft permissions.
Controls and validation
A good first report includes observation period, applications, cost assumptions, candidates, exceptions and next action. Do not present a raw dashboard as a customer deliverable.
Security and compliance
Client secrets, Graph tokens, MSAL caches, webhooks and collector keys must never be exposed in documentation, screenshots, exports or support messages.
Common mistakes
Connecting many tenants before the pilot is validated creates support noise. Deploying App Metering too broadly before confirming the collector key, Intune targeting and cost model creates weak evidence.