Create a Windows Information Protection (WIP) policy with MAM using the Azure portal for Microsoft Intune

Applies to:

  • Windows 10, version 1703 and later
  • Windows 10 Mobile, version 1703 and later (except Microsoft Azure Rights Management, which is only available on the desktop)

By using Microsoft Intune with Mobile application management (MAM), organizations can take advantage of Azure Active Directory (Azure AD) and the app protection policy feature to keep employees from logging in with personal credentials and accessing corporate data. Additionally, MAM solutions can help your enterprise do the following for mobile apps:

  • Configure, update, and deploy mobile apps to employees
  • Control what your employees can do with enterprise data, such as copying, pasting, and saving
  • Keep enterprise data separate from your employee's personal data
  • Remove enterprise data from employee's devices
  • Report on mobile app inventory and track usage

Note

This topic covers creating a Windows Information Protection (WIP) policy for organizations using a mobile application management (MAM) solution to deploy your WIP policy to Intune apps without device enrollment. If you are already managing devices by using a Mobile Device Management (MDM) solution, you must follow the instructions in the Create a Windows Information Protection (WIP) with enrollment policy using the Azure portal for Microsoft Intune topic.

Prerequisites to using MAM with Windows Information Protection (WIP)

Before you can create your WIP policy with MAM, you must first set up your MAM provider. For more info about how to do this, see the Get ready to configure app protection policies for Windows 10 topic.

Additionally, you must have an Azure AD Premium license and be running at least Windows 10, version 1703 on your device.

Important

WIP doesn't support multi-identity. Only one managed identity can exist at a time.

Add a WIP policy

After you’ve set up Intune for your organization, you must create a WIP-specific policy.

To add a WIP policy

  1. Open the Azure portal and click the Intune service from the sidebar.

    The Microsoft Intune Overview blade appears.

  2. Click Mobile apps, click App protection policies, and then click Add a policy.

    Microsoft Intune management console: App policy link

  3. In the Add a policy blade, fill out the fields:

  4. Click Create.

    The policy is created and appears in the table on the Mobile apps - App protection policies blade.

    Note

    Optionally, you can also add your apps and set your settings from the Add a policy blade, but for the purposes of this documentation, we recommend instead that you create the policy first, and then use the subsequent menus that become available.

Add apps to your Allowed apps list

During the policy-creation process in Intune, you can choose the apps you want to allow, as well as deny, access to your enterprise data through WIP. Apps included in this list can protect data on behalf of the enterprise and are restricted from copying or moving enterprise data to unprotected apps.

The steps to add your apps are based on the type of template being applied. You can add a recommended app, a store app (also known as a Universal Windows Platform (UWP) app), or a signed Windows desktop app. You can also import a list of approved apps or add exempt apps.

In addition, you can create an app deny list related to the policy based on an action value. The action can be either Allow or Deny. When you specify the deny action for an app using the policy, corporate access is denied to the app.

Important

Enlightened apps are expected to prevent enterprise data from going to unprotected network locations and to avoid encrypting personal data. On the other hand, WIP-unaware apps might not respect the corporate network boundary, and WIP-unaware apps will encrypt all files they create or modify. This means that they could encrypt personal data and cause data loss during the revocation process.

Care must be taken to get a support statement from the software provider that their app is safe with WIP before adding it to your Allowed apps list. If you don’t get this statement, it’s possible that you could experience app compatibility issues due to an app losing the ability to access a necessary file after revocation.

For this example, we’re going to add a few recommended apps to the Allowed apps list.

To add a recommended app

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Allowed apps from the menu that appears.

    The Allowed apps blade appears, showing you any apps that are already included in the list for this policy.

    Microsoft Intune management console: Viewing the recommended apps that you can add to your policy

  2. From the Allowed apps blade, click Add apps.

    The Add apps blade appears, showing you all Recommended apps.

    Microsoft Intune management console: Adding recommended apps to your policy

  3. Select each app you want to access your enterprise data, and then click OK.

    The Allowed apps blade updates to show you your selected apps.

    Microsoft Intune management console: Allowed apps blade with recommended apps

  4. Click Save to save the Allowed apps list to your policy.

