3.3.4. Microsoft Tunnel for Mobile Application Management
💡 First Principle: A VPN normally needs a managed device to hold its configuration, which is exactly what BYOD users refuse to hand over. Tunnel for MAM moves the VPN into the protected apps themselves, so the corporate connection travels with the app protection policy instead of with device enrollment — the same layer-skipping trick that app protection policies use for data.
The gateway comes first. Microsoft Tunnel is a VPN gateway that runs as containers on a Linux server, on premises or in the cloud: Podman on Red Hat Enterprise Linux and Docker on other supported distributions. It needs an Azure subscription, Intune Plan 1 for enrolled devices, and a TLS certificate whose subject alternative name matches the server's address. Setup runs in a fixed order: a server configuration (client IP range, DNS, split tunneling), then a site (the public address and its server configuration), then mstunnel-setup on the server. It needs inbound TCP and UDP 443, and can't sit behind an authenticated proxy or one that inspects TLS. Microsoft Defender for Endpoint is the Tunnel client app on Android and iOS. Monitor servers at Tenant administration > Microsoft Tunnel Gateway > Health status, and keep them on the latest release or one version behind to stay supported. Android 10 support ended March 31, 2026.
Tunnel for MAM extends that gateway to Android and iOS devices that aren't enrolled in Intune. It's an advanced capability that requires Intune Plan 2 or an additional subscription, and it's included in Microsoft 365 E3 and E5 since mid-2026. The two platforms work differently, and the exam likes the differences:
| Android | iOS/iPadOS | |
|---|---|---|
| What provides the VPN | Microsoft Defender for Endpoint app | The Tunnel for MAM iOS SDK built into each app |
| Other apps required | Company Portal installed (sign-in not required) and Defender | None — no Company Portal or Defender |
| VPN scope | Per-app or device-wide | Per-app only |
| Third-party browsers | Only with device-wide VPN | Not supported |
| Policies | App configuration policy for Defender, app configuration policy for Edge, app protection policy | App configuration policy (managed apps) and app protection policy |
On Android, the three policies must target the same groups. The Defender app configuration policy turns on Use Microsoft Tunnel VPN and names the site; the app protection policy sets Start Microsoft Tunnel connection on app-launch to Yes. Tunnel for MAM on Android doesn't support Always-on VPN; use Edge's Strict Tunnel Mode instead, which blocks internet traffic when the VPN is down while the user is signed in with a work account. Target only one Defender app configuration policy per device — several with different sites cause race conditions. Defender in Personal Profile mode isn't supported, and line-of-business apps for unenrolled devices must be deployed as available, not required.
On iOS, line-of-business apps need the Intune App SDK, MSAL and the Tunnel for MAM iOS SDK, plus an Entra app registration. Edge works, but Kerberos sites and certificate-based authentication to websites don't.
Two boundaries apply everywhere. A device that is enrolled can use MAM Tunnel configurations or MDM Tunnel configurations, never both. And Tunnel for MAM isn't available in 21Vianet and doesn't support FIPS.
⚠️ Exam Trap: "Deploy the Defender app and Company Portal to iPhones" is the wrong answer for Tunnel for MAM on iOS. Only Android uses Defender as the VPN client for unenrolled devices; iOS builds the tunnel into each app through the SDK, so it's per-app only and third-party browsers can't use it.
Reflection Question: BYOD Android users need Edge and a line-of-business app to reach an internal site through Tunnel, without enrolling. Which three policies do you create, how must they be assigned, and what replaces Always-on VPN?