Hi everyone, IT specialists! In this article, we continue our mini-series on how to simplify the Microsoft 365 Copilot and Microsoft 365 Copilot Chat user experience by using Microsoft Intune policies. Today, we will see how to map the physical Copilot key on newer PCs to launch the app with a single key press.
Please note: the video is narrated in Italian. English subtitles are available for non-Italian speakers.
Mapping the physical Copilot key
Today we focus on mapping the physical Copilot key, available on newer PCs. This key lets you launch the Microsoft 365 Copilot app with a single tap, further simplifying the user experience. To achieve this, we use a custom Microsoft Intune OMA-URI.
Let’s see right away how to create the policy and deploy this setting.
Creating a custom OMA-URI
Creating a custom OMA-URI is a quick and simple process: the specific details of the OMA-URI used are available below, right after the video snippet.
➡️ Name: SetCopilotHardwareKey
➡️ OMA-URI: ./User/Vendor/MSFT/Policy/Config/WindowsAI/SetCopilotHardwareKey
➡️ Data type: String
➡️ Value: Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe!Microsoft.MicrosoftOfficeHubVerification of policy application
Let’s see what happens on the Windows client in the personalization panel.
Test with the Copilot key
It’s time to press the key and see if everything works!
Perfect, everything works! 😊
Attached documentation
As always, here is some useful documentation:
📌 SetCopilotHardwareKey
📌 How to find the AUMID
Conclusions
Thank you for following this article all the way to the end! Implementing these policies is an effective way to streamline the Microsoft 365 Copilot user experience. If you already have PCs with the physical Copilot key in your device fleet, this policy is simple to implement and offers great benefits.
Let me know what you think in the comments of the video or on my social profiles!
See you soon, legends!
Your IT Specialist,
Riccardo
