diff --git a/windows/keep-secure/testing-scenarios-for-wip.md b/windows/keep-secure/testing-scenarios-for-wip.md index 1fdd1eb655..09ead9a07b 100644 --- a/windows/keep-secure/testing-scenarios-for-wip.md +++ b/windows/keep-secure/testing-scenarios-for-wip.md @@ -102,64 +102,65 @@ You can try any of the processes included in these scenarios, but you should foc Verify that Windows system components can use WIP.
    -
  1. +
  2. Start Windows Journal and Internet Explorer 11, creating, editing, and saving files in both apps.
    Make sure that all of the files you worked with are encrypted to your configured Enterprise Identity. In some cases, you might need to close the file and wait a few moments for it to be automatically encrypted.
    3. +
  3. Open File Explorer and make sure your modified files are appearing with a Lock icon.
    4. +
  4. Try copying and pasting, dragging and dropping, and sharing using these apps with other apps that appear both on and off the allowed apps list.

    Note
    Most Windows-signed components like File Explorer (when running in the user’s context), should have access to enterprise data.

    A few notable exceptions include some of the user-facing in-box apps, like Wordpad, Notepad, and Microsoft Paint. These apps don't have access by default, but can be added to your allowed apps list.

- + Use WIP on NTFS, FAT, and exFAT systems.
    -
  1. +
  2. Start an app that uses the FAT or exFAT file system (for example a SD card or USB flash drive), and appears on your allowed apps list.
    3. +
  3. Create, edit, write, save, copy, and move files.
    Basic file and folder operations like copy, move, rename, delete, and so on, should work properly on encrypted files.
- + Verify your shared files can use WIP.
    -
  1. +
  2. Download a file from a protected file share, making sure the file is encrypted by locating the Briefcase icon next to the file name.
    3. +
  3. Open the same file, make a change, save it and then try to upload it back to the file share. Again, this should work without any warnings.
    4. +
  4. Open an app that doesn't appear on your allowed apps list and attempt to access a file on the WIP-enabled file share.
    The app shouldn't be able to access the file share.
- + Verify your cloud resources can use WIP.
    -
  1. +
  2. Add both Internet Explorer 11 and Microsoft Edge to your allowed apps list.
    3. +
  3. Open SharePoint (or another cloud resource that's part of your policy) and access a WIP-enabled resource by using both IE11 and Microsoft Edge.
    Both browsers should respect the enterprise and personal boundary.
    4. +
  4. Remove Internet Explorer 11 from your allowed app list and then try to access an intranet site or enterprise-related cloud resource.
    IE11 shouldn't be able to access the sites.

    Note
    Any file downloaded from your work SharePoint site, or any other WIP-enabled cloud resource, is automatically marked as Work.

- + Verify your Virtual Private Network (VPN) can be auto-triggered.
    -
  1. +
  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-wip-policy-using-intune.md) topic.
    3. +
  3. Start an app from your allowed apps list.
    The VPN network should automatically start.
    4. +
  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.
- + Unenroll client devices from WIP. -
    -
  1. -
+ - + Verify that app content is protected when a Windows 10 Mobile phone is locked. -
    -
  1. -
- - - - - -
    -
  1. -
+ \ No newline at end of file