Add a Store app to your Allowed apps list

For this example, we’re going to add Microsoft Power BI, a Windows store app, to the Allowed apps list.

To add a Store app

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Allowed apps from the menu that appears.

    The Allowed apps blade appears, showing you any apps that are already included in the list for this policy.

  2. From the Allowed apps blade, click Add apps.

  3. On the Add apps blade, click Store apps from the dropdown list.

  4. Type the friendly name of the app, the publisher info, and the product name. For this example, the Publisher is CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US and the Product name is Microsoft.MicrosoftPowerBIForWindows.

  5. After you’ve entered the info into the fields, click OK to add the app to your Allowed apps list, and then click Save to save the Allowed apps list to your policy.

    Note

    To add multiple Store apps at the same time, you can click the menu (…) at the end of the app row, and continue to add more apps. When you’re done, click OK.

    Microsoft Intune management console: Adding Store app info

Find the Name, Publisher, and Product name for Store apps

If you don't know the publisher or product name for your Store app, you can find them for both desktop devices and Windows 10 Mobile phones by following these steps.

To find the publisher and product name values for Store apps without installing them

  1. Go to the Microsoft Store for Business website, and find your app. For example, Microsoft Power BI.

  2. Copy the ID value from the app URL. For example, Microsoft Power BI ID URL is https://www.microsoft.com/en-us/store/p/microsoft-power-bi/9nblgggzlxn1, and you'd copy the ID value, 9nblgggzlxn1.

  3. In a browser, run the Microsoft Store for Business portal web API, to return a JavaScript Object Notation (JSON) file that includes the publisher and product name values. For example, run https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9nblgggzlxn1/applockerdata, where 9nblgggzlxn1 is replaced with your ID value.

    The API runs and opens a text editor with the app details.

        {
            "packageIdentityName": "Microsoft.MicrosoftPowerBIForWindows",
            "publisherCertificateName": "CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
        }
    
  4. Copy the publisherCertificateName value into the Publisher box and copy the packageIdentityName value into the Name box of the Add apps blade.

    Important

    The JSON file might also return a windowsPhoneLegacyId value for both the Publisher Name and Product Name boxes. This means that you have an app that’s using a XAP package and that you must set the Product Name as windowsPhoneLegacyId, and set the Publisher Name as CN= followed by the windowsPhoneLegacyId.

    For example:
    {
    "windowsPhoneLegacyId": "ca05b3ab-f157-450c-8c49-a1f127f5e71d",
    }

To find the publisher and product name values for apps installed on Windows 10 mobile phones

  1. If you need to add mobile apps that aren't distributed through the Microsoft Store for Business, you must use the Windows Device Portal feature.

    Note

    Your PC and phone must be on the same wireless network.

  2. On the Windows Phone, go to Settings, choose Update & security, and then choose For developers.

  3. In the For developers screen, turn on Developer mode, turn on Device Discovery, and then turn on Device Portal.

  4. Copy the URL in the Device Portal area into your device's browser, and then accept the SSL certificate.

  5. In the Device discovery area, press Pair, and then enter the PIN into the website from the previous step.

  6. On the Apps tab of the website, you can see details for the running apps, including the publisher and product names.

  7. Start the app for which you're looking for the publisher and product name values.

  8. Copy the publisherCertificateName value and paste it into the Publisher Name box and the packageIdentityName value into the Product Name box of Intune.

    Important

    The JSON file might also return a windowsPhoneLegacyId value for both the Publisher Name and Product Name boxes. This means that you have an app that’s using a XAP package and that you must set the Product Name as windowsPhoneLegacyId, and set the Publisher Name as CN= followed by the windowsPhoneLegacyId.

    For example:
    {
    "windowsPhoneLegacyId": "ca05b3ab-f157-450c-8c49-a1f127f5e71d",
    }

Add a Desktop app to your Allowed apps list

For this example, we’re going to add WordPad, a Desktop app, to the Allowed apps list.

