Blog Post

Microsoft Security Community Blog
1 MIN READ

Fixing "Failed to parse the acquired Compliance Policy" Error

Tom_Moser's avatar
Tom_Moser
Icon for Microsoft rankMicrosoft
Oct 08, 2018

You've downloaded the MIP SDK and are running the sample applications. You use the file sample to try to list all labels, but you get:

 

Something bad happend: Failed to parse the acquired Compliance Policy. Failed with: [class mip::CompliancePolicyParserException] Tag not found : policy, NodeType: 15, Name: No Name Found, Value: , Ancestors: <SyncFile><Content>, correlationId:[34668a40-bb6a-4ef8-b2af-00005aa67409]

 

This indicates that you haven't migrated your labels from Azure Information Protection to the unified labeling experience! Follow this Docs article to migrate the labels, then create a Label Policy in Office 365 Security and Compliance Center. Once that's complete, the sample will run successfully.

 

Tom Moser, @milt0r, Sr. Program Manager – Azure Information Protection

Updated May 11, 2021
Version 7.0

3 Comments

  • Hi Tom,

    After eliminating this compliance policy parse error, I am getting this error-

    libc++abi.dylib: terminating with uncaught exception of type mip::NoPolicyError: Compliance policy not configured: missing <policy> tag, correlationId:[7fff415c-1364-4901-8989-00001481f60e]

    Abort trap: 6

     

    Abhijeet

  • I've seen this before when you have duplicate label names. Can you check to see if you have any AIP labels or retention labels that have the same name? 

     

  • Peter Bradley's avatar
    Peter Bradley
    Copper Contributor

    Hi Tom,

     

    The Docs article you linked to is failing at step 2 (Azure Information Protection - Unified labeling blade, select Activate).

    When we try to activate Unified labelling, it seems to always fail:

     

     

    Error - Migration Failed
    Unified labeling (Preview): Not activated

    Failed to complete migration to the unified labeling store.
    Please retry later, or contact Microsoft Support and include the following correlation ID: 'b2e0df49-b7a9-4ff0-8d45-76ae1347e008'
     
     
    Is there any guidance you can offer to get through this issue?
     
    Thanks, Peter