Default policy for Copilot features (#63407)

Co-authored-by: amrithss <89491847+amrithss@users.noreply.github.com>
Co-authored-by: Felix Guntrip <guntrip@github.com>

Author: 3 people

content/copilot/concepts/enterprise/default-availability.md

@@ -0,0 +1,73 @@
+---
+title: About default availability of {% data variables.product.prodname_copilot_short %} features and models
+shortTitle: Default availability
+intro: Policies control whether unconfigured features and models default to enabled or disabled.
+product: '{% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %}'
+versions:
+  feature: copilot
+contentType: concepts
+category:
+  - Learn about Copilot
+  - Manage Copilot for a team
+redirect_from:
+  - /copilot/concepts/models/automatic-enablement
+  - /copilot/concepts/models/default-availability
+  - /copilot/concepts/enterprise/default-model-availability
+---
+
+{% data reusables.copilot.default-availability-policies %}
+
+<!-- expires 2026-10-22 -->
+
+## 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.
+
+<!-- end expires 2026-10-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 **{% data variables.copilot.copilot_code-review_short %}** policy on the "Agents" page
+* The **MCP servers in {% data variables.product.prodname_copilot_short %}** policy on the "MCP" page
+
+The following policies are exceptions and are **not** affected:
+
+* Restrictive model policies on {% data variables.enterprise.data_residency_site %}: **Restrict Copilot to data residency models** and **Restrict Copilot to FedRAMP models**
+* **Store local sessions in the Cloud** for {% data variables.copilot.copilot_cli_short %} and {% data variables.product.prodname_vscode_shortname %} 
+
+## 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?
+
+{% data reusables.copilot.model-autoenablement-excluded-models %}
+
+## 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 [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies) and [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-policies).
+* For models, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-availability-of-default-models) and [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-organization/manage-default-models).
+
+## 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 {% data variables.product.github %}'s changelog. For more information, see [AUTOTITLE](/copilot/concepts/enterprise/learning-about-new-features-and-models).

content/copilot/concepts/enterprise/default-model-availability.md

@@ -6,7 +6,7 @@ versions:
   feature: copilot
 children:
   - /policies
-  - /default-model-availability
+  - /default-availability
   - /fedramp-models
   - /learning-about-new-features-and-models
   - /agent-management

content/copilot/concepts/enterprise/index.md

@@ -60,10 +60,6 @@ You can find information about the models available and upcoming models in the f
 * **Model comparison**: To compare model capabilities side by side, see [AUTOTITLE](/copilot/reference/ai-models/model-comparison).
 * **Changelog**: Model updates are announced in the [{% data variables.product.prodname_copilot_short %} changelog](https://github.blog/changelog/label/copilot/).
 
-#### Default enablement
-
-{% data reusables.copilot.model-autoenablement %}
-
 #### Special categories
 
 {% data variables.product.company_short %} categorizes certain types of model, allowing you to plan for model transitions and set user expectations.
@@ -80,6 +76,12 @@ You can find information about the models available and upcoming models in the f
 
 For more information, see [AUTOTITLE](/copilot/concepts/models/utility-models) and [AUTOTITLE](/copilot/concepts/models/fallback-and-lts-models).
 
+### Default enablement
+
+{% data reusables.copilot.default-availability-policies %}
+
+For more information, see [AUTOTITLE](/copilot/concepts/enterprise/default-availability).
+
 ## Considering different release stages
 
 {% data variables.product.prodname_copilot_short %} features and models progress through different release stages. Understanding release stages helps you decide when to enable features for your organization. Each stage has different expectations for stability and support.

content/copilot/concepts/enterprise/learning-about-new-features-and-models.md

@@ -40,6 +40,12 @@ A user's individual plan is cancelled when they are added to a {% data variables
 
 To see details for each policy, see [AUTOTITLE](/copilot/reference/enterprise-administrators/policy-conflicts).
 
+## What is the default status of policies?
+
+{% data reusables.copilot.default-availability-policies %}
+
+For more information, see [AUTOTITLE](/copilot/concepts/enterprise/default-availability).
+
 ## Where do policies apply?
 
 Policies can apply to any surface where users authenticate to {% data variables.product.prodname_copilot_short %}, including IDEs, the {% data variables.product.github %} website, and {% data variables.copilot.copilot_cli_short %}.

content/copilot/concepts/enterprise/policies.md

@@ -34,10 +34,12 @@ Developers get the most value from {% data variables.product.prodname_copilot_sh
 Consider enabling vetted capabilities promptly, rather than disabling features by default and enabling them only after review:
 
 * **Enable new features as they become available**, unless you have a specific compliance reason not to. {% data variables.product.github %} vets all features and models before release.
-* **Enable new models automatically**. By default, most new generally available models are enabled automatically. We recommend keeping the **Default availability for released models** policy enabled and only explicitly disabling individual models that you do not want to be available.
+* **Enable new models automatically**. By default, most new generally available models are enabled automatically.
 * **Only set enterprise-level defaults to disabled for non-negotiables**, such as compliance-critical controls or features that conflict with regulatory requirements.
 * **Scope restrictions to sensitive organizations**. Rather than blocking features enterprise-wide, disable them only in organizations with stricter compliance requirements. This lets other organizations move faster.
 
+We recommend keeping the default availability policies enabled for both features and models, and only explicitly disabling individual features and models that you do not want to be available. See [AUTOTITLE](/copilot/concepts/enterprise/default-availability).
+
 ### Spend management and policy posture
 
 Spend controls interact with your policies. If you enable advanced models and agentic features but set tight budget limits, developers may not be able to use those features consistently.

content/copilot/tutorials/roll-out-at-scale/govern-at-scale/govern-for-adoption.md

@@ -0,0 +1,7 @@
+For enterprises with {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} 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.
+
+<!-- expires 2026-10-22 -->
+
+The models policy is already active. The feature policy will become active soon.
+
+<!-- end expires 2026-10-22 -->