microsoft / unifiedlabelingsupporttool

The 'Compliance Utility' is a powerful tool that helps troubleshoot and diagnose sensitivity labels, policies, settings and more. Whether you need to fix issues or reset configurations, this tool has you covered.

Compliance Utility

The 'Compliance Utility' is a powerful tool that helps troubleshoot and diagnose sensitivity labels, policies, settings and more. Whether you need to fix issues or reset configurations, this tool has you covered.

Have you ever used the Sensitivity button in a Microsoft 365 App or applied a sensitivity label by right-clicking on a file? If so, you've either used the Office's built-in labeling experience or the Purview Information Protection labeling client (previously 'Azure Information Protection unified labeling client'). If something is not working as expected with your DLP policies, sensitivity labels or you don't see any labels at all the 'Compliance Utility' will help you.

The online manual for the 'Compliance Utility' can be found here.

Caution

The Azure Information Protection (AIP) Unified Labeling add-in for Office has been retired on April 11th, 2024.

To continue using sensitivity labels powered by Microsoft Purview Information Protection in Office applications, you must transition to the built-in labeling experience in Microsoft 365 Apps.

Important retirement milestones:

• April 11th, 2024 - New Client: Release of the Microsoft Purview Information Protection client for preview on the Microsoft Download Center. This client version 3.0 does not include the AIP Add-in for Office. To continue using the Information Protection Scanner, Viewer and File Labeler, your organization must upgrade and deploy the new client package.
• April 11th, 2024 - Previous Client: AIP Unified Labeling add-in is retired and no longer in support. Extensions to continue using the AIP add-in are granted on a case-to-case basis; please reach out to Microsoft Support or your account team.
• May 2024: AIP Unified Labeling add-in permanently disabled in Office. AIP Unified Labeling add-in for Office clients will be blocked from using the add-in and download of label policy will fail for all clients without extensions.

What you need to do to prepare:

For detailed migration steps, refer to our playbook: From bolt-on to built-in – Migrate from Azure Information Protection Add-in.

For the announcement and FAQs of the retirement, refer to our blog: Retirement notification for the Azure Information Protection Unified Labeling add-in for Office.

Trademarks: This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft’s Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party’s policies.

Copyright © Microsoft Corporation.

unifiedlabelingsupporttool's Issues

Reset silent cancels with no action

Using the -Reset Silent option the log entries show the function being cancelled:
2022-07-06, 10:56, fncInitialize, OS edition, Microsoft Windows 10 Enterprise
2022-07-06, 10:56, fncInitialize, OS version, 10.0.19044.0
2022-07-06, 10:56, fncInitialize, OS 64-Bit, True
2022-07-06, 10:56, fncInitialize, Script module version, 3.0.3
2022-07-06, 10:56, fncInitialize, Username, ########
2022-07-06, 10:56, fncInitialize, Machine name, ###########
2022-07-06, 10:56, fncInitialize, PowerShell Host, ConsoleHost
2022-07-06, 10:56, fncInitialize, PowerShell Version, 5.1.19041.1682
2022-07-06, 10:56, fncInitialize, PowerShell Edition, Desktop
2022-07-06, 10:56, fncInitialize, PowerShell Current culture, en-US
2022-07-06, 10:56, fncInitialize, PowerShell Current UI culture, en-US
2022-07-06, 10:56, fncInitialize, Running privileged, True
2022-07-06, 10:56, UnifiedLabelingSupportTool, Parameter Reset, Triggered
2022-07-06, 10:56, fncReset, Reset Silent, Initiated
2022-07-06, 10:56, fncReset, Reset, Canceled

It would seem the variable $Private:ReadHost is not being set when the silent option is being used.