Skip to content

Commit f720bbe

Browse files
committed
Header fix
1 parent b82ed68 commit f720bbe

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

memdocs/intune/protect/microsoft-tunnel-migrate-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -217,11 +217,11 @@ Before you begin your migration to Defender for Endpoint, use the [Microsoft End
217217

218218
2. From Properties, record the available values including those that are assigned as *required* or are assigned as *available*. This information will help you to create similar deployments for the Microsoft Defender for Endpoint app.
219219

220-
## Manage VPN profiles for iOS/iPadOS
220+
### Manage VPN profiles for iOS/iPadOS
221221

222222
To enable devices to use Microsoft Defender for Endpoint to connect to Microsoft Tunnel Gateway, deploy VPN profiles that use the **Microsoft Tunnel (preview)** connection type. During migration you can choose to edit your existing profiles to use the new connection type, or create new VPN profiles with the new connection type.
223223

224-
### Modify a VPN Profile for Microsoft Tunnel
224+
#### Modify a VPN Profile for Microsoft Tunnel
225225

226226
Use the following steps to modify a VPN profile to migrate devices from the standalone tunnel client app to Microsoft Defender for Endpoint as the tunnel client app.
227227

@@ -245,7 +245,7 @@ Use the following steps to modify a VPN profile to migrate devices from the sta
245245
5. After the profile redeploys, wait for devices to check in or force devices to sync to get the new policies.
246246
6. Verify that users can connect to Tunnel manually in the Defender for Endpoint app. If your VPN Profile includes on-demand rules, users must open the Defender for Endpoint app one time before the new on-demand rules can apply.
247247

248-
### Create a new VPN profile for Microsoft Tunnel
248+
#### Create a new VPN profile for Microsoft Tunnel
249249

250250
Use the following steps to create a new VPN profile for devices that will use *Microsoft Defender for Endpoint* as the tunnel client app. When the profile is configured as a per-app VPN, the last step requires you to restart devices after they receive the VPN profile. To avoid this you can choose to [modify an existing VPN profile](#modify-a-vpn-profile-for-microsoft-tunnel) instead of creating and deploying a new one.
251251

0 commit comments

Comments
 (0)