End User License Agreement

1. License grant

[Legal review required: entity name] grants the customer a non-exclusive, non-transferable license to install and run the software on infrastructure the customer controls, for the tenant(s) and term stated in the order, subject to a valid license key or lease. [Legal review required: seat, tenant and deployment scope language]

2. Restrictions

The customer may not redistribute, sublicense or offer the software as a service to third parties. The customer may not reverse engineer, decompile or disassemble the software, and may not remove, disable, circumvent or tamper with its license enforcement, its license data or its update verification, except to the extent applicable law expressly permits despite this restriction. [Legal review required: jurisdiction-specific wording]

3. Customer data

All data the software collects from the customer tenant is stored in the customer database and remains the customer's property. The vendor does not receive it. The software sends the vendor only the license and update information described in section 4.

4. License validation

The software validates its license online once a day; it has no offline mode. If the license cannot be validated, for any reason including the vendor platform being unreachable from the customer's network, the software stops scanning and stops receiving updates when its current lease ends, about 30 hours after the last successful validation. Information already collected remains available to the customer.

The license covers a number of licensed Microsoft 365 users in the customer's tenant. If the tenant has more licensed users than the license covers, the software says so, and if the license is not upgraded within 5 days, or the period stated in the order, the software stops scanning and stops producing reports and exports of the collected information until the license is upgraded. Information already collected remains viewable in the software.

Validation sends the installation's random instance id, the Microsoft 365 tenant id, the installed component versions, the license key or current lease token, and the number of licensed users in the tenant (a single number, never a list of people). Update checks send the same versions and lease. The software does not send the customer's permissions, users, groups, sites, files or audit records. [Legal review required: remedies when validation fails or the tenant exceeds its licensed users]

5. Updates

Updates are delivered as signed packages and are checked against the vendor's signature before they are installed; only versions newer than the installed one are installed automatically. When the software is set up, an administrator chooses whether it installs updates by itself. If they choose so, it installs new versions during a weekly update window the customer configures, which is Sunday 02:00 to 06:00 in the server's time zone unless changed. An administrator can change this choice and the update window at any time, and install updates manually instead, including outside the update window. Applying updates outside the supported version range may leave the software unable to start safely, by design.

6. Acceptance

The person who accepts this agreement in the installer or in the software's setup accepts it on behalf of the customer and confirms that they are authorized to do so. The software records who accepted which version of this agreement, and when, on the customer's own server and in its database; that record is not sent to the vendor. [Legal review required: acceptance on behalf of an organization]

7. Support

Support scope, response targets and exclusions are stated in the order. [Legal review required: support terms]

8. Warranty and liability

[Legal review required: warranty, disclaimer and limitation of liability language]

9. Term and termination

[Legal review required: term, renewal, termination and post-termination obligations; note that customer data remains with the customer]

10. Governing law

[Legal review required: governing law and venue]