From 9b4886e0c5c8f7eb03fd492aa55d65e0aceba6f6 Mon Sep 17 00:00:00 2001 From: LizRoss Date: Wed, 12 Apr 2017 12:29:24 -0700 Subject: [PATCH] Fixing broken links --- windows/keep-secure/testing-scenarios-for-wip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/testing-scenarios-for-wip.md b/windows/keep-secure/testing-scenarios-for-wip.md index 81e9282bd3..a0c2aaf46e 100644 --- a/windows/keep-secure/testing-scenarios-for-wip.md +++ b/windows/keep-secure/testing-scenarios-for-wip.md @@ -141,7 +141,7 @@ You can try any of the processes included in these scenarios, but you should foc Verify your Virtual Private Network (VPN) can be auto-triggered.
    -
  1. Set up your VPN network to start based on the WIPModeID setting.
    For specific info about how to do this, see the [Create and deploy a VPN policy for Windows Information Protection (WIP) using Microsoft Intune](create-wip-policy-using-intune.md) topic.
    2. +
  2. Set up your VPN network to start based on the WIPModeID setting.
    For specific info about how to do this, see the [Create and deploy a VPN policy for Windows Information Protection (WIP) using Microsoft Intune](create-vpn-and-wip-policy-using-intune.md) topic.
  3. Start an app from your allowed apps list.
    The VPN network should automatically start.
  4. Disconnect from your network and then start an app that isn't on your allowed apps list.
    The VPN shouldn't start and the app shouldn't be able to access your enterprise network.