To add a Desktop app

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Allowed apps from the menu that appears.

    The Allowed apps blade appears, showing you any apps that are already included in the list for this policy.

  2. From the Allowed apps blade, click Add apps.

  3. On the Add apps blade, click Desktop apps from the dropdown list.

    The blade changes to show boxes for you to add the following, based on the results you want returned:

    Field Manages
    All fields marked as “*” All files signed by any publisher. (Not recommended)
    Name A friendly name for your app. You can't use this field by itself. However, you can use it in conjunction with any of the other fields.
    Publisher (required) only Filling out this field, gives you all files signed by the named publisher. This might be useful if your company is the publisher and signer of internal line-of-business apps.

    This is a required field and must be filled out whether by itself or in conjunction with other fields.
    Publisher (required) and Product name only If you only fill out these fields, you’ll get all files for the specified product, signed by the named publisher.
    Publisher (required), Product name, and File only If you only fill out these fields, you’ll get any version of the named file or package for the specified product, signed by the named publisher.
    Publisher (required), Product name, File, and Min version only If you only fill out these fields, you’ll get the specified version or newer releases of the named file or package for the specified product, signed by the named publisher.

    This option is recommended for enlightened apps that weren't previously enlightened.
    Publisher (required), Product name, File, and Max version only If you only fill out these fields, you’ll get the specified version or older releases of the named file or package for the specified product, signed by the named publisher.
    All fields completed If you fill out all fields, you’ll get the specified version of the named file or package for the specified product, signed by the named publisher.
  4. After you’ve entered the info into the fields, click OK to add the app to your Allowed apps list, and then click Save to save the Allowed apps list to your policy.

    Note

    To add multiple Desktop apps at the same time, you can click the menu (…) at the end of the app row, and then continue to add more apps. When you’re done, click OK.

    Microsoft Intune management console: Adding Desktop app info

Find the Publisher and File name for Desktop apps

If you’re unsure about what to include for the publisher, you can run this PowerShell command:

Get-AppLockerFileInformation -Path "<path_of_the_exe>"

Where "<path_of_the_exe>" goes to the location of the app on the device. For example, Get-AppLockerFileInformation -Path "C:\Program Files\Windows NT\Accessories\wordpad.exe".

In this example, you'd get the following info:

Path                   Publisher
----                   ---------
%PROGRAMFILES%\WINDOWS NT\ACCESSORIES\WORDPAD.EXE O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US

Where the text, O=MICROSOFT CORPORATION, L=REDMOND, S=WASHINGTON, C=US is the publisher name to enter into the Publisher box and WORDPAD.EXE is the text to enter into the File box.

Import a list of apps to your Allowed apps list

For this example, we’re going to add an AppLocker XML file to the Allowed apps list. You’ll use this option if you want to add multiple apps at the same time. For more info about AppLocker, see the AppLocker content.

