Known issues - Azure Information Protection

Use the lists and tables below to find details about known issues and limitations related to Azure Information Protection features.

Other digital signing and encryption solutions

Azure Information Protection can't protect or decrypt files\emails that are digitally signed or encrypted with other solutions, such as removing protection from mails that are signed or encrypted with S/MIME.

Client support for container files, such as .zip files

Container files are files that include other files, with a typical example being .zip files that contain compressed files. Other examples include .rar, .7z, .msg files and PDF documents that include attachments.

You can classify and protect these container files, but the classification and protection isn't applied to each file inside the container.

If you have a container file that includes classified and protected files, you must first extract the files to change their classification or protection settings. However, you can remove the protection for all files in supported container files by using the Set-AIPFileLabel cmdlet.

Encryption for .msg files is supported in the MIP SDK only.

The Azure Information Protection viewer can't open attachments in a protected PDF document. In this scenario, when the document is opened in the viewer, the attachments aren't visible.

For more information, see Admin Guide: File types supported by the Azure Information Protection client.

Known issues for watermarks

When you're adding a watermark to a label, keep in mind that if you use font size one, it automatically adjusts to fit the page. However, if you use any other font size, it uses the size you specified in the font settings.

PowerShell support for the Azure Information Protection client

The current release of the AzureInformationProtection PowerShell module that's installed with the Azure Information Protection client has the following known issues:

• Outlook personal folders (.pst files). Natively protecting .pst files isn't supported using the AzureInformationProtection module.

• Outlook protected email message (.msg files with a .rpmsg attachment). Unprotecting Outlook protected email messages is supported by the AzureInformationProtection module for messages inside an Outlook personal folder (.pst file), or on disk in an Outlook message file (.msg file).

• PowerShell 7. Currently PowerShell 7 isn't supported by the AIP Client. Using PS7 results in the error: "Object reference not set to an instance of an object."

For more information, see Admin Guide: Using PowerShell with the Azure Information Protection client.

Known issues AIP Scanner authentication in version 2.16.73

If you're using version 2.16.73 of the AIP Scanner or installing it for the first time, you might encounter an error when trying to authenticate. The error message reads "Unable to authenticate and set up Azure Information Protection."

This issue is caused by a problem with MSAL authentication. To resolve it, you can add a registry key to the server.

Path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSIP

DWORD: AuthenticateUsingAdal

Value: 1

By adding this registry key, the Scanner authenticates using ADAL instead.

Known issues AIP Scanner

• Scanning of .msg files with signed PDF files is currently not supported.

• Sensitive Information Types (SIT) that are Trainable Classifiers and EDM (Exact Data Match) classifiers.

• Password protected files.

Known issues for co-authoring

Known issues for co-authoring are relevant only when co-authoring is enabled in your tenant.

Known issues for co-authoring in AIP include:

• Supported versions for co-authoring and sensitivity labels

• Policy updates

• Unsupported features for co-authoring

Supported versions for co-authoring and sensitivity labels

All apps, services, and operation tools in your tenant must support co-authoring.

Before you start, make sure that your system complies with the version requirements listed in the Microsoft 365 prerequisites for co-authoring.

We recommend that you always use the latest Office version available. Earlier versions might cause unexpected results, such as not being able to see labels in Azure Information Protection, or no policy enforcement.

Policy updates

If your labeling policy was updated while an Office application was opened with Azure Information Protection, any new labels are displayed, but applying them results in an error.

If this occurs, close and reopen your Office application to be able to apply your labels.

User interface changes when applying labels

When co-authoring is enabled in your tenant, the user experience for labels that are configured for user-defined permissions changes to the experience for built-in labels.

Instead of seeing the Azure Information Protection dialog box where users can select permission levels such as Viewer, Reviewer, and Only for me, they see the same dialog box as if they had they selected the File tab > Info > Protect Document > Restrict Access > Restricted Access. From this dialog box, they can specify their choice of permissions and users.

For more information, see the Word, PowerPoint, andCould you use contractions to make it less formal? Excel permissions section from the Microsoft Purview documentation.

Unsupported features for co-authoring

The following features aren't supported or are partially supported when co-authoring is enabled for files encrypted with sensitivity labels:

• DKE templates and DKE user-defined properties. For more information, see Double Key Encryption (DKE).

