Tools #Coding agents Oct 23, 2026 · Originally published Oct 22

Copilot's global default policy starts enforcement, rolling out through October 26: unconfigured features and MCP server settings will be set once from the global default

Admins on Copilot Business and Enterprise have one check to do this week. What will change and what won't.

Primary source GitHub Changelog · github.blog Read the original ↗

// Key points

  • The global default policy announced in September begins rolling out enforcement today for Copilot Business and Copilot Enterprise, completing by October 26, so it may take effect at different times for different enterprises and organizations.
  • Generally available features under Features & clients and MCP servers in Copilot that are still Unconfigured will be set to the chosen global default of Enabled, Disabled or Let organizations decide. It's a one-time change; later changes to the default won't touch settings already in place.
  • Features you've explicitly enabled or disabled stay as they are, and preview features remain opt-in.

Builder's takeI'd check the default under AI Controls before the 26th, especially the MCP servers section: once it's set to Enabled in this one-time pass, changing the default later won't take it back. Better to start with Let organizations decide and open things up one by one.

// Background · from #Coding agents

Full timeline →
  1. Oct 23 Claude Code 2.1.309 fixes several sandbox and permission gaps, including sandboxed Bash running shell startup files outside the sandbox before each command
  2. Oct 23 The Copilot impact dashboard adds industry comparisons: agent adoption and merge rates benchmarked by company size across ten industries
  3. Oct 22 Claude Code 2.1.307 emits an OpenTelemetry event each time a safety layer stops, prompts or sends back a tool call