To create a list of Allowed apps using the AppLocker tool

  1. Open the Local Security Policy snap-in (SecPol.msc).

  2. In the left blade, expand Application Control Policies, expand AppLocker, and then click Packaged App Rules.

    Local security snap-in, showing the Packaged app Rules

  3. Right-click in the right-hand blade, and then click Create New Rule.

    The Create Packaged app Rules wizard appears.

  4. On the Before You Begin page, click Next.

    Create Packaged app Rules wizard, showing the Before You Begin page

  5. On the Permissions page, make sure the Action is set to Allow and the User or group is set to Everyone, and then click Next.

    Create Packaged app Rules wizard, showing the Before You Begin page

  6. On the Publisher page, click Select from the Use an installed packaged app as a reference area.

    Create Packaged app Rules wizard, showing the Publisher

  7. In the Select applications box, pick the app that you want to use as the reference for your rule, and then click OK. For this example, we’re using Microsoft Dynamics 365.

    Create Packaged app Rules wizard, showing the Select applications page

  8. On the updated Publisher page, click Create.

    Create Packaged app Rules wizard, showing the Microsoft Dynamics 365 on the Publisher page

  9. Click No in the dialog box that appears, asking if you want to create the default rules. You must not create default rules for your WIP policy.

    Create Packaged app Rules wizard, showing the Microsoft Dynamics 365 on the Publisher page

  10. Review the Local Security Policy snap-in to make sure your rule is correct.

    Local security snap-in, showing the new rule

  11. In the left blade, right-click on AppLocker, and then click Export policy.

    The Export policy box opens, letting you export and save your new policy as XML.

    Local security snap-in, showing the Export Policy option

  12. In the Export policy box, browse to where the policy should be stored, give the policy a name, and then click Save.

    The policy is saved and you’ll see a message that says 1 rule was exported from the policy.

    Example XML file
    This is the XML file that AppLocker creates for Microsoft Dynamics 365.

        <?xml version="1.0"?>
        <AppLockerPolicy Version="1">
            <RuleCollection EnforcementMode="NotConfigured" Type="Appx">
                <FilePublisherRule Action="Allow" UserOrGroupSid="S-1-1-0" Description="" Name="Microsoft.MicrosoftDynamicsCRMforWindows10, version 3.2.0.0 and above, from Microsoft Corporation" Id="3da34ed9-aec6-4239-88ba-0afdce252ab4">
                    <Conditions>
                        <FilePublisherCondition BinaryName="*" ProductName="Microsoft.MicrosoftDynamicsCRMforWindows10" PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US">
                            <BinaryVersionRange HighSection="*" LowSection="3.2.0.0"/>
                        </FilePublisherCondition>
                    </Conditions>
                </FilePublisherRule>
            </RuleCollection>
            <RuleCollection EnforcementMode="NotConfigured" Type="Dll"/>
            <RuleCollection EnforcementMode="NotConfigured" Type="Exe"/>
            <RuleCollection EnforcementMode="NotConfigured" Type="Msi"/>
            <RuleCollection EnforcementMode="NotConfigured" Type="Script"/>
        </AppLockerPolicy>
    
  13. After you’ve created your XML file, you need to import it by using Microsoft Intune.

To import your list of Allowed apps using Microsoft Intune

  1. From the Allowed apps area, click Import apps.

    The blade changes to let you add your import file.

    Microsoft Intune, Importing your AppLocker policy file using Intune

  2. Browse to your exported AppLocker policy file, and then click Open.

    The file imports and the apps are added to your Allowed app list.

Add exempt apps to your policy

If you're running into compatibility issues where your app is incompatible with WIP, but still needs to be used with enterprise data, you can exempt the app from the WIP restrictions. This means that your apps won't include auto-encryption or tagging and won't honor your network restrictions. It also means that your exempted apps might leak.

To exempt a Store app, a Desktop app, or an AppLocker policy file from the Allowed apps list

  1. From the App policy blade, click the name of your policy, and then click Exempt apps from the menu that appears.

    The Exempt apps blade appears, showing you any apps that are already included in the list for this policy.

  2. From the Exempt apps blade, click Add apps.

    Be aware that when you exempt apps, they’re allowed to bypass the WIP restrictions and access your corporate data. To allow apps, see the Add app rules to your policy section of this topic.

  3. Fill out the rest of the app info, based on the type of app you’re adding:

  4. Click OK.

Manage your Required settings

In the Required settings blade you must pick your Windows Information Protection mode and you can review or change your Corporate identity.

Manage the WIP protection mode for your enterprise data

After you've added the apps you want to protect with WIP, you'll need to apply a management and protection mode.

We recommend that you start with Silent or Allow Overrides while verifying with a small group that you have the right apps on your allowed apps list. After you're done, you can change to your final enforcement policy, Hide Overrides.

Note

For info about how to collect your audit log files, see How to collect Windows Information Protection (WIP) audit event logs.

