Merge pull request #45629 from github/repo-sync

Repo sync

Author: docs-bot

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

@@ -13,15 +13,7 @@ redirect_from:
   - /copilot/concepts/models/automatic-enablement
 ---
 
-On {% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %} plans, the **Default availability for released models** policy will control whether unconfigured generally available (GA) models default to enabled or disabled. If this policy is enabled, users will benefit from the latest models without the need for administrator intervention.
-
-<!-- expires 2026-08-26 -->
-
-To give you time to prepare, this policy can be configured but **does not currently affect model availability**. On August 26, 2026, new GA models and existing unconfigured GA models will automatically follow the default set in the policy. These models will be relabeled as "inherits default" in the UI.
-
-To prepare for this change, you can disable the policy or explicitly disable models you don't want to be enabled.
-
-<!-- end expires 2026-08-26 -->
+For enterprises with {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} plans, the **Default availability for released models** policy controls whether unconfigured generally available (GA) models default to enabled or disabled. If this policy is enabled, users benefit from the latest models without the need for administrator intervention.
 
 ## Which models follow the policy?
 

content/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-availability-of-default-models.md

@@ -12,37 +12,40 @@ allowTitleToDifferFromFilename: true
 
 As an enterprise owner, you can manage which {% data variables.product.prodname_copilot_short %} models are available to people in your enterprise.
 
-An enterprise owner can enable or disable models for everyone in the enterprise. Alternatively, there are two different modes for controlling granular access to models: organizations and enterprise teams.
+You can enable or disable models for everyone in the enterprise. On top of this baseline, there are two different modes for controlling additional granular access to models: through organizations, or through enterprise teams.
 
-By default, models that are set to "optional" at the enterprise level are available for organizations to set to enabled or disabled. Enterprise owners can also create model rules to enable or disable models in organizations directly.
-
-> [!IMPORTANT] {% data reusables.copilot.model-autoenablement %}
-
-## About the enterprise teams model access preview
-
-As an opt-in preview, enterprises can switch to controlling granular model access exclusively through enterprise teams. This gives you more control over model access based on business needs, roles, or levels of training.
+* In the default experience, enterprise owners can delegate decisions for each model to organizations. Organization owners can then set the model to enabled or disabled. Enterprise owners can also create model rules to enable or disable models in organizations directly.
+* As an opt-in preview, enterprises can switch to controlling granular model access exclusively through enterprise teams. This gives you more control over model access based on business needs, roles, or levels of training.
 
 ## Setting a baseline for model access
 
-Regardless of whether you are opted in to the preview, you should explicitly configure all models that should be either enabled or disabled for everyone. For example, everyone in your company might get access to vetted, low-cost models, whereas some models might be disabled everywhere for compliance reasons.
+Regardless of whether you are opted in to the enterprise teams preview, you should explicitly configure all models that should be either enabled or disabled for everyone. For example, everyone in your company might get access to vetted, low-cost models, whereas some models might be disabled everywhere for compliance reasons.
 
-This sets a baseline that you can add to with more granular controls. For models that only some people should get access to, set them to "optional." Then, you will be able to grant access to specific organizations or enterprise teams, depending on your settings.
+This sets a baseline that you can add to with more granular controls. For models that only some people should get access to, you will delegate the model setting to organizations or enterprise teams, depending on which experience you're using.
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.ai-controls-tab %}
 {% data reusables.enterprise-accounts.copilot-sidebar %}
 {% data reusables.enterprise-accounts.configure-allowed-models %}
 1. Select a status for each model in the list:
 
-   * **Enabled**: Enabled for everyone.
-   * **Disabled**: Explicitly disabled for everyone.
-   * **Optional**: You can choose whether to enable the model for specific organizations or enterprise teams.
+   * **Enabled** for everyone.
+   * **Disabled** for everyone.
+   * **Delegate** the decision to organizations or enterprise teams and apps.
+
+### Checking for unconfigured models
+
+{% data reusables.copilot.model-autoenablement %}
+
+These models are labeled as "Delegate to Default Policy" in your model settings. If the "Default availability" policy is enabled, these models will be available for everyone.
+
+If you are not happy with any of these settings, you can disable specific models, make them available only for specific organizations or teams, or disable the "Default availability" policy so unconfigured models default to disabled.
 
 ## Granting access to specific organizations (default)
 
 This section applies if you are **not** opted in to the enterprise teams model access preview.
 
-To allow each organization to make its own decision about a model, set it to **Optional** in your enterprise's model list. Organization owners can then choose whether to enable or disable the model. If left unconfigured by an organization, the model will follow the organization's **Default availability for released models** policy setting.
+To allow each organization to make its own decision about a model, select **Delegate to Organizations** in your enterprise's model settings. Organization owners can then choose whether to enable or disable the model. If left unconfigured by an organization, the model will follow the organization's **Default availability for released models** policy setting.
 
 As an alternative to delegating control to organizations, targeted model rules let you control exactly which models are available to specific organizations, giving you more granular control than the enterprise-wide availability settings.
 
