Question 1

Which devices can I connect to with Atlas Reach?

Accepted Answer

Live view and control works on enrolled Windows devices — session hosts and physical Windows endpoints running the Atlas AVD Agent. Operators choose view-only or full control per session. The Atlas Reach agent for macOS and Linux lands Macs, Linux workstations, and Linux VMs on the same Devices page speaking the identical device-facing contract, with live health monitoring today; remote control of those platforms is monitoring-only in v1.

Question 2

Is remote control on by default?

Accepted Answer

No. Remote control is off unless the server enables it, and a session runs only for an authorized, entitled operator. Every session is audited. A fleet that does not want the capability at all can install the agent telemetry-only, which leaves remote control out entirely — and that install-time choice is one the server can never override.

Question 3

Does Atlas Reach open an inbound port to my devices?

Accepted Answer

No. The agent holds a persistent outbound connection to the server — the same authenticated channel it reports telemetry on — and the server relays the session to the operator. Nothing connects inbound to the device, and because the control channel authenticates with the device's own credential, revoking a device means it can no longer be reached.

Question 4

What does Atlas Reach cost?

Accepted Answer

Atlas Reach is metered in units, like the End User Portal and Atlas Ink: one unit per calendar month for every managed device the agent is installed on that is neither an Azure VM nor an AVD session host — physical Windows, Mac, and Linux endpoints, and VMs that run outside Azure and belong to no host pool. Any Azure VM is free, of any kind, and so is any AVD session host, however much Reach is used on them. A unit is always $1, drawn first from your plan's pooled monthly unit allowance and billed per unit beyond it; Founding Partners (the first 25 subscribers) get a 25% discount on unit usage, applied on their Stripe invoice.

Question 5

Why are Azure VMs and AVD session hosts free?

Accepted Answer

Managing your Azure estate is what your Atlas AVD plan's flat price already buys, so any Azure VM is free — of any kind, whether or not it sits in an AVD host pool — and so is any AVD session host. Reach counts units only for devices beyond that: the physical endpoints, and the VMs running outside Azure, that it brings onto the same Devices page.

Question 6

How do devices get enrolled?

Accepted Answer

A tenant admin mints an enrollment token on the Atlas Reach Devices page and bakes it into the agent install. The device enrolls once, receives its own long-lived device credential, and every later connection authenticates with that credential — one enrollment token binds to exactly one tenant, so a device can never report into someone else's environment.

Atlas Reach: Remote View & Control for AVD