Modify Sensitivity Labels

Nancy Daniel 0 Reputation points
2026-08-13T13:09:43.55+00:00

My question is regarding the modification to some fields of the existing sensitivity labels in Microsoft Purview which have already been published in label policies. The Scope for the labels in question are - "****Files & other data assets, Email".

The modification we would want to do is for the following fields:

  • Change the Description of the labels
  • Removal of the Content marking (Header)

If we make the above mentioned changes, will we need to republish the label?

Scope and Access Controls for the sensitivity labels will remain as is.**

Are there any other considerations before doing so? I'd like confirmation as well as guidance on the steps for performing this change.

Thanks for your support!

Microsoft Security | Microsoft Purview
0 comments No comments

2 answers

Sort by: Most helpful
  1. Marcin Policht 102K Reputation points MVP Volunteer Moderator
    2026-08-13T13:49:52.16+00:00

    Nope - you do not need to republish the label policy if you only change the Description or remove the Content marking Header from an existing sensitivity label. The changes to the existing label propagate automatically - just allow up to 24 hours for replication and for Office clients/services to reflect the changes.

    To make the change, go to Microsoft Purview > Information Protection > Sensitivity labels, select the existing label, choose Edit label, and update the Description fields as required. Proceed to the Content marking section and remove/disable the Header configuration. Leave the existing Scope and Access Controls unchanged, review the configuration, and select Save label.

    The main consideration is existing content. Removing the Header from the label definition does not automatically remove headers that were already applied to existing files or emails. It prevents the header from being applied when the label is subsequently applied or reapplied. Therefore, test both newly labeled content and existing labeled content.

    Also allow for propagation and client caching. Changes may appear within minutes but can take up to 24 hours. If a client does not reflect the change, restarting Office applications or signing out and back in can help. There is no need to create a new label or republish the label policy for these changes.


    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-08-13T13:10:02.3866667+00:00

    Yes. For an existing sensitivity label that is already published in a label policy, changing the label settings does not require creating a new policy or republishing the label.

    Supported guidance:

    1. In the Microsoft Purview portal, go to Information Protection > Sensitivity labels.
    2. Select the existing label.
    3. Select Edit label.
    4. Update the fields needed, such as:
      • the Description
      • the Content marking configuration, including removing the Header if that is currently configured on the label
    5. Complete the Edit sensitivity label configuration.

    After saving:

    • No extra publish or republish step is needed for the same users if the label is already included in an existing label policy.
    • The changes become available automatically to the same users and services.
    • Allow up to 24 hours for the changes to propagate across apps and services.

    Other considerations before making the change:

    • Since the label scope remains Files & other data assets and Emails, there is no indication that a policy change is required just for these edits.
    • Avoid creating a new label policy unless different users need different labels or different policy settings. The guidance is to keep the number of label policies as low as possible.
    • If multiple label policies apply to the same users, review policy order only if there is a possible conflict between policies.
    • Because label changes can take time to replicate, wait the full propagation window before troubleshooting.
    • If advanced label settings were originally configured by PowerShell, review them as well so the portal change aligns with the current label configuration. The label configuration can be checked with Get-Label / Set-Label in Security & Compliance PowerShell.

    If the goal is only to change the description and remove the header content marking while leaving scope and access controls unchanged, the normal edit flow is the correct path.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.