Azure Intune: Multi-User VDI

WAI Docs Wed Aug 19 13:22:37 EDT 2026
List
Quick Start
Welcome
Supported Applications & LLMs
Release Notes
August 18, 2026 WitnessAI Release
August 4, 2026 WitnessAI Release
July 21, 2026 WitnessAI Release
July 14, 2026 WitnessAI Release
July 9, 2026 WitnessAI Release
June 30, 2026 WitnessAI Hotfix
June 23, 2026 WitnessAI Release
June 16, 2026 WitnessAI Release
June 11, 2026 WitnessAI Release
June 4, 2026 WitnessAI Hotfix
June 2, 2026 WitnessAI Update
May 19, 2026 WitnessAI Update
April 30, 2026 WitnessAI Update
April 28, 2026 WitnessAI Update
April 23, 2026 WitnessAI Update
April 16, 2026 WitnessAI Update
April 14, 2026 WitnessAI Update
April 9, 2026 WitnessAI Update
April 9, 2026 WitnessAI Update
April 7, 2026 WitnessAI Update
April 2, 2026 WitnessAI Update
March 31, 2026 WitnessAI Update
March 24, 2026 WitnessAI Update
March 19, 2026 WitnessAI Update
March 17, 2026 WitnessAI Update
March 12, 2026 WitnessAI Update
March 5, 2026 WitnessAI Update
February 26, 2026 WitnessAI Update
February 24, 2026 WitnessAI Update
February 10, 2026 WitnessAI Update
January 27, 2026 WitnessAI Update
January 20, 2026 WitnessAI Update
January 13, 2026 WitnessAI Update
December 18, 2025 WitnessAI Update
December 9, 2025 WitnessAI Update
November 25, 2025 WitnessAI Update
November 18, 2025 WitnessAI Update
November 11, 2025 WitnessAI Update
October 28, 2025 WitnessAI Update
October 23, 2025 WitnessAI Update
October 9, 2025 WitnessAI Update
October 2, 2025 WitnessAI Update
September 30, 2025: WitnessAI Update
September 23, 2025: WitnessAI Update
August 12, 2025: WitnessAI Update
July 31, 2025: WitnessAI Update
July 18, 2025: WitnessAI Update
April 11, 2025: WitnessAI Release v2.0
June 9, 2025: WitnessAI Update
June 23, 2025: WitnessAI Update
TOC Left Sidebar: not active
TOC Left Sidebar: ORIGINAL
User Guide
Policies - GuardRails
Witness Anywhere: Remote Device Security
Witness Attack
Administrator Guide
404

Witness Anywhere Deployment on Azure VDI (Multi-User) using Intune

💡
Note: This solution is designed for an Azure Virtual Desktop (AVD) deployment using a multi-user per VM model with persistent storage. Stunnel is not supported in multi-user VDI environments; therefore, traffic from the Copilot Personal thick client application will not be intercepted by Witness AI.
Architecture flow diagram for ‘Witness Anywhere Deployment on Azure VDI’ showing the deployment steps with horizontal arrows: Download Registration Script → Scheduled Task Creation → Witness Anywhere Registration → (below the arrow) Deploy via Intune, User Logon Event, LLM Traffic Routing. The diagram illustrates how registration scripts are deployed through Intune and triggered on user login for multi-user VDI environments.

Generate PAC Token & Download Files

  1. As a User with Admin Role or above, log into the WitnessAI Console.
  2. Click on the Settings menu item (1), then click on Proxy Configuration in the sub-menu (2).
  3. Enter a name in the Key Name field (3).
  4. Choose an Expiration Date (4).
  5. Click the Generate PAC Token button (5).
WitnessAI Settings > Proxy Configuration page with numbered callouts (1-7) for the Azure Intune Multi-User VDI deployment. Shows Settings menu (1), Proxy Configuration sub-menu (2), Key Name field (3), Expiration Date (4), Generate PAC Token button (5). A table shows existing PAC tokens with their expiration dates, and a row highlighted (6) showing where to click the download symbol to get the scripts using Microsoft Intune (Windows) option (7).
  1. Locate the row in the list with the Key Name and Expiration Date of the PAC Token you created (6), and click the Download Symbol.
  2. Click on Microsoft Intune (Windows) (7) from the dropdown, and a zip file will be downloaded to your Downloads folder.
