Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The policy is configurable now but does not change user feature access before October 22, 2026. No exact time or time zone is announced.
- GitHub documentation says the default is Enabled. Without administrator action, eligible unconfigured GA features become available October 22; explicit enabled or disabled choices remain.
- Options are Enabled, Disabled and Let organizations decide. Inspect unconfigured items at enterprise and organization levels separately.
- Preview features remain opt-in. Default model availability is a separate policy already in effect, with exceptions for some pre-GA, open-weight and specific data-retention models.
- Check Features & clients, Copilot code review and MCP servers in Copilot in AI Controls. Preserve current settings before changes if exceptions or organization inheritance are unclear.
What changes on October 22
GitHub's September 24, 2026 announcement introduces “Default policy for new features” for Copilot Business and Copilot Enterprise. Administrators can configure it now, but the announcement gives 28 days without changing user access. From October 22, eligible GA features still marked Unconfigured follow the global default. GitHub Docs says that default is Enabled, so organizations taking no action should expect eligible unconfigured features to become available.
This does not enable every Copilot feature, model and preview at once. Administrators should identify which items remain Unconfigured, the enterprise default, explicit organization overrides, and whether capabilities meet internal data and budget requirements.
Which features enter the default policy
Scope includes eligible features on the enterprise Features & clients page, Copilot code review on Agents, and MCP servers in Copilot on MCP. New GA features, previews becoming GA and existing unconfigured GA features may be affected. Official help lists exceptions: two restricted-model policies on GHE.com and Store local sessions in the Cloud for Copilot CLI/VS Code are outside this feature-default policy.
Preview features remain opt-in. Explicit Enabled or Disabled choices are not overwritten by the new global default. An existing opt-in to a preview remains when it becomes GA. A release announcement or screenshot alone cannot establish that a tenant has every feature.
What Enabled, Disabled and organization choice mean
Enabled makes current and future eligible features available by default where no individual choice exists. Disabled keeps current eligible features unavailable and requires administrator approval for future ones. Let organizations decide delegates eligible-feature choices to organization administrators. Enterprise choices apply to unconfigured enterprise items; organization defaults inherit only when the enterprise permits organization choice and the organization has no individual setting.
An enterprise with several organizations may let ordinary development teams try new features while keeping them disabled for stricter compliance groups. Record which decisions belong to the enterprise, organizations and individual feature overrides. “Organizations can decide” does not mean every organization has approved.
Administrator checks: save a baseline before handling unconfigured items
First confirm appropriate enterprise or organization administrator permissions and a Copilot Business/Enterprise subscription. Open GitHub AI Controls → Copilot and read Default policy for new features. Next inspect the documented count of eligible unconfigured policies and Features & clients. Then separately review Agents code review, MCP servers in Copilot and organization overrides. Save choices, scope and review date.
Fourth, assess each capability's data, permission and cost requirements, then retain defaults, choose Disabled, delegate to organizations or set explicit feature overrides. Fifth, after October 22, have an authorized account verify actual policies and user-visible capabilities. This page relies on public announcements and documentation, without enterprise-tenant login or switching tests. Stop bulk changes and consult GitHub administrative support if interfaces, inheritance or policy labels differ.
Model defaults and September 28 unified access are separate changes
GitHub Docs says Default availability for released models is already effective, separate from the feature policy starting October 22. It applies to unconfigured released models, with disabled exceptions for pre-GA models, open-weight models, some models outside GitHub's data-retention agreements, and models failing enterprise data-residency or FedRAMP restrictions. Default feature enablement does not mean every model immediately becomes available.
GitHub separately announced September 28 changes to unified web/mobile access, chat retention and code-review default intensity. See the Copilot unified-policy and data-retention checks. This page concerns defaults for unconfigured features after October 22. Do not mix the two announcements’ dates, settings or administrator tasks.
Validation, failure diagnosis and applicable rollback
Distinguish global defaults, organization inheritance and explicit item settings. No access change before October 22 does not mean the setting failed to save. Afterward, a missing capability may reflect preview eligibility, plan, region or explicit disabling rather than global-policy failure. GitHub publishes neither a fixed list of every current eligible feature nor precise per-tenant activation times.
For unintended access, first record the affected feature, organization and global and individual values. An administrator can then disable the feature or adjust the applicable default and verify new requests stop. Restoring a switch does not undo existing sessions, data or charges; handle those under existing organizational audit procedures. PRODUCT_FIT=NONE: changing IPs cannot alter enterprise policies, feature eligibility or billing.
Sources
Frequently Asked Questions
When does GitHub Copilot's new-feature default policy take effect?
GitHub specifies October 22, 2026 for eligible unconfigured GA features. It can be configured now but does not change access through this policy before then. No exact time or time zone is announced.
Will inaction enable every Copilot feature?
No. Official help says the default is Enabled, applying October 22 to eligible unconfigured GA features. Explicit choices, previews and listed exceptions keep their respective rules.
Will a global default override explicitly disabled features?
No. GitHub says explicit enabled or disabled choices remain. Still inspect enterprise, organization and individual settings separately.
Do previews and new models also switch on automatically October 22?
Previews remain opt-in. Default model availability is a separate policy already in effect, with exceptions for pre-GA, open-weight and some retention or compliance-restricted models.
Does Let organizations decide mean an organization already approved?
No. It delegates eligible-feature decisions to organization administrators. Inspect inherited defaults and explicit choices separately for unconfigured enterprise and organization items.
Can turning off the default undo previous use?
No. Administrators can adjust global or individual policies and verify future access, but prior sessions, data and charges need separate organizational audit handling.