To add your protection mode

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Required settings from the menu that appears.

    The Required settings blade appears.

    Microsoft Intune, Required settings blade showing Windows Information Protection mode

    Mode Description
    Hide Overrides WIP looks for inappropriate data sharing practices and stops the employee from completing the action. This can include sharing info across non-enterprise-protected apps in addition to sharing enterprise data between other people and devices outside of your enterprise.
    Allow Overrides WIP looks for inappropriate data sharing, warning employees if they do something deemed potentially unsafe. However, this management mode lets the employee override the policy and share the data, logging the action to your audit log. For info about how to collect your audit log files, see How to collect Windows Information Protection (WIP) audit event logs.
    Silent WIP runs silently, logging inappropriate data sharing, without blocking anything that would’ve been prompted for employee interaction while in Allow Override mode. Unallowed actions, like apps inappropriately trying to access a network resource or WIP-protected data, are still stopped.
    Off (not recommended) WIP is turned off and doesn't help to protect or audit your data.

    After you turn off WIP, an attempt is made to decrypt any WIP-tagged files on the locally attached drives. Be aware that your previous decryption and policy info isn’t automatically reapplied if you turn WIP protection back on.
  2. Click Save.

Define your enterprise-managed corporate identity

Corporate identity, usually expressed as your primary Internet domain (for example, contoso.com), helps to identify and tag your corporate data from apps you’ve marked as protected by WIP. For example, emails using contoso.com are identified as being corporate and are restricted by your Windows Information Protection policies.

Starting with Windows 10, version 1703, Intune automatically determines your corporate identity and adds it to the Corporate identity field.

To change your corporate identity

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Required settings from the menu that appears.

    The Required settings blade appears.

  2. If the auto-defined identity isn’t correct, you can change the info in the Corporate identity field. If you need to add additional domains, for example your email domains, you can do it in the Advanced settings area.

    Microsoft Intune, Set your corporate identity for your organization

Manage your Advanced settings

In the Advanced settings blade you must specify where apps can access your corporate data, upload a Data Recovery Agent (DRA) certificate, and set several optional data protection and access settings.

Choose where apps can access enterprise data

After you've added a protection mode to your apps, you'll need to decide where those apps can access enterprise data on your network.

There are no default locations included with WIP, you must add each of your network locations. This area applies to any network endpoint device that gets an IP address in your enterprise’s range and is also bound to one of your enterprise domains, including SMB shares. Local file system locations should just maintain encryption (for example, on local NTFS, FAT, ExFAT).

Important

Every WIP policy should include policy that defines your enterprise network locations.
Classless Inter-Domain Routing (CIDR) notation isn’t supported for WIP configurations.

