DataProtectionManager.UnprotectAsync(IBuffer) Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
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.
Removes the protection to an enterprise identity from a buffer.
public:
static IAsyncOperation<BufferProtectUnprotectResult ^> ^ UnprotectAsync(IBuffer ^ data);/// [Windows.Foundation.Metadata.RemoteAsync]
static IAsyncOperation<BufferProtectUnprotectResult> UnprotectAsync(IBuffer const& data);[Windows.Foundation.Metadata.RemoteAsync]
public static IAsyncOperation<BufferProtectUnprotectResult> UnprotectAsync(IBuffer data);function unprotectAsync(data)Public Shared Function UnprotectAsync (data As IBuffer) As IAsyncOperation(Of BufferProtectUnprotectResult)Parameters
- data
- IBuffer
The buffer to be unprotected.
Returns
When the call to this method completes successfully, it returns a BufferProtectUnprotectResult object that contains the status of the unprotected buffer.
- Attributes
Windows requirements
| App capabilities |
enterpriseDataPolicy
|
Remarks
UnprotectAsync never returns a status of Unprotected since it requires that the input resource be protected. (It is not possible to reliably verify that a resource is unprotected.) If your app compares the result to Unprotected, it contains a design flaw because it implies that it lost track of whether the buffer is protected.