GitHub tightens enforcement of managed settings in GitHub Copilot
Administrators can require current policies to be loaded when GitHub Copilot starts. With forceRemoteSettingsRefresh enabled, the client does not continue unless it confirms that the policies are current. The managed sandbox setting now also enforces a minimum client version.
GitHub has enabled enterprise administrators to require supported GitHub Copilot clients to load current settings from the server at startup. The forceRemoteSettingsRefresh option is supported by Copilot CLI, VS Code and GitHub Copilot app. When set to true, cached policies are not sufficient: if the client cannot confirm that they are current, it does not continue operating.
The option can be delivered from the server, through MDM or via a file. Delivery through MDM or a file can enforce loading current policies even before the first sign-in. A value delivered from the server starts requiring a refresh on subsequent launches after the client first receives it. Without this option enabled, clients continue to use the standard managed settings cache, which GitHub says speeds up startup and helps bridge temporary service outages.
The managed sandbox setting now enforces a minimum client version in connection with the generally available local sandbox feature. If an administrator includes this key in the settings, users of older versions that do not meet the requirement must update their client to use GitHub Copilot again.
Why it matters
Administrators gain the ability to ensure that a change to organizational policies takes effect before work with GitHub Copilot begins. This has an operational consequence: when refresh is mandatory, an inability to confirm current policies can block startup even if the client has older settings stored.
Two audiences, two different impacts
What this means
For individuals
A developer using a client pinned to an older version may need to update it to continue working once the sandbox key is included in the organization’s settings.
For a business
An organization can prevent GitHub Copilot from being used with outdated policies, but enabling mandatory refresh makes availability at startup dependent on successfully confirming settings with the server.
Risks and complianceCheck the original
Event sources
only one source so far · 1 publisher, 0 independent. We count feeds from the same owner only once.