To define where your allowed apps can find and send enterprise data on you network

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Advanced settings from the menu that appears.

    The Advanced settings blade appears.

  2. Click Add network boundary from the Network perimeter area.

    The Add network boundary blade appears.

    Microsoft Intune, Set where your apps can access enterprise data on your network

  3. Select the type of network boundary to add from the Boundary type box.

  4. Type a name for your boundary into the Name box, add your values to the Value box, based on the following options, and then click OK.

    Boundary type Value format Description
    Cloud Resources With proxy: contoso.sharepoint.com,contoso.internalproxy1.com|
    contoso.visualstudio.com,contoso.internalproxy2.com

    Without proxy: contoso.sharepoint.com|contoso.visualstudio.com
    Specify the cloud resources to be treated as corporate and protected by WIP.

    For each cloud resource, you may also optionally specify a proxy server from your Internal proxy servers list to route traffic for this cloud resource. Be aware that all traffic routed through your Internal proxy servers is considered enterprise.

    If you have multiple resources, you must separate them using the "|" delimiter. If you don’t use proxy servers, you must also include the "," delimiter just before the "|". For example: URL <,proxy>|URL <,proxy>.

    Important
    In some cases, such as when an app connects directly to a cloud resource through an IP address, Windows can’t tell whether it’s attempting to connect to an enterprise cloud resource or to a personal site. In this case, Windows blocks the connection by default. To stop Windows from automatically blocking these connections, you can add the /*AppCompat*/ string to the setting. For example: URL <,proxy>|URL <,proxy>|/*AppCompat*/.

    When using this string, we recommend that you also turn on Azure Active Directory Conditional Access, using the Domain joined or marked as compliant option, which blocks apps from accessing any enterprise cloud resources that are protected by conditional access.
    Network domain names corp.contoso.com,region.contoso.com Starting with Windows 10, version 1703, this field is optional.

    Specify the DNS suffixes used in your environment. All traffic to the fully-qualified domains appearing in this list will be protected.

    If you have multiple resources, you must separate them using the "," delimiter.
    Proxy servers proxy.contoso.com:80;proxy2.contoso.com:443 Specify the proxy servers your devices will go through to reach your cloud resources. Using this server type indicates that the cloud resources you’re connecting to are enterprise resources.

    This list shouldn’t include any servers listed in your Internal proxy servers list. Internal proxy servers must be used only for WIP-protected (enterprise) traffic.

    If you have multiple resources, you must separate them using the ";" delimiter.
    Internal proxy servers contoso.internalproxy1.com;contoso.internalproxy2.com Specify the internal proxy servers your devices will go through to reach your cloud resources. Using this server type indicates that the cloud resources you’re connecting to are enterprise resources.

    This list shouldn’t include any servers listed in your Proxy servers list. Proxy servers must be used only for non-WIP-protected (non-enterprise) traffic.

    If you have multiple resources, you must separate them using the ";" delimiter.
    IPv4 ranges Starting IPv4 Address: 3.4.0.1
    Ending IPv4 Address: 3.4.255.254
    Custom URI: 3.4.0.1-3.4.255.254,
    10.0.0.1-10.255.255.254
    Starting with Windows 10, version 1703, this field is optional.

    Specify the addresses for a valid IPv4 value range within your intranet. These addresses, used with your Network domain names, define your corporate network boundaries.

    If you have multiple ranges, you must separate them using the "," delimiter.
    IPv6 ranges Starting IPv6 Address: 2a01:110::
    Ending IPv6 Address: 2a01:110:7fff:ffff:ffff:ffff:ffff:ffff
    Custom URI: 2a01:110:7fff:ffff:ffff:ffff:ffff:ffff,
    fd00::-fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    Starting with Windows 10, version 1703, this field is optional.

    Specify the addresses for a valid IPv6 value range within your intranet. These addresses, used with your Network domain names, define your corporate network boundaries.

    If you have multiple ranges, you must separate them using the "," delimiter.
    Neutral resources sts.contoso.com,sts.contoso2.com Specify your authentication redirection endpoints for your company.

    These locations are considered enterprise or personal, based on the context of the connection before the redirection.

    If you have multiple resources, you must separate them using the "," delimiter.
  5. Repeat steps 1-4 to add any additional network boundaries.

  6. Decide if you want to Windows to look for additional network settings:

    Microsoft Intune, Choose if you want Windows to search for additional proxy servers or IP ranges in your enterprise

    • Enterprise Proxy Servers list is authoritative (do not auto-detect). Click On for Windows to treat the proxy servers you specified in the network boundary definition as the complete list of proxy servers available on your network.Click Off and Windows searches for additional proxy servers in your immediate network.

    • Enterprise IP Ranges list is authoritative (do not auto-detect). Click On for Windows to treat the IP ranges you specified in the network boundary definition as the complete list of IP ranges available on your network. Click Off and Windows searches for additional IP ranges on any domain-joined devices connected to your network.

Upload your Data Recovery Agent (DRA) certificate

After you create and deploy your WIP policy to your employees, Windows begins to encrypt your corporate data on the employees’ local device drive. If somehow the employees’ local encryption keys get lost or revoked, the encrypted data can become unrecoverable. To help avoid this possibility, the Data Recovery Agent (DRA) certificate lets Windows use an included public key to encrypt the local data while you maintain the private key that can unencrypt the data.

Important

Using a DRA certificate isn’t mandatory. However, we strongly recommend it. For more info about how to find and export your data recovery certificate, see the Data Recovery and Encrypting File System (EFS) topic. For more info about creating and verifying your EFS DRA certificate, see the Create and verify an Encrypting File System (EFS) Data Recovery Agent (DRA) certificate topic.

To upload your DRA certificate

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Advanced settings from the menu that appears.

    The Advanced settings blade appears.

  2. In the Upload a Data Recovery Agent (DRA) certificate to allow recovery of encrypted data box, click Browse to add a data recovery certificate for your policy.

    Microsoft Intune, Upload your Data Recovery Agent (DRA) certificate

