Clarification Needed: “Allow‑Until” Date Behavior for Policy Violation

Regarding how the “Allow‑Until” date works for policy violations and what the system does after this date expires.

Could someone help with the following?

1. Where exactly is the “Allow‑Until” date configured?
I want to confirm the precise location in the admin portal or policy settings where this value is set (e.g., inside the policy configuration, etc.).

2. What happens after the Allow‑Until date expires?
Please clarify the expected system behavior. For example:

Does the exception automatically end?
Does the policy start enforcing again immediately?
Will the user be blocked, warned, or notified?
3. Will the violation be detected again and re‑assigned to the user?
After the Allow‑Until period ends, will the system automatically:

Re-detect the same activity?
Reassign the violation back to the same user if the behavior persists?
Or does the user need to trigger the violating action again for detection to occur?
Understanding this will help us monitor violations properly and ensure policy behavior matches our compliance expectations.

Thanks in advance for your guidance!

Hello,

The “Allow Until” shows up in the policy violation work item that is sent to whoever is set as the reviewer / owner of the policy violation.

Once the date has passed, whatever you have configured to have happen when that policy violation occurs is what will then happen.

Note that if you have a custom workflow that does not have any kind of work item creation then you will not have the “Allow Until” option.