GitHub Ships Copilot Access Controls Days After Opus 5

GitHub added two Copilot governance controls on July 27, per the company's changelog.

For enterprises rolling out Copilot's cloud agent, that gap matters. Locking down who can reach it beats discovering later which employees already have access.

The access policy controls which users in an enterprise can reach the Copilot app at all. The managed settings entry covers both the app and the cloud agent, not just one or the other.

Both landed three days after GitHub added Claude Opus 5 to Copilot on July 24. Capability shipped first. The switches to control it followed close behind.

If you're selling tooling into enterprises, that ordering is worth copying. Ship the controls right behind the capability, not months after a security review flags it.

For IT buyers, the model Copilot runs matters less than who can flip the switch on an autonomous coding agent. That switch existed before the agent shipped, not after.