After you've decided where your protected apps can access enterprise data on your network, you’ll be asked to decide if you want to add any optional WIP settings.

To set your optional settings

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Advanced settings from the menu that appears.

    The Advanced settings blade appears.

  2. Choose to set any or all optional settings:

    Microsoft Intune, Choose if you want to include any of the optional settings

    • Prevent corporate data from being accessed by apps when the device is locked. Applies only to Windows 10 Mobile. Determines whether to encrypt enterprise data using a key that's protected by an employee's PIN code on a locked device. Apps won't be able to read corporate data when the device is locked. The options are:

      • On (recommended). Turns on the feature and provides the additional protection.

      • Off Doesn't enable this feature.

    • Revoke encryption keys on unenroll. Determines whether to revoke a user’s local encryption keys from a device when it’s unenrolled from Windows Information Protection. If the encryption keys are revoked, a user no longer has access to encrypted corporate data. The options are:

      • On (recommended). Revokes local encryption keys from a device during unenrollment.

      • Off. Stop local encryption keys from being revoked from a device during unenrollment. For example if you’re migrating between Mobile Device Management (MDM) solutions.

    • Revoke access to protected data when the device enrolls to MDM. Determines whether to revoke a user's WIP keys when a device is upgraded from MAM to a higher-security MDM solution. The options are:

      • On. Revokes the encryption keys from a device when it's upgraded from MAM to MDM.

      • Off. Encryption keys aren't removed and the user can continue to access protected files. This is the recommended setting if the MDM service uses the same WIP EnterpriseID value as the MAM service.

    • Show the enterprise data protection icon. Determines whether an icon appears on corporate files in the Save As and File Explorer views. The options are:

      • On. Allows an icon to appear on corporate files in the Save As and File Explorer views. Additionally, for unenlightened but allowed apps, the icon also appears on the app tile and with Managed text on the app name in the Start menu.

      • Off (recommended). Stops the icon from appearing on corporate files or unenlightened, but allowed apps. By default, this is turned off.

    • Use Azure RMS for WIP. Determines whether to use Azure Rights Management encryption with Windows Information Protection. The options are:

      • On. Starts using Azure Rights Management encryption with WIP. By turning this option on, you can also add a TemplateID GUID to specify who can access the Azure Rights Management protected files, and for how long. For more info about setting up Azure Rights management and using a template ID with WIP, see the Choose to set up Azure Rights Management with WIP section of this topic.

      • Off. Stops using Azure Rights Management encryption with WIP.

    • MDM discovery URL. Lets the Windows Settings > Accounts > Access work or school sign-in offer an Upgrade to MDM link. Additionally, this lets you switch to another MDM provider, so that Microsoft Intune can manage MAM, while the new MDM provider manages the MDM devices. By default, this is specified to use Microsoft Intune.

Choose to set up Azure Rights Management with WIP

WIP can integrate with Microsoft Azure Rights Management to enable secure sharing of files by using removable drives such as USB drives. For more info about Azure Rights Management, see Microsoft Azure Rights Management. To integrate Azure Rights Management with WIP, you must already have Azure Rights Management set up.

To configure WIP to use Azure Rights Management, you must set the AllowAzureRMSForEDP MDM setting to 1 in Microsoft Intune. This setting tells WIP to encrypt files copied to removable drives with Azure Rights Management, so they can be shared amongst your employees on computers running at least Windows 10, version 1703.

Optionally, if you don’t want everyone in your organization to be able to share your enterprise data, you can set the RMSTemplateIDForEDP MDM setting to the TemplateID of the Azure Rights Management template used to encrypt the data. You must make sure to mark the template with the EditRightsData option.

Note

For more info about setting the AllowAzureRMSForEDP and the RMSTemplateIDForEDP MDM settings, see the EnterpriseDataProtection CSP topic. For more info about setting up and using a custom template, see Configuring custom templates for the Azure Rights Management service topic.

Choose whether to use and configure Windows Hello for Business

You can turn on Windows Hello for Business, letting your employees use it as a sign-in method for their devices.

