Because the blocking is not coming from the WIP “Silent” mode itself, but from other protection controls that still enforce restrictions even when WIP is configured as Silent.
In WIP:
- Silent mode only means WIP does not prompt end users or block actions that would otherwise show a user-facing warning in Allow Overrides mode.
- However, “unallowed actions” are still blocked, even in Silent mode. The documentation states that in Silent mode, WIP “runs silently, logging inappropriate data sharing, without stopping anything that would have been prompted for employee interaction while in Allow Overrides mode. Unallowed actions, like apps inappropriately trying to access a network resource or WIP-protected data, are still stopped.”
In practice, this means:
- If Outlook is treated as a corporate/WIP-protected app and Chrome (or the specific Chrome profile) is treated as non-corporate/unprotected, then copying corporate data from Outlook and pasting into Chrome can be considered an unallowed action.
- Even with WIP set to Silent, those unallowed actions are still blocked at the platform level, so users experience blocking when trying to paste into Chrome.
To avoid this behavior while auditing:
- Ensure Chrome (or the relevant profile) is configured as a WIP-allowed/enlightened app or otherwise treated as a corporate app in the WIP policy, so that copy/paste from Outlook to the internal web app is not classified as an unallowed action.
- Alternatively, adjust the app and network boundary definitions so that the internal web app and its browser context are recognized as corporate, reducing the number of actions that fall into the “unallowed” category that WIP must still block even in Silent mode.
References: