Datto RMM Integration

Connect Datto RMM to Atlas AVD: device inventory linked to your session hosts, accounts and sites, and open alerts you can mute or resolve.

Before you begin

  • An Enterprise plan or above. The Integrations hub is locked below Enterprise
  • The Administrator role in Atlas to connect, configure or disconnect a connector. Integrations appears under Administration only for administrators
  • A tenant selected in the tenant picker. Credentials are stored encrypted per tenant, so each tenant you manage connects its own account
  • A Datto RMM API key, and your Datto RMM API URL

What you can do

  • See every Datto RMM device with its site, account, operating system, online status and last seen, and jump from a device to the matching session host in Atlas.
  • Track online and offline devices and open alerts at a glance.
  • Browse your accounts and the sites under each one, with a device count per site.
  • Acknowledge (mute) or resolve open Datto RMM alerts from Atlas.
  • Read and resolve Datto alerts from your own automation with an Atlas API key.

Step 1: Get an API key from Datto RMM

In Datto RMM, open Setup → Global Settings and turn on API access, then generate an API key for a user Atlas can act as (Setup → Users → the user → Generate API Keys). Note the API URL Datto shows alongside it: it is specific to your platform, for example https://pinotage-api.centrastage.net.

Step 2: Connect in Atlas

Once connected, the card shows Manage, which opens the Datto RMM page, and Disconnect. The API key is stored encrypted.

  1. Select the tenant in the tenant picker.
  2. Go to Administration → Integrations and click Connect on the Datto RMM card.
  3. Enter the Platform URL: your Datto RMM API URL, starting with https://, for example https://pinotage-api.centrastage.net.
  4. Paste the API Key and click Connect. Atlas reads your Datto account with the key before saving anything; if Datto rejects it, nothing is stored.

What you see

  • Overview: Total Devices, Online, Offline and Active Alerts, the device online ratio, and how many accounts and sites you have.
  • Devices: host name, site, account, OS, status and last seen. Search by host name, display name, site or account, sort any column, and click the AVD link to open the matching session host. A device links when its host name matches a VM name exactly, or when its short name matches exactly one VM.
  • Alerts: open alerts with device, site, priority, message and when they were raised. Search, and filter by Critical, High, Medium, Low or Info.
  • Sites & Accounts: each account with its sites, each site's description, and the number of devices at each site.

Atlas reads Datto RMM live each time you open a tab or click Refresh; it does not copy your RMM data into Atlas or sync it in the background.

Acknowledge and resolve alerts

Each alert row has two actions, which change the alert in Datto RMM straight away, with no confirmation step:

  • Acknowledge mutes the alert in Datto RMM. It stays open but stops notifying.
  • Resolve resolves the alert in Datto RMM and removes it from the open list.

Use it from your own tools

An Atlas API key with the integration.datto_rmm.read scope can list open alerts at GET /api/integration/datto-rmm/alerts, and one with integration.datto_rmm.write can resolve an alert at POST /api/integration/datto-rmm/alerts/{uid}/resolve. Muting is not available through an API key. See API Access for how keys are issued.

What the integration does not do

  • It does not run components or jobs, open a remote session, reboot, patch or install software through Datto RMM. Use Datto RMM for those, or Atlas Reach.
  • It does not create tickets.
  • Its only changes in Datto RMM are muting and resolving alerts.
  • It connects one Datto RMM account per Atlas tenant.
  • Credentials cannot be edited in place: disconnect and connect again with the new key.
  • Atlas Advisor can tell you whether Datto RMM is connected, but does not answer questions about devices or alerts.

GCC High tenants

On a tenant or deployment in Azure Government (GCC High), calls to Datto RMM are blocked by default, because they can carry VM, host-pool and tenant names to a service outside the Government boundary. Connect fails with an Azure Government (GCC High) egress boundary message and nothing is stored, and pages that read from Datto RMM stay empty. The operator who runs your Atlas deployment can approve Datto RMM as a destination that is allowed to receive that data; once approved, the connector works normally. Running in Azure Government does not by itself make a third-party integration GCC High or CMMC compliant.

Disconnecting

Click Disconnect on the card and confirm. Atlas deletes its stored copy of the API key; nothing changes in Datto RMM. Revoke the key in Datto RMM too if you no longer need it. You can reconnect at any time.

Troubleshooting

  • Datto RMM rejected the supplied credentials: the API key is wrong or has been reset, or API access is off for the account or user.
  • Could not connect to Datto RMM — verify the server URL and credentials: check the Platform URL is your platform's API URL (it ends in -api.centrastage.net).
  • platformUrl must be a valid https:// URL: include https://.
  • Datto RMM is temporarily rate limiting requests: wait a minute and try again.
  • The Devices or Alerts tab is empty when you expect data: click Refresh. An empty tab can also mean Datto returned an error; if it persists, disconnect and connect again to re-test the key.

Next steps