Atlas Resolve™
DNS filtering delivered by the Atlas agent you already run, with no extra appliance.
Atlas Resolve filters DNS on the devices that run the Atlas Reach agent, including your session hosts. You set one policy for the tenant and override it per host pool: block threat categories, keep your own always-allow and always-block lists, enforce SafeSearch and send lookups upstream over encrypted DNS. The fleet overview shows which devices are enforcing, which need attention, and whether anything is getting around the filter. Atlas Resolve is in preview, is included with Atlas Reach and uses no units of its own: filtering DNS on a device adds nothing to that device's Atlas Reach unit.
Preview. Atlas Resolve™ is available in Atlas AVD today and is marked Preview in the console while it is finished. An administrator can switch preview features off for a tenant.
The problem Atlas Resolve™ solves
Most phishing, malware and command-and-control traffic starts with a DNS lookup, so filtering DNS is one of the cheapest controls you can add to a desktop. The usual options each leave a gap. A network or firewall filter only covers machines routed through it, so a laptop at home or a session host on another virtual network slips past. A cloud DNS service means one more vendor, one more agent or forwarder, and one more console to keep in step with your host pools.
Filtering also tends to break the things that matter most. A badly tuned block list that catches an Entra sign-in or AVD broker name takes every desktop down with it, and nobody can tell from the outside which devices are actually enforcing the policy.
Key capabilities
How Atlas Resolve™ works
- 1Install the Atlas Reach agent on your devices and session hosts
- 2Turn filtering on for the tenant or a host pool and choose categories and lists
- 3Atlas pushes the policy to connected agents straight away; offline devices pick it up when they reconnect
- 4The agent filters lookups locally and forwards allowed ones over encrypted DNS
- 5Devices send a status heartbeat every 15 minutes, and report changes sooner
Policies, categories and lists
Atlas Resolve is under Atlas Operations → Resolve, with tabs for Overview, Query log, Policies, Always allow, Always block and Block page. A policy is a named, reusable set of choices: the categories to block, its own allow and block lists, SafeSearch, the block response and the upstream resolvers. Assign one policy to the tenant and, where a pool needs something different, another to a host pool. The pool's policy replaces the tenant's for its session hosts; the two are not merged. Until you assign one, devices run in monitor mode, logging lookups and blocking nothing, and the page offers Apply recommended policy to get started.
Security categories cover malware, phishing, botnet command and control and cryptomining, from abuse.ch, Phishing.Database and NoCoin feeds refreshed every 12 hours. Content categories such as adult, gambling and social media come from open community lists and Atlas's own classifier, and the console labels their coverage as partial. Lists cover subdomains, and an allow always wins. Up to eight schedules per policy can add blocking at certain times of day, on the device's own clock. Microsoft sign-in, AVD, Windows Update, Intune, Azure Resource Manager and the Teams and Exchange front doors can never be blocked, so a policy cannot cut off the desktops it protects.
How it runs on the device
The Atlas Reach agent answers DNS on the device itself, on Windows, macOS and Linux, so the policy follows a laptop off the network as well as covering session hosts. Allowed lookups go upstream over DNS over HTTPS or TLS to Quad9 (the default), Cloudflare, Google or your own resolver. A blocked site is answered as not existing, or sent to a block page hosted by Atlas or by you; HTTPS sites show the browser's own warning instead of the page. Bypass protection locks the device's DNS settings and turns off secure DNS in the browser, and Block other DNS servers can be switched on.
If the local filter stops answering, a watchdog hands the device its own DNS back within about 30 seconds and the device reports Restored after failure, so a fault never leaves users offline. Turn off for every device, at the top of the page, stops filtering everywhere at once and records your reason in the audit log.
Seeing what is enforced
Devices report a status of Enforcing, Monitoring, Degraded, Leak detected, Off, Error, Stale or Never reported, sending a heartbeat every 15 minutes and changes sooner. The Overview breaks the fleet down by host pool, charts activity over 7, 30 or 90 days, flags devices whose lookups are getting around the filter, and exports to CSV. When a policy records every lookup, the Query log keeps them for 1 to 90 days, 30 by default, and a site can be moved to Always allow or Always block from there. An alert fires when DNS failures spike across the fleet.
How to set up Atlas Resolve™
- 1Install the Atlas Reach agent on your session hosts and other devices.
- 2Open Atlas Operations → Resolve and click Apply recommended policy, or build your own on the Policies tab.
- 3Assign the policy to the tenant, and give any host pool that needs different rules its own policy.
- 4Add the sites you always allow or always block, and choose the block response.
- 5Watch the Overview until devices report Enforcing, then check the Query log for anything blocked by mistake.
Atlas Resolve™: frequently asked questions
Which plan includes Atlas Resolve?
Every plan, Community included, wherever Atlas Reach is on. It is in preview and uses no units of its own: a device uses only its Atlas Reach unit, and verified AVD session hosts need none. Running out of units does not switch filtering off.
Which operating systems does it support?
Windows, macOS and Linux devices running the Atlas Reach agent, from the first agent builds with DNS filtering. Older agents show as Never reported until they update.
Can I filter differently for different users on the same session host?
No. Filtering is per device, so everyone on a shared session host gets that host pool's policy. Use separate host pools when groups of users need different rules.
Could a policy break sign-in or AVD itself?
No. Entra sign-in, AVD, Windows Update, Intune, Azure Resource Manager and the Teams and Exchange front doors are protected and can never be blocked, whatever the policy says.
What happens if the filter fails on a device?
A watchdog gives the device its own DNS back within about 30 seconds, so users stay online, and the device reports Restored after failure. A spike of failures across the fleet raises an alert.
How is it different from Azure Firewall or the DNS Filter integration?
Azure Firewall only filters traffic routed through it. Atlas Resolve filters on the device, so it covers laptops off the network too. The DNS Filter and Cisco Umbrella integrations bring a service you already pay for into Atlas; Resolve is Atlas's own filtering.
Related features
Guides
Available on
Community plan and above
Atlas Resolve™ is included in every Community subscription.