The downloaded file will have a name similar to: 1227db3823fcc1c7cd1db6cc3ed0c5cc1c7cd1da15c5b50a5b.zip.
It will uncompress to a folder of the same name, containing another folder called azure_multi_user_vdi with two files:
register_device.ps1: A powershell script to register the user device with Witness Anywhere.
flush.ps1: A powershell script to deregister the user device from Witness Anywhere.

Configure The Device Group

  1. Log in to Intune Admin Console
  2. Navigate to Groups and click on New group
  3. Enter the following information:
    • Group type: Security
    • Group name: Azure-VDI-Hosts
    • Under Members, click on No members selected and add all the Azure VDI Hosts.
  4. Finally Click on Create
Microsoft Intune admin center ‘New Group’ form for configuring the Azure VDI device group. Fields shown with orange highlights: Group type (Security), Group name (Azure-VDI-Hosts), Group description (empty), Microsoft Intune roles checkbox, Membership type (Assigned), Owner (No owners selected), Members (1 member selected) with Create button at bottom.

Deploying The Registration Script

  1. In the Microsoft Intune Admin Center, navigate to Devices > Scripts and Remediations > Platform Scripts, click Add, and select Windows 10 and later as the platform.
Microsoft Intune admin center showing Devices > Scripts and remediations for the Azure Intune Multi-User VDI deployment. The Platform scripts tab is selected with ‘Windows 10 and later’ filter applied. The navigation shows Scripts and remediations highlighted in the left menu.
  1. Enter the name of the script as Witness-Anywhere-Registration, then click Next to proceed
  2. In the Script settings section, enter the following details and click Next:
    • Script location: Browse and select the register_device.ps1 file downloaded from the WitnessAI console
    • Run this script using the logged on credentials: No
    • Enforce script signature check: No
    • Run script in 64 bit PowerShell Host: No
Microsoft Intune admin center ‘Add PowerShell script’ for Witness Anywhere Multi-User VDI - Script settings tab. Script location shows ‘register_device.ps1’. ‘Run this script using the logged on credentials’ is set to Yes (blue, enabled). ‘Enforce script signature check’ and ‘Run script in 64 bit PowerShell Host’ are set to No.
  1. In the Assignments section, click Add groups under Included groups, select the previously created device group Azure-VDI-Hosts, and then click Next.
Microsoft Intune admin center ‘Add PowerShell script’ Assignments tab for the registration script. Shows ‘Included groups’ section with the Azure-VDI-Hosts device group added (1 devices, 0 users), a Remove button, and an information note about user and device group assignment. The ‘Excluded groups’ section shows no groups selected.
  1. Finally, review the configuration summary and click Create to complete the script deployment.
  2. At this point, the script will be pushed to all VDI hosts that are members of the selected device group, and a scheduled task named "Witness-Anywhere-Registration" will be created on each host to run automatically at user logon.
  3. Note: The registration script will be stored in the location specified below. Please ensure that this path is included in the persistent storage configuration.
    C:\Users\Default\AppData\Local\WitnessAI
  4. When a user logs on to a VDI host, the registration script executes, enrolling the user into Witness Anywhere and applying the configured Proxy PAC URL. From that point forward, all LLM traffic initiated by the user will be automatically routed through WitnessAI for policy enforcement and monitoring.
  5. Each time a user logs in to the VDI host, the registration script will execute for all active sessions. Users who are already registered will be skipped, while any new users will be automatically enrolled in Witness Anywhere.

Deploying The Flush Script

  1. To flush the Witness Anywhere configuration from a VDI host, follow the same steps as when deploying the registration script. However, instead of selecting the register_device.ps1 file, use the flush.ps1 file to remove the configuration.
  2. When the script is executed on the host, all logged-in users are de-enrolled from Witness Anywhere. In addition, the scheduled task created for Witness Anywhere registration is removed, and old log files are cleaned up.
  3. Logs: C:\Windows\Temp\pac-flush-log.txt
Microsoft Intune admin center ‘Add PowerShell script’ for the flush script (flush.ps1) deployment. Script settings tab shows: Script location field with ‘flush.ps1’, ‘Run this script using the logged on credentials’ set to Yes (blue), ‘Enforce script signature check’ set to Yes (blue), ‘Run script in 64 bit PowerShell Host’ set to No. This is for Deploying The Flush Script step in Azure Intune Multi-User VDI setup.