When Does Sensitivity Label Content Expiry Apply to an Already Labeled Document?
Short answer
B Doc1 keeps the 21-day content expiry embedded when Label1 was applied on January 3, so User2 loses access on January 24.
Question
Key Takeaways
It tests whether a label setting change is retroactive to already-labeled content — the trap is applying the new 28-day period to the original labeling date and picking January 31.
Sensitivity label content expiry is embedded in a document at the moment the label is applied, so later changes to the label's expiry period do not extend access to content that already carries it. This page confirms that Doc1, labeled on January 3 with a 21-day expiry, expires for User2 on January 24 (B), not after the January 15 change to 28 days.
Common mistake: Selecting January 31 (D) by recalculating from the new 28-day content expiry, treating the January 15 label update as if it re-stamped the already-labeled Doc1.
Expert Analysis
Why the Answer Is Correct
Label1's table sets a content expiry, and Microsoft calculates that period from the date the label is actually applied to the item — here January 3, when User1 labeled Doc1. January 3 plus the original 21-day period lands on January 24, so that is when User2's access to Doc1 ends. Changing the label's expiry to 28 days on January 15 is not retroactive: the expiry metadata stored in Doc1 was stamped when the label was applied and is not recalculated afterwards. Neither the January 2 publication of the label nor User2's January 4 edit resets or extends that clock. Therefore January 24 (B) is the expiry date for User2.Why the Other Options Are Wrong
January 23 (A) counts 21 days from January 2, the date Label1 was published to User1; publication only makes the label available and is not when expiry starts. January 25 (C) is an inclusive off-by-one count of the 21 days rather than a straight addition from the labeling date. January 31 (D) applies the increased 28-day period to a document that was labeled on January 3, which assumes label updates retroactively reset expiry — exactly the behavior Microsoft does not implement. The 67-vote support for B does not by itself prove anything, but it matches how the platform actually embeds expiry at labeling time.Community Comment Notes
MrParfumeDeluxe captured the governing rule, pointing out that "label settings are embedded at the time of labeling" and that later label updates do not retroactively affect already-labeled content. itsadel walked the same arithmetic and concluded with the exact expression "January 3 + 21 days = January 24", treating the January 15 change as inapplicable to Doc1. emartiy took the opposite view, arguing that "3th + 28 days from label" gives January 31, which is the classic retroactivity trap. Athena94 raised a separate point that Label1 was never published to User2, a fair scope observation, though the content expiry still governs User2's access to the labeled document. The vote split is a useful reminder that many test takers misread label updates as retroactive.Official Reference
- https://learn.microsoft.com/en-us/purview/sensitivity-labels
- https://learn.microsoft.com/en-us/purview/sensitivity-labels-office-apps
These links open the official vendor documentation in a new tab.
Exam Strategy
Separate the label's publication date from the date the label was applied to the content — content expiry always starts from the labeling action, not from publishing. Whenever the question adds a later label update (here January 15 to 28 days), treat it as a retroactivity check: existing labeled items keep their embedded settings. Pick the date computed from the original period and the original labeling date.
Frequently Asked Questions
Does changing the content expiry period on Label1 affect already labeled documents like Doc1?
Why doesn't User2 editing Doc1 on January 4 reset the content expiry date?
Community Votes
67% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
MrParfumeDeluxe 👍 4 Answered BCorrect answer is B. In Microsoft’s official sensitivity label documentation, it’s stated that "label settings are embedded at the time of labeling" and that updates to the label do not retroactively affect already labeled content.
-
itsadel 👍 2 Answered BInitial Expiry Period: The sensitivity label "Label1" specifies that user access to content expires after 21 days. User1 created Doc1 on January 3, which means the 21-day expiry period is calculated as: January 3 + 21 days = January 24. Change to Expiry Period on January 15: On January 15, the expiry period is updated to 28 days. However, changes to the sensitivity label do not retroactively affect content that already has the label applied. Since Doc1 already had Label1 applied on January 3 with the original 21-day expiry, it will still follow the original expiry rule. Conclusion: For User2, access to Doc1 expires on January 24, as the original expiry setting remains in effect.
-
emartiy 👍 2 Answered DItem was created on 3th Jan. so updating label 21 to 28 days will make document accessible until 31 of Jan.. Created at 3th + 28 days from label = 31.
-
Athena94 👍 1Label-1 was never published to User2, isn't this question incorrect?
-
Domza 👍 1 Answered DLooks good~ Adding extra 7 days to access Doc 1
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.