For enterprises with Copilot Business or Copilot Enterprise plans, two separate policies control whether unconfigured generally available (GA) features and models default to enabled or disabled. If these policies are enabled, users benefit from the latest features and models without the need for administrator intervention.
The models policy is already active. The feature policy will become active soon.
Default availability of features
The Default policy for new features policy is available to configure but is not currently active. It will start applying to new and existing GA features from October 22, 2026. In your policy settings, you will see a banner showing how many eligible policies are currently unconfigured, so you can assess the impact of your global default and explicitly configure individual policies before October 22.
This policy is enabled by default. If you don't take action, unconfigured features will be enabled on October 22.
What does the policy do?
Your setting for this policy determines the enablement status of:
- New GA (general availability) features
- Features that move from preview to GA
- Existing GA features that are Unconfigured in your policy settings
The policy can be configured in an enterprise and its organizations. At the enterprise level, it applies to features labeled as Unconfigured. At the organization level, it applies to features that an enterprise owner has set to Let organizations decide, but that an organization owner has not explicitly configured.
The policy does not apply to features in preview.
What counts as a feature?
For the purposes of this policy, a "feature" refers to any policy configured on an enterprise's "Features & clients" page (github.com/enterprises/ENTERPRISE/ai-controls/copilot/features), plus:
- The Copilot code review policy on the "Agents" page
- The MCP servers in Copilot policy on the "MCP" page
The following policies are exceptions and are not affected:
- Restrictive model policies on GHE.com: Restrict Copilot to data residency models and Restrict Copilot to FedRAMP models
- Store local sessions in the Cloud for Copilot CLI and VS Code
Default availability of models
The Default availability for released models policy is active and affects new and unconfigured GA models.
Which models follow the policy?
既定のポリシーは、明示的に構成していないモデルに適用されます。 これらのモデルは、既定の ポリシーへの委任 ラベルを使用して、企業または組織のモデル設定で示されます。 新しいモデルがリリースされると、明示的に構成するまで、そのモデルは既定値を継承します。
次のモデルはスコープ 内にありません 。 既定では、"既定の可用性" ポリシー設定に関係なく無効になります。
- GA 前モデル
- オープン ウェイト モデル (DeepSeek、 Kimi K2.7 Code、 Kimi K3)
- GitHubのデータ保持契約 (Claude Fable 5、Claude Fable 5.1) の対象とされないモデル
- モデルを「データ常駐型」または「FedRAMP 準拠」に限定している企業において、これらのポリシーを遵守していないモデル
How do I prevent default enablement?
To disable default enablement entirely, disable the default policies in your enterprise or organization's settings. You can set a policy for the entire enterprise, or disable the policy only in organizations with stricter compliance requirements.
If you keep the default availability policies enabled, you can explicitly disable individual features and models so that they are not eligible for automatic enablement.
- For features, see 企業での GitHub Copilot のポリシーと機能の管理 and 組織内のGitHub Copilotのポリシーと機能の管理.
- For models, see 企業でのモデルの可用性の管理 and 組織内のモデルの可用性の管理.
How do I prepare for new releases?
We recommend keeping up with new releases and GA announcements so you can choose your enablement settings. New features and models are announced on GitHub's changelog. For more information, see 新機能とモデルについて学習する.