Limit remote control to managed devices
Enterprises and organizations can now restrict which devices are eligible to host remotely controlled Copilot sessions, giving administrators fine-grained control over where remote control access is permitted. The new remoteControl… The post Limit remote control to managed devices appeared first on The GitHub Blog.
Overview
Enterprises and organizations can now restrict which devices are eligible to host remotely controlled Copilot sessions, giving administrators fine-grained control over where remote control access is permitted.
The new remoteControl enterprise managed setting gives administrators the ability to define exactly how remote control works on managed devices, whether that means requiring SSO authorization for specific organizations or tailoring access on a per-device basis. This setting works alongside the existing enterprise policy, which controls whether remote control is available to users at all. Together, this gives you layered control from broad access down to per-device restrictions.
Getting started
Set mode to requireSSO to enforce SSO authorization, disabled to block remote control entirely, or enabled to allow it without restriction.
Details
You can also add the remoteControl key to your copilot-settings.json file.
You can deploy this setting through three mechanisms:
- Server-managed (
.github-privaterepository): Applies to user accounts in your enterprise. - MDM-managed: Applies to specific devices and is ideal for enforcing policies on managed machines.
- File-based: Applies to any machine that receives the file.
For more information on enterprise managed settings, check out the GitHub docs.
Cookie Preferences
The post Limit remote control to managed devices appeared first on The GitHub Blog.
Source
Originally published at github.blog.
