EnforcementLevel Enum

Definition

Namespace:

Windows.Security.EnterpriseData

Note

Starting in July 2022, Microsoft is deprecating Windows Information Protection (WIP) and the APIs that support WIP. Microsoft will continue to support WIP on supported versions of Windows. New versions of Windows won't include new capabilities for WIP, and it won't be supported in future versions of Windows. For more information, see Announcing sunset of Windows Information Protection.

For your data protection needs, Microsoft recommends that you use Microsoft Purview Information Protection and Microsoft Purview Data Loss Prevention. Purview simplifies the configuration set-up and provides an advanced set of capabilities.

A set of enumerated values together describing the possible Windows Information Protection (WIP) enforcement levels. WIP enforcement level is one aspect of mobile device management (MDM) policy configuration.

public enum class EnforcementLevel

/// [Windows.Foundation.Metadata.ContractVersion(Windows.Security.EnterpriseData.EnterpriseDataContract, 131072)]
enum class EnforcementLevel

[Windows.Foundation.Metadata.ContractVersion(typeof(Windows.Security.EnterpriseData.EnterpriseDataContract), 131072)]
public enum EnforcementLevel

var value = Windows.Security.EnterpriseData.EnforcementLevel.noProtection

Public Enum EnforcementLevel

Inheritance

Enum

EnforcementLevel

Attributes

ContractVersionAttribute

Windows requirements

Device family	Windows Desktop Extension SDK (introduced in 10.0.10586.0) Windows Mobile Extension SDK (introduced in 10.0.10586.0)
API contract	Windows.Security.EnterpriseData.EnterpriseDataContract (introduced in v2.0)

Fields

Name	Value	Description
NoProtection	0	The policy calls for no protection. Your app should disable WIP behavior if data is protected, and unprotect data.
Silent	1	The policy calls for silent protection. Your app should not prompt in response to an action such as pasting data into an unauthorized app. Instead, your app should silently allow the action, and audit it.
Override	2	The policy calls for the user to be allowed to override a warning message. In response to an attempted action such as pasting data into an unauthorized app, your app should prompt the user via an overridable warning message. If the user overrides, then your app should perform the action and audit it.
Block	3	The policy calls for the user to be blocked. In response to an attempted action such as pasting data into an unauthorized app, your app should block the action, and audit it.