Tactical RMM Integration

Connect a self-hosted Tactical RMM server to Atlas AVD: agent inventory linked to your session hosts, clients and sites, and more.

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 Tactical RMM server whose API address is reachable from the internet (Atlas does not connect to private or internal addresses)
  • A Tactical RMM API key

What you can do

  • See every Tactical RMM agent with its client, site, operating system, status and last check-in, and jump from an agent to the matching session host in Atlas.
  • Track online and offline agents and active alerts at a glance.
  • Browse your clients and the sites under each one, with an agent count per site.
  • Acknowledge (snooze for a day) or resolve active Tactical RMM alerts from Atlas.
  • Read and acknowledge Tactical alerts from your own automation with an Atlas API key.

Step 1: Create an API key in Tactical RMM

In Tactical RMM, open Settings → Global Settings → API Keys and add a key for Atlas, tied to a user whose permissions let it view agents, clients and alerts and update alerts. Copy the key. A dedicated user makes it easy to see Atlas's activity and to revoke it later.

Step 2: Connect in Atlas

Once connected, the card shows Manage, which opens the Tactical 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 Tactical RMM card.
  3. Enter the Server URL: the address of your Tactical RMM API server, usually the api. host, for example https://api.rmm.example.com.
  4. Paste the API Key and click Connect. Atlas calls your server with the key before saving anything; if the server rejects it or cannot be reached, nothing is stored.

What you see

  • Overview: Total Agents, Online, Offline and Active Alerts, the agent online ratio, and how many clients and sites you have. Agents that are overdue count as offline.
  • Agents: host name, client, site, OS, status and last seen. Search by host name, client or site, sort any column, and click the AVD link to open the matching session host. An agent links when its host name matches a VM name exactly, or when its short name matches exactly one VM.
  • Alerts: unresolved alerts with agent, type, severity, message and when they were raised. Search, and filter by Critical, Error, Warning or Info.
  • Clients & Sites: each client with its sites and the number of agents at each site.

Atlas reads Tactical 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 Tactical RMM straight away, with no confirmation step:

  • Acknowledge snoozes the alert in Tactical RMM for one day. Alerts that are already snoozed do not show the button.
  • Resolve marks the alert resolved in Tactical RMM. The alert's history is kept.

Use it from your own tools

An Atlas API key with the integration.tactical_rmm.read scope can list alerts at GET /api/integration/tactical-rmm/alerts, and one with integration.tactical_rmm.write can acknowledge an alert at POST /api/integration/tactical-rmm/alerts/{id}/acknowledge. Resolving 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 scripts, open a remote session, reboot, patch or install software through Tactical RMM. Use Tactical RMM for those, or Atlas Reach.
  • It does not create tickets.
  • Its only changes in Tactical RMM are acknowledging and resolving alerts.
  • It connects one Tactical RMM server per Atlas tenant.
  • It cannot reach a server on a private network or one that resolves to a private address.
  • Credentials cannot be edited in place: disconnect and connect again with the new key.
  • Atlas Advisor can tell you whether Tactical RMM is connected, but does not answer questions about agents or alerts.

GCC High tenants

On a tenant or deployment in Azure Government (GCC High), calls to Tactical 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 Tactical RMM stay empty. The operator who runs your Atlas deployment can approve Tactical 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 Tactical RMM. Delete the key in Tactical RMM too if you no longer need it. You can reconnect at any time.

Troubleshooting

  • Tactical RMM rejected the API key: the key is wrong, expired or deleted. Create a new one and connect again.
  • Could not connect to Tactical RMM — verify the server URL and API key: check the address is the API host, that it resolves to a public IP address, that its certificate is valid, and that the server is up.
  • serverUrl must be a valid http:// or https:// URL: include the scheme, for example https://.
  • The Agents or Alerts tab is empty when you expect data: click Refresh. An empty tab can also mean Tactical RMM returned an error; if it persists, disconnect and connect again to re-test the key.
  • Stored credentials could not be decrypted — please reconnect: disconnect and connect again.

Next steps