# Limit remote control to managed devices

> Source: <https://github.blog/changelog/2026-07-30-limit-remote-control-to-managed-devices>
> Published: 2026-07-30 14:54:47+00:00

# Limit remote control to managed devices

Enterprises and organizations can now restrict which devices are eligible to host [remotely controlled Copilot sessions](https://github.blog/changelog/2026-05-18-remote-control-for-copilot-cli-sessions-now-generally-available-on-mobile-web-and-vs-code/), 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](https://docs.github.com/copilot/concepts/agents/copilot-cli/about-remote-control#administering-remote-control), 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](#getting-started)

Set `mode`

to `requireSSO`

to enforce SSO authorization, `disabled`

to block remote control entirely, or `enabled`

to allow it without restriction.

You can also add the `remoteControl`

key to your `copilot-settings.json`

file.

You can deploy this setting through three mechanisms:

**Server-managed (** Applies to user accounts in your enterprise.`.github-private`

repository):**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](https://docs.github.com/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings).