Webhook events
Microsoft notifies Valedo about subscription changes (subscribe, change plan, renew, suspend, reinstate, unsubscribe). Valedo stores each event, confirms it with Microsoft before acting, and processes it in the background. Seat-quantity changes are rejected because this offer has no seats. The webhook event log shows every event and its outcome; Microsoft retries failed deliveries for up to eight hours. A daily reconciliation compares Valedo’s subscriptions with Marketplace and corrects drift. Mismatches raise an alert.Background jobs
The operations view (
Valedo.Publisher.Admin) shows job runs, dead-letter queues with replay, Microsoft Graph throttling, and the purge queue.
Tenant purge
After a customer cancels, Valedo keeps working during a 30-day transition (the customer can extend it once) and keeps the data retrievable for at least 30 more days; thentenant-purge deletes it and writes an erasure record. Billing and audit records that the law requires are kept. This follows the EU Data Act; the design is in README §4.8 (planned). You can extend a transition from Licensing with a reason when a switch can’t finish in time.
Support access
Customers decide whether Valedo support can see their templates and rules. A customer admin grants time-limited support access in the Admin Portal. Under an active grant,Valedo.Publisher.Support can view (not edit) that tenant’s templates and rules. Every view is audited and visible to the customer.
Audit
Publisher-side actions (overrides, re-emits, replays, support views) are written to an immutable publisher audit log, visible toValedo.Publisher.Admin.