Auto labelling with InformationProtectionLabelId

Hi @Catarina Machado,

Thanks for reaching out to Microsoft Q&A Forum support.

I understand that you're having the issue of auto-labeling using the InformationProtectionLabelId property in Microsoft Purview.
I’ve reviewed your scenario and also followed up on related discussions and documentation to help clarify the issue. You can check out this relevant discussion and engage directly with the author here:

Link: Sensitivity Auto-labelling via Document Property | Microsoft Community Hub

To inform you more clearly about this topic, here’s a summary of the insights shared by Microsoft Forum contributors and moderators:

Auto-labeling based on document properties such as InformationProtectionLabelId is supported, but it requires precise configuration. This includes:

• Correct GUID formatting (e.g., ensuring a space after the colon in GUID: 1234).
• Mapping the custom property to a SharePoint Search Managed Property to ensure its indexed and detectable by the auto-labeling engine.
• Understanding that auto-labeling does not override manually applied labels and may not apply to documents created before the policy was enabled unless they are edited.

I also found another discussion confirming that auto-labeling policies may fail in simulation mode if the metadata is not properly indexed or if encryption settings interfere with detection:

Link: Auto-Labeling based on data in Document Properties doesn't work | Microsoft Community Hub

As a forum moderator, I’m here to help guide discussions and share information based on Microsoft documentation and community knowledge. However, I don’t have access to internal product insights or the ability to provide a precise answer from a developer perspective.

In case the Tech Community answer doesn’t fully address your concerns, I’d recommend following up directly on that thread to ask for clarification. And if you still need a more definitive answer, the best next step would be to Raise Support ticket via https://admin.microsoft.com/#/support/requests because our technical team can contact you directly via call or meeting to troubleshoot issue faster.

Additionally, here’s a quick clarification on the scope of support available:

• Raise Ticket via Admin Center: You can submit a free support ticket here, but it's primarily intended for issues directly related to Microsoft Purview functionality. It doesn’t cover development-related questions or architectural guidance.
• Microsoft Q&A: This forum is a great place for community-driven support and advice based on publicly available documentation and research. However, we don’t have access to internal databases or the ability to provide insights from the product engineering teams.

That said, the two most reliable paths forward are either checking the Tech Community post or create a post by yourself, which includes input from Microsoft engineers I believe they have enough technical knowledge to help you, or submitting a support ticket to connect directly with our technical team. This ensures you get the most accurate and authoritative answer, especially for more technical or complex scenarios. 

Hope you will solve the problem soon. 
Best Regard.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.