• This means that applying a label with user-defined permissions prevents you from working on the document with others at the same time.

• Removing external content marking in apps. External content marking is removed only when a label is applied, and not when the document is saved. For more information, see The client side of Azure Information Protection.

• Features listed in the Microsoft 365 documentation as co-authoring limitations.

• Labelbycustomproperties for mapping other labeling solutions won't work with co-auth enabled.

Sharing external doc types across tenants

When users share external doc types, such as PDFs, across tenants, recipients receive a consent prompt that requires them to accept the sharing of the listed permissions. For example:

Depending on your application, you might see this prompt repeatedly for the same document. When the prompt appears, select Accept to continue to the shared document.

Known issues in policies

Publishing policies might take up to 24 hours.

Known issues for the AIP viewer

• External users
• ADRMS protected files on Android devices

For more information, see Unified labeling client: View protected files with the Azure Information Protection viewer.

External users and the AIP viewer

If an external user already has a guest account in Microsoft Entra ID, the AIP Viewer might display an error when the user opens a protected document, telling them that they can't sign in with a personal account.

If such an error appears, the user must install Adobe Acrobat DC with the MIP extension in order to open the protected document.

When a user opens the protected document after installing Adobe Acrobat DC with the MIP extension, that user might still see an error showing that the selected user account doesn't exist in the tenant, and prompting them to select an account.

This is an expected error. In the prompt window, select Back to continue opening the protected document.

ADRMS protected files on Android devices

On Android devices, ADRMS-protected files can't be opened by the AIP Viewer app.

Known issues for track and revoke features

Tracking and revoking document access using the unified labeling client has the following known issues:

• Password-protected documents

• Documents accessed via SharePoint or OneDrive

For more information, see the Admin Guide and User Guide procedures.

Password-protected documents

Password-protected documents aren't supported by track and revoke features.

Documents accessed via SharePoint or OneDrive

• Protected documents that are uploaded to SharePoint or OneDrive lose their ContentID value, and access can't be tracked or revoked.

• If a user downloads the file from SharePoint or OneDrive and accesses it from their local machine, a new ContentID is applied to the document when they open it locally.

  Using the original ContentID value to track data won't include any access performed for the user's downloaded file. Additionally, revoking access based on the original ContentID value won't revoke access for any of the downloaded files.

  If administrators have access to the downloaded files, they can use PowerShell to identify a document's ContentID for track and revoke actions.

Known issues for the AIP client and OneDrive

If you have documents stored in OneDrive with a sensitivity label applied, and an administrator changes the label in the labeling policy to add protection, the newly applied protection isn't automatically applied to the labeled document.

In such cases, relabel the document manually to apply the protection as needed.

AIP-based Conditional Access policies

External users who receive content protected by Conditional Access policies must have a Microsoft Entra business-to-business (B2B) collaboration guest user account in order to view the content.

While you can invite external users to activate a guest user account, allowing them to authenticate and pass the conditional access requirements, it might be difficult to ensure that this occurs for all external users required.

We recommend enabling AIP-based conditional access policies for your internal users only.

Enable conditional access policies for AIP for internal users only:

1. In the Azure portal, navigate to the Conditional Access blade, and select the conditional access policy you wish to modify.
2. Under Assignments, select Users and groups, and then select All users. Make sure that the All guest and external users option is not selected.
3. Save your changes.

You can also entirely disable/exclude CA within Azure Information Protection if the functionality isn't required for your organization, in order to avoid this potential issue.

For more information, see the Conditional Access documentation.

Can't publish or use labels with sub-labels as standalone labels

If a label contains any sub-labels in the Microsoft Purview compliance portal, this label must not be published as a standalone label to any AIP users.

Similarly, AIP doesn�t support labels that contain sub-labels as default labels, and you can't configure automatic labeling for these labels.

Additionally, using a label with UDP (User Defined Permissions) as a default label isn't supported in the Unified Labeling Client.

More information

The following additional articles might be helpful in answering questions you have about Azure Information Protection:

• File types supported by the Azure Information Protection unified labeling client
• Frequently asked questions for Azure Information Protection
• Frequently asked questions about data protection in Azure Information Protection
• Frequently asked questions about classification and labeling in Azure Information Protection