Incorrect and Inconsistent Sensitivity label triggering including retired labels

Sonya Smith (CTR) 5 Reputation points
2026-11-04T17:36:07.4266667+00:00

My manager and I were testing Copilot while entering the same prompt a sensitivity label is triggered for my manager but not for me. Also, it is pulling retired sensitivity labels. Why is this happening and how can we correct it?

Microsoft Security | Microsoft Purview
0 comments No comments

1 answer

Sort by: Oldest
  1. Billy Peralta 0 Reputation points
    2026-11-16T05:41:46.76+00:00

    There are two things I'd check here.

    First, Copilot can give different results to different users, even with the same prompt.

    Copilot only uses content each person is allowed to access. It also doesn't necessarily use the same files every time.

    In Copilot Chat, when a response uses files with different sensitivity labels, Microsoft says it shows the highest-priority label from those sources.

    I'd compare the files Copilot referenced for you and your manager. Then check which sensitivity labels are applied to those files.

    For the retired labels, there's an important difference:

    • If a label was removed from a publishing policy, it can still remain on files that were already labeled.
    • If the label was actually deleted from Microsoft Purview, that's a different situation and needs checking.

    I'd ask your Microsoft Purview administrator to confirm whether those old labels were unpublished or deleted, and whether they're still applied to existing documents.

    That should help narrow down whether you're seeing differences in source files or an issue with the labels themselves.

    Microsoft references:

    Was this answer helpful?

    0 comments No comments

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.