Let’s discuss Enable Windows Cross Device Participation to Seamlessly Share Content using Intune. This policy setting governs whether a Windows device is permitted to participate in cross-device experiences, also known as “Shared Experiences” or the Connected Devices Platform (CDP).
Cross-device experiences are Microsoft features that allow users to seamlessly continue activities, share content, and send notifications/messages between their various Windows devices (and sometimes Android/iOS devices) that are connected to the same Microsoft account or Azure AD account.
Organizations choose to Enable or Disable Windows Cross Device Participation policy based on their security posture, collaboration needs, and data governance requirements. Users can start a task on one corporate device (e.g., a laptop) and instantly continue it on another corporate device (e.g., a desktop or tablet) without interruption, boosting efficiency.
Certain Microsoft features rely on this platform, such as: Nearby Sharing (for quick, local transfer of files and links) and the Cloud Clipboard (for synchronizing copied content across devices). Disabling it breaks these features.
Table of Contents
Enable Windows Cross Device Participation to Seamlessly Share Content using Intune
A financial institution has strict policies against allowing any device communication that is not explicitly required for business functions, especially between highly-secure workstations and personal devices. If the Admin disable this policy, a user cannot use Nearby Sharing to quickly send a document containing sensitive customer data from their work laptop to their personal phone.
- Intune Configuration Profile Allow Clipboard Synchronization Across Devices
- Turn off App Notifications On The Lock Screen Policy using Intune
- Support Device Authentication Using Certificate Policy Intune
Configure Policy from Intune Portal
This is an ADMX-backed policy and requires SyncML format for configuration. Sign in to the Microsoft Intune Portal with Credentials. Navigate to Devices > Configuration > + Create > New Policy.

Profile Choosing Step
After that you can choose appropriate platform and profile type. This is necessary step for policy creation and you cannot change profile and platform after creating profile. Here I would like to configure the policy to Windows 10 and later platform and settings catalog profile. Then click on the Create button.

Begin Policy with Basic Tab
Basic Tab is the first tab that helps users to give identity for policy. For this you can add Name and description for the settings you want to select for policy creation. Here is Name is mandatory and description is optional. After adding this click on the Next button.

Configure Cross Device Participation Policy
After that you will get Configuration settings tab which helps you to access specific settings. To get the settings click on the +Add settings hyperlink and select specific settings from Settings Picker. Here, I would like to select the settings by browsing by Category. I choose Administrative Templates\System\Group Policy\Continue experiences on this device.

Disable Windows Cross Device Participation
If you disable this policy setting, the Windows device isn’t discoverable by other devices, and can’t participate in cross-device experiences. Click on the Next button.

Enable Windows Cross Device Participation
If you enable this policy setting, the Windows device is discoverable by other Windows devices that belong to the same user, and can participate in cross-device experiences. Click on the Next button.

Adding Scope Tags
Scope Tag is not a mandatory step for policy creation. But you can add Scope tags for visibility restrictions. Here, I don’t add scope tags for Enterprise IP Range Policy. Click on the Next button.

Selecting Group from the Assignment Tab
To assign the policy to specific groups, you can use the Assignment Tab. Here I click, +Add groups option under Included groups. I choose a group from the list of groups and click on the Select button. Again, I click on the Select button to continue.

Finalize Policy
This is the Fina step for policy creation. You can review all the details on this tab and avoid misconfiguration. After verifying all the details, click on the Create Button. After creating the policy, you will get a success message.

Device Check-in Status
Device Check-in Status Page shows if the Policy is succeeded or Not. Before checking this, you can sync the device on Company Portal for Faster policy deployment. Then Go to Devices > Configuration > Search for the Policy. Here, the policy shows as successful.

Client Side Verification
It helps you check the client side and verify the policy status. Open the Client device and open the Event Viewer. Go to Start > Event Viewer. Navigate to Logs: In the left pane, go to Application and Services Logs > Microsoft > Windows > DeviceManagement-Enterprise-Diagnostics-Provider > Admin.
| Event ID Details |
|---|
| MDM PolicyManager: Set policy string, Policy: (EnableCDP), Area: (ADMX_GroupPolicy), EnrollmentID requesting merge: (EB427D85-802F-46D9-A3E2-D5B414587F63), Current User: (Device), String: (), Enrollment Type: (0x6), Scope: (0x0). |

Removing the Assigned Group from Windows Cross Device Participations Policy Settings
If you want to remove the Assigned group from the policy, it is possible from the Intune Portal. To do this, open the Policy on Intune Portal and edit the Assignments tab and the Remove Policy.
To get more detailed information, you can refer to our previous post – Learn How to Delete or Remove App Assignment from Intune using by Step-by-Step Guide.

How to Windows Cross Device Participation Policy
You can easily delete the Policy from the Intune Portal. From the Configuration section, you can delete the policy. It will completely remove it from the client devices.
For detailed information, you can refer to our previous post – How to Delete Allow Clipboard History Policy in Intune Step by Step Guide.

CSP Details
This policy setting determines whether the Windows device is allowed to participate in cross-device experiences (continue experiences). This policy is applicable for Windows 10, version 2004 with KB5005101 [10.0.19041.1202] and later, Windows 10, version 20H2 with KB5005101 [10.0.19042.1202] and later, Windows 10, version 21H1 with KB5005101 [10.0.19043.1202] and later, Windows 11, version 21H2 [10.0.22000] and later.

Need Further Assistance or Have Technical Questions?
Join the LinkedIn Page and Telegram group to get the step-by-step guides and news updates. Join our Meetup Page to participate in User group meetings. Also, Join the WhatsApp Community to get the latest news on Microsoft Technologies. We are there on Reddit as well.
Author
Anoop C Nair has been Microsoft MVP for 10 consecutive years from 2015 onwards. He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His primary focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career, etc
