Application inventory
Collected application records, reports and scan history are stored locally. They are not uploaded as part of license activation.
Security and data handling
Understand where your data goes.
Your detailed application inventory stays on your server. Online features have separate, defined data flows.
Certificate connection
The collector uses the certificate prepared on your Windows server. Upload the public collector.cer to Entra and keep the private key protected locally.
Online licensing
Activation and renewal communicate tenant, device-linking and subscription information to the publisher licensing service. Microsoft sign-in is used to authorize activation.
Optional usage sharing
Off by default. If enabled, aggregate feature-page counts are linked to the licensed tenant. Inventory, report contents and credentials are excluded.
Support cases
Support sends the contact address, subject, description, app version and linked tenant information. Detailed inventory and logs are not attached automatically; share only appropriate information.
Software updates
The updater verifies signed releases before installing them. Publisher signing protects update integrity; review the current documentation for deployment and operating-system controls.
Review the current, detailed security overview.
This summary describes the product’s data flows. The detailed overview explains the validation scope, online service boundaries and operating responsibilities.
Read the detailed security overview ↗Ready to review your own tenant?
Check the requirements and follow the guided setup.