visiq-discovery binary installed to stay: it lives on the device, scans again on a schedule, and reports what it finds to your Discover dashboard. It is how Discovery runs across a managed fleet.
In the product this is the “Discovery Sensor (Standalone)” card, and you will find the
same card in two places: under Discover and under Context Firewall.It is one card and one install, shown twice, not two things to set up. It appears under
Context Firewall because this sensor is how the firewall reaches everything that is not a
browser tab: it carries the host egress proxy, which governs desktop AI apps, third-party
browser extensions, and any browser the extension itself cannot be installed into (Firefox
today). Opening it from either section opens the same walkthrough.If you only want the browser covered, the Context Firewall browser
extension is the lighter option and does not need this
sensor. If you want both, you install this once.
Before you start
- Windows devices enrolled in Microsoft Intune, 64-bit Windows 10 or later, and an Intune role that can add and assign Windows apps.
- A VisIQ account that can open Connect AI. The package you download there is built for your tenant and carries its key, so there is no key to copy.
- Outbound HTTPS from each host to
api.visiqlabs.comanddownloads.visiqlabs.com. Network requirements says what each host is for, which hosts a deployment that runs its own VisIQ API uses instead, and how the sensor uses your proxy.
Install it with Microsoft Intune
Microsoft Intune installs the sensor on Windows as a Win32 app. The package carries the signed sensor itself, so Intune delivers it over its own channel and the install needs no download on the device. The app model is also what keeps the sensor installed and current. Intune deployment of the sensor is available for Windows; macOS and Linux are not available yet. In VisIQ, the Discovery Sensor (Standalone) card under Connect AI walks you through the same steps, with a picture of each Intune screen.- Check for an older VisIQ app. If Intune has no VisIQ app from before this setup, there is nothing to remove (the guide asks this first and chooses no answer for you; the download waits until you answer). Otherwise, under Apps → Windows, open the older app (the guide names it VisIQ Deployed Sensor) and, under Monitor, choose Device install status. If any device reads Installed, the old sensor is still on it: remove it first, by moving those devices’ group from the old app’s Required assignment to its Uninstall assignment (the guide’s Uninstall · remove the sensor steps), and wait until every device reads Not installed. If a device reads Uninstall Failed, its removal stopped partway, and Intune runs it again by itself about a day later: leave the old app and its Uninstall assignment as they are, and ask anyone who uses that device and is signed out to sign in and stay signed in until it reads Not installed (the removal cannot undo a setting VisIQ made for their ChatGPT desktop app while they are signed out). Deleting the app does not remove its sensor, and a device that still has it, or its program, reads Installed for the new app, which then never runs its installer there. So wait until every device reads Not installed, then choose Overview and Delete. The older app looks for the same file as the new one, and while it keeps an Uninstall assignment, Intune can run that uninstall again and remove the new sensor.
- Download the package. In the dashboard press Download install.intunewin, once. It is built for your tenant and saved as one file; there is nothing to unzip, wrap or sign. Every press builds a new package with a new key, and the file carries that key, so store it like a credential and revoke the key under Settings, API keys if it is ever mislaid. On the hosted service your browser, not your devices, downloads the file from
visiq-edr-discovery-binaries.s3.us-east-1.amazonaws.com(a deployment that runs its own VisIQ serves it from its own object store), and each link works for 48 hours: if your web filter blocks the host, allow it and download again. - Create the Win32 app under Apps → Windows → Create → Windows app (Win32), select
install.intunewinas the app package file, and name the app VisIQ Deployed Sensor. On the Program page set the install commandpowershell.exe -NoProfile -ExecutionPolicy Bypass -File install.ps1, the uninstall commandpowershell.exe -NoProfile -ExecutionPolicy Bypass -File uninstall.ps1, and Install behavior = System (the sensor installs for the whole device, not for one person); leave Installation time required (mins) at 60, Allow available uninstall at Yes and Device restart behavior at No specific action. On the Requirements page set Check operating system architecture to Yes. Specify the systems the app can be installed on., then select Install on x64 system only. - Add a detection rule: a File rule that
visiq-discovery.exeexists under%ProgramData%\VisIQ\discovery, with Associated with a 32-bit app on 64-bit clients = No. Detect on presence only, never on a version or a hash: the sensor updates itself in place, so a version or hash rule would make Intune reinstall the packaged build over a newer one. After OK the table lists the rule: File under Type, and the path under Path/Code. - Assign it to a small test group first, as Required on an Entra device security group. Every other device gets it in the last step, Roll out to the rest of your devices. The sensor installs on the next device check-in. On every scheduled run (at start-up and on its interval) it first checks for a newer release and updates itself in place, then scans; a sensor that goes missing, or that fails signature validation, is replaced on the next run. If an update fails, it is tried again after 1, 2 and 4 hours and then every 6 hours, and the reason is written to
%ProgramData%\VisIQ\egress-firewall\update.logon the device. A new release needs no new Intune package. - Check that it arrived. Assigning the app tells each device to check in with Intune, and the device installs the app at that check-in, which can come within moments or take a few hours. To start one device sooner, open it under Devices and choose Sync, or restart the Microsoft Intune Management Extension service on it; the install itself takes a few minutes. The guide’s Check that it arrived step shows what VisIQ has received from your devices; What happens after the scan lists what each state means.
- Roll out to the rest of your devices. When your test devices read Installed, open the app under Apps → Windows, choose Properties, then Edit beside Assignments, add your other device groups under Required, and choose Review + save, then Save. The Required assignment keeps the app installed on them, and the sensor updates itself.
api.visiqlabs.com and downloads.visiqlabs.com; Network requirements says what each host is for. The install checks both hosts, prints the result on lines that start with VisIQ preflight: and saves it in %ProgramData%\VisIQ\discovery\preflight.json. That check never fails the install.
The sensor runs as SYSTEM. From version 0.3.107 it finds the proxy your network uses: a proxy you name for it, the machine WinHTTP proxy, or a PAC file or WPAD that Windows resolves for the computer. When a proxy asks it to sign in, it answers as the computer account and never with a user password, so a proxy that accepts only user passwords must let both hosts through without proxy authentication for the SYSTEM account. If your devices reach the internet through a proxy the computer does not advertise, add it to the install command: powershell.exe -NoProfile -ExecutionPolicy Bypass -File install.ps1 -ProxyUrl http://proxy.example.com:8080.
The Context Firewall proxy listens on 127.0.0.1:8080 when that port is free. If another program holds it, the proxy picks a free local port between 12080 and 12979 instead and keeps it, and the browser and app settings it writes name that port. The port is local to the device, so no firewall rule is needed. Do not reserve that range for the sensor: a reserved port cannot be used by anything, the sensor included.
The signed artifact is the visiq-discovery binary inside the package (Authenticode, DigiCert OV, subject VISIQ LABS LLC), not the .intunewin container, which is never signed. Before a broad rollout, trust the sensor with a Publisher rule keyed on that certificate, as described in the signing note above, so the Defender ASR prevalence rule does not block a fresh binary.
The Context Firewall on the sensor
The same binary carries the Context Firewall’s egress proxy, and the persistent installers turn it on as a second, always-on service beside the scan (visiq-discovery firewall-proxy). It is enabled by default for the tenant; turn it off for everyone from Settings → Context Firewall → Egress proxy on the Deployed Sensor, and every sensor stops terminating traffic within one heartbeat.
What the installer does on each host:
- Enrolls the machine as a firewall endpoint using the credential the sensor already holds (the tenant key an app-mode install carries, or the per-instance agent token on a fleet host). Nothing is pasted by a human, and a re-imaged machine re-enrolls itself under the same name. The endpoint appears on Inventory AI → Browsers with kind proxy.
- Installs the proxy’s certificate authority where the machine’s TLS clients look: the system store and each user’s NSS database plus a Firefox policy on Linux; the System keychain on macOS; the machine Root store on Windows. Firefox is told to import enterprise roots on Linux and macOS; Firefox on Windows is not covered.
- Points the browsers at the proxy by PAC. The proxy serves its PAC file,
proxy.pac, on its local port (8080, or the port it picked), which names only the governed hosts (the same list the extension governs, plus any your tenant adds under Settings → Context Firewall → Additional governed hosts); everything else isDIRECTand never touches the proxy. Chrome, Chromium and Edge get a managed policy on Linux; macOS uses the OS auto-proxy URL on every network service; Windows sets a managed PAC policy for Chrome and Edge and gives Microsoft Copilot and the other governed desktop apps their own proxy settings; for the ChatGPT desktop app it adds a PAC to each signed-in user’s own proxy settings, and leaves that app alone where the user’s proxy is set by policy, WPAD is in use or another managed egress agent is present. It does not change the machine-wide Windows proxy setting.
Desktop AI apps that were already open
Microsoft 365 Copilot on Windows picks up the proxy when it starts, and ChatGPT may take a few minutes to. An app that was already open when the sensor was installed can keep talking to its service directly until it is restarted. The sensor restarts such an app for you. This is on by default, every night at midnight US Central. To change the time or time zone, or to turn it off, go to Settings → Context Firewall → Restart desktop AI apps left unprotected. At that time, each Windows computer restarts only an app that was open before the sensor was installed and is still running without the proxy, and only when nobody is using the computer: if someone has used it in the last 15 minutes, the app is left alone until the same time the next day. An app that is already going through the proxy is never restarted. Uninstalling the sensor reverts the proxy settings, removes the certificate authority from every store it was installed in, and stops the service. Devices apply the removal at their next check-in with Intune; to start it sooner on a device that has not run it yet, open the device under Devices and choose Sync (or, on the device, open Company Portal, choose Settings, then Sync). A device that reads Not installed has had the removal run. If a device reads Uninstall Failed, its removal stopped partway, and Intune runs it again by itself about a day later: leave the Uninstall assignment in place, and ask anyone who uses that device and is signed out to sign in and stay signed in until it reads Not installed (the removal cannot undo a setting VisIQ made for their ChatGPT desktop app while they are signed out).What happens after the scan
The sensor performs a read-only scan and posts one structured report per host to your tenant, where it appears under Inventory AI → Computers. It scans again on the schedule set under Settings → Discovery. A device that has the sensor installed and never reports does not appear under Discover at all. The Check that it arrived step of the Deployed Sensor guide in Connectors tells those cases apart: it reads what VisIQ has received since your package was built and shows one of these states.
When a package was built and only the browser extension is reporting, the card says so on a line of its own, so an extension’s activity never reads as a working sensor. For a device that never reports, When a device never reports lists what to check on the device.
See Discovery for what each scanner detects and the read-only guarantees the sensor holds to.