How Do IT Admins Control Clipboard History With Group Policy?

IT admins control Windows clipboard history with two policies: Allow Clipboard History (Experience/AllowClipboardHistory) turns the Win+V history feature on or off for the device, and Allow Clipboard synchronization across devices (Privacy/AllowCrossDeviceClipboard) allows or blocks syncing clipboard content to the user's other devices. Both are under Computer Configuration > Administrative Templates > System > OS Policies in Group Policy, and both are available as MDM policies for Intune. Neither can change the 25-item or 4 MB limits, and neither stops apps from reading the live clipboard.

Allow Clipboard History

Microsoft describes it as determining whether "history of Clipboard contents can be stored in memory". The change takes effect immediately.

"Allowed" doesn't mean "turned on". With the policy at 1, users still choose whether to switch history on. There is no policy to force history on.

To confirm the policy is working, Microsoft's validation steps are: set the value to 0, copy some text in Notepad, press Win+V, and check that no items appear, including the one you just copied. The setting under Settings > System > Clipboard should be greyed out with a policy message.

Allow Clipboard synchronization across devices

When allowed, clipboard contents can sync across devices signed in with the same Microsoft account or Microsoft Entra account. When disabled, contents can't be shared to other devices. This is the policy behind the Clipboard history across your devices switch users see in Settings. The default is allowed, so joining a device to Microsoft Entra doesn't turn sync off by itself. Set 0 explicitly if you don't want it.

Setting them in Intune

Both are device-scoped Policy CSP settings, so you can deploy them from an Intune configuration profile; search the Settings catalog for the policy names. Assign to device groups, since neither has a user-scoped version.

A common baseline:

To check a device, look for the greyed-out switches in Settings, run gpresult /h report.html for domain Group Policy, or check the device's configuration status in Intune.

What users see

Copy and paste still work when history is blocked; only the list of earlier copies goes away. Tell users this before rollout, or some will install their own clipboard manager to replace it. Clipboard history greyed out by organization is written for the user's side of this.

What these policies don't do

• Raise or lower the 25-item and 4 MB limits.
• Add an expiry timer. Unpinned items still clear only at restart.
• Stop other processes from reading the live clipboard. Can other apps read everything you copy? explains why.
• Remove or block third-party clipboard managers or Phone Link. Use application control (App Control for Business or AppLocker) for that.
• Configure Recall. Recall has its own policies under Windows Components > Windows AI, such as Allow Recall to be enabled and Turn off saving snapshots for Recall. Windows Recall vs clipboard history compares the two.
• Affect Snipping Tool. Screenshots still go to the live clipboard when history is blocked.

Suggested baselines

Standard office laptops

• Allow history.
• Block cross-device sync.
• Ask staff not to pin customer data and to clear history at the end of the day. A one-page team clipboard SOP puts those rules in writing.

Privileged-access workstations

• Block history.
• Block sync.
• Use password manager autofill or a privileged access tool instead of copying credentials.

Shared kiosks and lab PCs

• Block history.
• Block sync.
• Sign users out or restart between sessions rather than relying on fast user switching.

Contractor or BYOD devices you manage

• Block sync at minimum.
• Block history if the data is regulated; otherwise allowing it may be better than users installing an unmanaged manager.

Rolling out the change

1. Deploy AllowCrossDeviceClipboard = 0 first. Users rarely notice it.
2. Announce AllowClipboardHistory = 0 before deploying it. Help desk will hear about the missing Win+V list the same day.
3. Offer an alternative for reusable text, such as ticket templates or an approved snippet tool.
4. Look for existing clipboard managers (for example Ditto.exe, copyq.exe or ClipboardFusion.exe) in installed software and startup entries, and either approve them with a reviewed configuration or remove them.
5. If you have Copilot+ PCs, review the Recall policies in the same change so the two features aren't left inconsistent.

For the user-facing decision, should you disable clipboard history on a work laptop? explains the trade-offs role by role.

Other features to review separately

FAQ

Can Group Policy increase the clipboard history limit beyond 25 items?

No. There is no supported policy or setting for it. The 25-item and 4 MB limits are fixed.

Is there a user-level policy for clipboard history?

No. Both clipboard policies are device-scoped in the CSP documentation.

Does blocking clipboard sync also block local history?

No. AllowCrossDeviceClipboard only controls syncing. Local Win+V history keeps working if AllowClipboardHistory allows it.

Related reading

• Should You Disable Clipboard History on a Work Laptop?
• Clipboard History Grayed Out by Your Organization: What to Do
• How to Disable Windows Clipboard Cloud Sync
• Does Windows Clipboard Sync Upload What You Copy?

Sources

• Experience Policy CSP: AllowClipboardHistory (Microsoft Learn) — CSP path, values, Group Policy mapping and validation steps.
• Privacy Policy CSP: AllowCrossDeviceClipboard (Microsoft Learn) — CSP path, values, Group Policy mapping and description.
• Manage Recall for Windows clients (Microsoft Learn) — separate Windows AI policies for Recall.
• Using the clipboard (Microsoft Support) — the 25-item and 4 MB limits and restart behaviour.

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge Drop vs Win+V · Support