To turn on and configure Windows Hello for Business

  1. From the Mobile apps - App protection policies blade, click the name of your policy, and then click Advanced settings from the menu that appears.

    The Advanced settings blade appears.

  2. Choose to turn on and configure the Windows Hello for Business settings:

    Microsoft Intune, Choose to use Windows Hello for Business

    • Use Windows Hello for Business as a method for signing into Windows. Turns on Windows Hello for Business. The options are:

      • On. Turns on Windows Hello For Business for anyone assigned to this policy.

      • Off. Turns off Windows Hello for Business.

    • Set the minimum number of characters required for the PIN. Enter a numerical value (4-127 characters) for how many characters must be used to create a valid PIN. Default is 4 characters.

    • Configure the use of uppercase letters in the Windows Hello for Business PIN. Lets you decide whether uppercase letters can be used in a valid PIN. The options are:

      • Allow the use of uppercase letters in PIN. Lets an employee use uppercase letters in a valid PIN.

      • Require the use of at least one uppercase letter in PIN. Requires an employee to use at least 1 uppercase letter in a valid PIN.

      • Do not allow the use of uppercase letters in PIN. Prevents an employee from using uppercase letters in a valid PIN.

    • Configure the use of lowercase letters in the Windows Hello for Business PIN. Lets you decide whether lowercase letters can be used in a valid PIN. The options are:

      • Allow the use of lowercase letters in PIN. Lets an employee use lowercase letters in a valid PIN.

      • Require the use of at least one lowercase letter in PIN. Requires an employee to use at least 1 lowercase letter in a valid PIN.

      • Do not allow the use of lowercase letters in PIN. Prevents an employee from using lowercase letters in a valid PIN.

    • Configure the use of special characters in the Windows Hello for Business PIN. Lets you decide whether special characters can be used in a valid PIN. The options are:

      • Allow the use of special characters in PIN. Lets an employee use special characters in a valid PIN.

      • Require the use of at least one special character in PIN. Requires an employee to use at least 1 special character in a valid PIN.

      • Do not allow the use of special characters in PIN. Prevents an employee from using special characters in a valid PIN.

    • Specify the period of time (in days) that a PIN can be used before the system requires the user to change it. Enter a numerical value (0-730 days) for how many days can pass before a PIN must be changed. If you enter a value of 0, the PIN never expires.

    • Specify the number of past PINs that can be associated to a user account that can't be reused. Enter a numerical value (0-50 days) for how many days can pass before an employee can reuse a previous PIN. If you enter a value of 0, a PINs can be reused immediately and past PINs aren't stored.

      Note

      PIN history is not preserved through a PIN reset.

    • Number of authentication failures allowed before the device will be wiped. Enter a numerical value for how many times the PIN can be incorrectly entered before wiping the device of corporate data. If you enter a value of 0, the device is never wiped, regardless of the number of incorrect PIN entries.

      This setting has different behavior for mobile devices and desktops.

      • On mobile devices. When an employee reaches the value set here, the device is wiped of corporate data.

      • On desktop devices. When an employee reaches the value set here, the desktop is put into BitLocker recovery mode, instead of being wiped. You must have BitLocker installed on the device or this setting is ignored.

    • Maximum amount of time (in minutes) allowed after the device is idle that will cause the device to become PIN or password locked. Enter a numerical value for how many days can pass before a PIN must be changed. If you enter a value of 0, the device never becomes PIN or password locked while idle.

      Note

      You can set this value to be anything; however, it can't be longer than the time specified by the Settings app. If you exceed the maximum timeout value, this setting is ignored.

Deploy your policy

After you’ve created your policy, you'll need to deploy it to your employees. MAM is deployed to users and not devices.

To deploy your policy

  1. On the Mobile apps - App protection policies pane, click your newly-created policy, click Assignments from the menu that appears, and then click Select groups.

    A list of user groups, made up of all of the security groups in your Azure Active Directory, appear in the Add user group pane.

  2. Choose the group you want your policy to apply to, and then click Select to deploy the policy.

    The policy is deployed to the selected group.

    Microsoft Intune, Pick your user groups that should get the policy when it's deployed