AIP Client versions blockers (urgent)

Question

1. Why our company version of the AIP client removes the “Documents Summary Information” and the “Summary Information” streams in an encrypted package whereas newer but also older versions do not do this?
2. Are there settings in the unified labelling client which can trigger this behavior, and can the MIP SDK be parametrized to also create this behavior?
3. What happens if our company upgrades from their version of the UL client to the built-in client of Office? What happens to the labels? Can they be read by the built-in version?

Answer 1

It seems like you are dealing with specific issues related to the Azure Information Protection (AIP) client, Unified Labeling (UL) client, and the Microsoft Information Protection (MIP) SDK. These tools are used for data protection and classification in organizations. Let's address each of your questions:

Removal of Document Summary Information and Summary Information Streams:

• The behavior you described might be influenced by the settings in the Unified Labeling client or specific configurations in your organization's deployment. It's also possible that the version of the AIP client you are using has specific modifications or customizations.
• Check the settings in the Unified Labeling client and any policies or configurations applied that might affect how metadata is handled during encryption.

MIP SDK Parametrization:

• The MIP SDK allows developers to build custom solutions for information protection. However, it's important to note that the behavior you're describing might not be a standard feature and could be specific to your organization's implementation or modifications.
• Consult the MIP SDK documentation and your organization's development or configuration documentation to see if there are parameters or settings that control the removal of specific metadata during encryption.

Upgrading from Company UL Client to Office Built-in Client:

• When upgrading from a company-specific Unified Labeling client to the built-in client in Office, there can be considerations related to label compatibility and features.
• Labels created with the company-specific UL client may not be fully compatible with the built-in client. It depends on the label policies, configurations, and versions.
• It's recommended to test the migration in a controlled environment to ensure a smooth transition. The impact on labels needs to be carefully evaluated, and adjustments may be required.

1. Label Readability by Built-in Version:
   • The built-in Office client should be able to recognize and display labels created with the company-specific UL client, provided that the necessary policies and configurations Puppe are consistent.
     • However, the level of integration and features supported by the built-in client may differ from those in a custom or company-specific UL client.

For more detailed and accurate information related to your specific setup, I recommend reaching out to Microsoft support or your organization's IT support. They can provide insights into the specific configurations, policies, and behaviors related to the AIP client, Unified Labeling, and MIP SDK in your environment.