Does Nerdio Manager Store Customer Information?

Does Nerdio Manager Store Customer Information

Nerdio Manager is an Azure application that is installed into your (the MSP's) Azure subscription. As the end customer's managed service provider, you then create a Nerdio Manager account, allowing you to provision, manage, and optimize their IT environment in Azure. Nerdio Manager creates a service principal in your customer's Azure tenant when the Nerdio Manager account is first created, and makes Microsoft Graph API calls using that service principal to execute the tasks you initiate from the Nerdio Manager portal.

Nerdio staff does not have access to your install of Nerdio Manager, unless you specifically grant access. Consequently, the Nerdio staff does not have access to the customer's data. In addition, Nerdio Manager does not collect any customer data.

Your install of Nerdio Manager reports usage information to our licensing servers on a periodic basis. Specifically, we store the following information in our licensing servers about your Nerdio Manager install and about each of your Nerdio Manager accounts.

Your Nerdio Manager install:

  • License registration information you provided during the installation of Nerdio Manager: first name, last name, company, phone number, email address, distributor, and Azure tenant & subscription's name, ID and domain.

  • Email address of the user that last updated your Nerdio Manager install.

  • Initial version of Nerdio Manager that you installed.

  • Current version of Nerdio Manager.

  • Mailing address, if you enter the address on Settings page.

Your Nerdio Manager customer accounts:

  • Account name and ID.

  • Date and time account was created.

  • Azure tenant, subscription, and region of account.

  • Identity method of account (Entra ID, Entra Domain Services, or Active Directory).

  • Whether account has been tagged as an Internal Use account.

  • Status of account (active or in process of being provisioned).

  • AVD Workspaces name and ID.

  • Number of Host Pools, their names and IDs.

  • Number of Hosts in each host pool.

  • Number of VMs in each host pool.

  • Number of CPU cores in each host pool.

  • Number of desktop users by host pool.

  • Count of user sessions by host pool.

  • Monthly active user count for current month and for past 30 days by host pool.

For example, here is a test account:

Product analytics data for your Nerdio Manager customer accounts

  • Tasks

    • Job type | Number of successful | Number of failed.

    • Count of all tasks in the last 30 days.

  • Page Views

    • Page name | URL | Views count

  • Public API Requests

    • Name | URL | Requests count.

    • Name format: <HTTPMethod> ResourceName/ResourceAction, for example: GET Accounts/List.

    • Request count: all requests regardless of response status.

  • Unique Users

    • Number of daily unique visitors, derived from page views.

    • The number of users assigned to the Nerdio Manager application. We do not collect any details about users and do not track logins to the portal. Instead, we collect page views, so as to know the number of unique visitors and which pages they visited.

  • MSP Metrics (numeric value)

    • Accounts.

    • Count of linked RGs.

    • Count of linked networks.

    • Scripted actions.

    • Scripted actions assigned to global images.

    • Scripted actions assigned to accounts.

    • Azure Runbook scheduled scripted actions.

    • Linked GitHub repositories.

    • Global images count.

    • Count of global images assigned to accounts.

    • Users assigned to Nerdio Manager.

    • Users logged in.

    • Custom roles.

    • Cost estimates.

    • Workflows.

  • Account Metrics (numeric value)

    • Desktop images.

    • Desktop images applied to pools.

    • AVD pools.

    • Auto-scale-enabled AVD pools.

    • Scripted actions count.

    • Count of scripted actions assigned to pools.

    • Linked GitHub repositories.

    • Count of linked RGs.

    • Directory profiles.

    • FSLogix profiles storage.

    • Recovery vaults.

    • Intune apps (enabled/disabled).

    • Intune devices.

    • Intune compliance and configuration policies.

    • Intune security policies.

    • MSIX App Attach images.

    • MSIX App Attach certificates.

    • MSIX App Attach storage locations.

    • Servers.

    • Count of linked networks.

    • Networks.

    • VPNs.

    • Network security groups.

    • Public IPs.

    • NAT Gateways.

    • Azure Files shares.

    • Windows 365 network connections.

    • Windows 365 provisioning policies.

    • Windows 365 Cloud PC images.

    • Azure monitor insights enabled/disabled.

Settings for each account in an install without tracking customer data

  • MSP Settings (enabled / disabled)

    • Details of REST API activity - number of API calls to each endpoint along with their frequency -daily, weekly, also keep a tab on less frequently used APIs.

    • Azure Runbooks.

    • Notifications.

    • Announcements.

  • Account Settings (enabled / disabled)

    • Intune.

    • Remote Assistance.

    • Azure Monitor Insights.

    • Azure Runbooks.

Unattended Access module

  • Device name

  • Device full name: The host name used to identify the device

  • Platform: The device's OS platform.

  • OS name: The full name of the device's OS (for example, Windows 10 Pro)

  • OS version: The NT version

  • MAC address

  • Serial number

  • Manufacture's name

  • Product name: The device's model

  • Service tag

  • UUID

  • GUID

  • Domain name: The domain in which the device is configured

  • AD domain name

  • IP address: The public IP via which the device connects to assist servers

  • Private IP address

  • Subnet mask

  • DHCP server

  • Active users: The user name logged in to the remote device

Was this article helpful?

0 out of 0 found this helpful
Have more questions? Submit a request

Comments (0 comments)

Please sign in to leave a comment.