How to Configure Application Guard, Hardware Isolated Browsing, and Sandbox Governance in Microsoft Edge

Modern enterprise workforces interact with thousands of external web domains daily, exposing corporate endpoints to zero-day browser vulnerabilities, drive-by malware payloads, and sophisticated phishing campaigns. Traditional software-level sandbox protections within web browsers operate inside the host operating system’s memory space, leaving endpoints vulnerable to sandbox escape exploits. Microsoft Edge counters this threat through Microsoft Defender Application Guard (MDAG).

Application Guard leverages hardware-enforced Hyper-V virtualisation to isolate untrusted browsing sessions within a lightweight, disposable micro-virtual machine. When an employee navigates to an untrusted domain or clicks an unknown URL, Edge spins up an isolated container separate from the host kernel. Malware cannot escape the container, cannot access local user credentials, and cannot persist: the moment the isolated browser window terminates, the entire virtual container is destroyed.

Architectural Overview: Hyper-V Hardware Isolation in Microsoft Edge

Application Guard bifurcates web traffic into trusted corporate network zones and untrusted public networks using network isolation boundaries:

Security Layer	Host OS Environment	Application Guard Micro-VM
Kernel Boundary	Native Windows 11 / Windows 10 host kernel.	Isolated Hyper-V container with a separate, stripped-down kernel copy.
Local Storage & Files	Direct access to local user folders and profiles.	Zero access to host storage; ephemeral VHD discarded upon window closure.
Credential Vault	Enterprise Single Sign-On (SSO) and Kerberos.	Isolated credential storage; host corporate tokens are inaccessible.
Clipboard & Printing	Unrestricted bidirectional data transfer.	Policy-governed unidirectional or blocked clipboard and print services.
Network Classification	Internal enterprise intranet and cloud resources.	Public internet, unclassified domains, and phishing candidate URLs.

Enabling the Application Guard Windows Feature via PowerShell

Before Microsoft Edge can instantiate isolated sessions, the underlying Hyper-V container feature must be installed on Windows 11 or Windows 10 Enterprise / Pro / Education.

Step 1: Install the Windows Optional Feature

Open an elevated PowerShell window as an Administrator:

# Enable Microsoft Defender Application Guard feature
Enable-WindowsOptionalFeature -Online -FeatureName "Windows-Defender-ApplicationGuard" -NoRestart

# Enable underlying Hyper-V Hypervisor prerequisites if not present
Enable-WindowsOptionalFeature -Online -FeatureName "Microsoft-Hyper-V-Hypervisor" -NoRestart

Step 2: Restart the Endpoint

Reboot the computer to initialise the low-level Hyper-V hypervisor micro-VM platform:

Restart-Computer

Configuring Application Guard Policies via Group Policy / Intune

Enterprise administrators configure Application Guard behaviour using Group Policy (GPO) or Microsoft Intune Administrative Templates.

Step 1: Define Network Isolation Boundaries

Application Guard needs to know which domains are trusted enterprise assets so that only untrusted domains trigger the container. In Group Policy Editor (gpedit.msc), navigate to:

Computer Configuration > Administrative Templates > Network > Network Isolation

1. Open Enterprise cloud resources.
2. Toggle to Enabled and define your corporate cloud domains separated by pipes (e.g. sharepoint.com|outlook.office.com|enterprise.internal).
3. Open Enterprise domains and specify internal intranet DNS suffixes (e.g. corp.local).

Step 2: Configure Microsoft Edge Application Guard Settings

Navigate to Computer Configuration > Administrative Templates > Windows Components > Microsoft Defender Application Guard:

Policy Name	Recommended Setting	Operational Impact
Turn on Microsoft Defender Application Guard in Managed Mode	Enabled (Option 1: For Microsoft Edge)	Enables automated container launches when untrusted URLs are opened in Edge.
Configure clipboard settings	Enabled: Block clipboard operation (or Isolated-to-Host only)	Prevents untrusted sites from reading sensitive data from the host clipboard.
Configure print settings	Enabled: Print to PDF / XPS only	Restricts untrusted web documents from accessing local enterprise network printers.
Allow data persistence	Disabled	Ensures all cookies, cache, and downloaded artefacts are purged on session close.

Operating an Application Guard Browser Session

Once policies are deployed, users can launch isolated sessions automatically or on-demand.

Step 1: Launching an Application Guard Window Manually

1. Launch Microsoft Edge.
2. Click the Settings and more (three dots) menu in the upper-right corner.
3. Select New Application Guard window.
4. Edge initialises the Hyper-V micro-VM. The isolated browser window opens, identifiable by a distinct shield badge icon in the title bar and tab strip.

Step 2: Automated Redirection of Untrusted URLs

When an employee clicks an external web link from an email in Outlook or enters an external URL in the primary browser window, Edge evaluates the enterprise boundary definition. If the URL is not on the corporate white-list, Edge automatically loads the destination inside the isolated Application Guard container.

Troubleshooting Application Guard and Edge Sandbox Errors

Consult this diagnostic reference table to debug hardware virtualization faults and policy conflicts:

Error Code / Symptom	Underlying Root Cause	Corrective Action
Error 0x80070422 / 0x80070005: Failed to start Application Guard	Virtualization technology (VT-x or AMD-V) or Second Level Address Translation (SLAT) is disabled in computer BIOS/UEFI.	Reboot into system BIOS and enable Intel Virtualization Technology / SVM Mode and DEP (Data Execution Prevention).
Internal enterprise intranets open unexpectedly inside Application Guard.	Intranet domains or internal IP ranges are missing from the Network Isolation enterprise boundaries policy.	Update EnterpriseCloudResources and EnterpriseInternalProxyServers policies with all corporate domain wildcards and internal CIDR subnets.
“New Application Guard window” menu item is disabled or missing.	The device runs an unsupported Windows edition (e.g. Windows Home), or MDAG feature was uninstalled.	Verify edition with winver; Application Guard requires Pro, Enterprise, or Education. Reinstall feature via Enable-WindowsOptionalFeature.
Slow performance or high RAM consumption on container startup.	Container micro-VM is allocating standard dynamic memory slices on hardware with limited resources.	Ensure host endpoints have at least 8 GB RAM and 4 physical CPU cores. Enable hardware-accelerated graphics remoting in MDAG policies.
Users cannot download files or save documents to local drives.	By design, Application Guard blocks filesystem persistence to prevent malware drop vectors.	If file retrieval is mandatory, configure the policy “Allow files to download and save to the host operating system from Microsoft Defender Application Guard” with file inspection enabled.

Implementing Microsoft Defender Application Guard creates an impenetrable barrier against zero-day web threats, isolating untrusted browsing into disposable hardware containers and ensuring host endpoint resilience across the enterprise.