@@ -55,7 +58,7 @@ As an alternative to delegating control to organizations, targeted model rules l
 
 ## Granting access to enterprise teams (opt-in preview)
 
-Once you are opted in to the preview, organization-level model settings will be deactivated. Organization owners can no longer manage model policies. Instead, individual models can be enabled for specific enterprise teams.
+When you opt in to the preview, organization-level model settings are deactivated. Organization owners can no longer manage model policies. Instead, individual models can be enabled for specific enterprise teams.
 
 You can roll back from enterprise teams mode while the feature is in preview. This returns your enterprise to its previous policy state before you opted in. Any changes to enterprise-level model policies made after switching to enterprise teams mode will not be preserved after rollback.
 
@@ -65,15 +68,15 @@ Model settings for enterprise teams are additive to your enterprise's model sett
 * If the enterprise has enabled a model, it is always enabled for teams.
 * A team can receive access to additional models on top of the enterprise baseline.
 * If a user belongs to multiple enterprise teams, they receive access to all models enabled by the enterprise and across all of their enterprise teams. As long as one of their enterprise teams enables a model, the user gets access to it.
-* There is no option to explicitly set a model to "disabled" for a team in the team's settings. "Optional" in the team's settings means the model is not currently enabled for the team.
+* There is no option to explicitly set a model to "disabled" for a team in the team's settings. By default, models that are delegated to teams are set to "Optional" in each team's settings, meaning the model is not currently enabled for the team.
 
 ### Preparing to migrate
 
 Before opting in to the preview, we recommend you create enterprise teams and begin recreating and enhancing your existing organization-based setup. With teams, you have more scope to map model access to business needs. For example, higher-cost models might be enabled for development teams or people who have received specific training.
 
 For each team, you can use the **default models** tab to configure the model access that the team will receive. These settings do not apply until you opt in to the preview.
 
-Make sure your new setup will not cause regressions for users. Although models that are explicitly "enabled" or "disabled" at the enterprise level will keep those settings once you opt in to the preview, models that are "optional" or unconfigured will be unavailable by default until they are enabled for specific teams. Filter your enterprise's model policy page by status to identify these models and choose which teams will receive access to them.
+Make sure your new setup will not cause regressions for users. Although models that are explicitly "Enabled" or "Disabled" at the enterprise level will keep those settings once you opt in to the preview, models that are currently delegated to organizations will be unavailable until they are enabled for specific teams. Filter your enterprise's model policy page by status to identify these models and choose which teams will receive access to them.
 
 For information on creating teams, see [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams).
 
@@ -88,7 +91,7 @@ For information on creating teams, see [AUTOTITLE](/enterprise-cloud@latest/admi
 
 To grant access to an enterprise team:
 
-1. Ensure models you want to enable for the team are set to "optional" in your enterprise's model policies.
+1. Ensure models you want to enable for the team are set to **Delegate to Enterprise Teams/Apps** in your enterprise's model policies.
 1. Access the settings for the team. See [AUTOTITLE](/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/create-enterprise-teams).
 1. Click the **Default models** tab.
 1. For each model that the team should receive access to beyond the enterprise baseline, set the dropdown to **Enabled**.

content/copilot/how-tos/administer-copilot/manage-for-organization/manage-default-models.md

@@ -18,21 +18,15 @@ allowTitleToDifferFromFilename: true
 
 If your organization is part of an enterprise, the enterprise owner controls which {% data variables.product.prodname_copilot_short %} models are available and how they can be configured at the organization level.
 
-<!-- expires 2026-08-26 -->
-<!-- unconfigured label will no longer exist -->
-
 When viewing the model settings for your organization, you may see the following statuses:
 
 * **Enabled** or **Disabled** with a {% octicon "shield" aria-label="shield" %} icon: The enterprise owner has enforced this setting. You cannot change the availability of this model.
-* **Enabled**, **Disabled**, or **Unconfigured** in a dropdown menu: The enterprise owner has made this model optional. You can configure the availability for your organization.
-
-> [!IMPORTANT] {% data reusables.copilot.model-autoenablement %}
-
-<!-- end expires 2026-08-26 -->
+* **Enabled** or **Disabled** in a dropdown menu: The enterprise owner has made this model optional. You can configure the availability for your organization.
+* **Delegate to Default Policy**: This model is available for you to configure, but no one has configured it in the organization. The model inherits the default set in the "Default availability" policy for your organization. See [AUTOTITLE](/copilot/concepts/models/default-availability).
 
 ## Configuring model availability for your organization
 
-If the enterprise owner has set a model to **Optional**, you can enable or disable it for your organization.
+If the enterprise owner has delegated a model to organizations, you can enable or disable it for your organization.
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}