github · docs-bot · Sep 7, 2026 · Sep 7, 2026 · Sep 7, 2026 · Sep 7, 2026
diff --git a/content/copilot/concepts/agents/cloud-agent/index.md b/content/copilot/concepts/agents/cloud-agent/index.md
@@ -11,7 +11,6 @@ children:
   - /about-custom-agents
   - /about-automations
   - /about-automation-rationale-and-approvals
-  - /access-management
   - /mcp-and-cloud-agent
   - /risks-and-mitigations
 contentType: concepts

diff --git a/content/copilot/concepts/agents/code-review.md b/content/copilot/concepts/agents/code-review.md
@@ -106,10 +106,9 @@ Code reviews have two cost components: {% data variables.product.prodname_ai_cre
 
 If a repository is configured to automatically request a code review from {% data variables.product.prodname_copilot_short %} for all new pull requests, the {% data variables.product.prodname_ai_credits_short %} consumption is attributed to the pull request author. If a review is manually requested by another user, the consumption is attributed to that user instead.
 
-If a pull request is created by {% data variables.product.prodname_actions %} or by a bot, the usage will apply to:
+For pull requests authored by {% data variables.copilot.copilot_cloud_agent %}, usage is attributed first to the human co-author associated with the change. If the co-author cannot be billed, usage is billed directly to the organization.
 
-* The user who triggered the workflow, if that user can be identified.
-* A designated billing owner.
+For pull requests authored by other bots, or when a bot requests the review, usage is billed directly to the organization. These pull requests are eligible for agentic review.
 
 ### What happens when a budget is reached
 

diff --git a/content/copilot/concepts/agents/copilot-cli/cancel-and-roll-back.md b/content/copilot/concepts/agents/copilot-cli/cancel-and-roll-back.md
@@ -17,7 +17,7 @@ category:
 When you work in an interactive {% data variables.copilot.copilot_cli_short %} session, you can press <kbd>Esc</kbd> or <kbd>Ctrl</kbd>+<kbd>C</kbd> to control what {% data variables.product.prodname_copilot_short %} is doing. Both keypresses can cancel operations, but they work slightly differently:
 
 * <kbd>Ctrl</kbd>+<kbd>C</kbd> acts immediately, without a confirming second press—removing any queued prompts first (one per press), then canceling the current operation.
-* A single <kbd>Esc</kbd> keypress gives you more gradual, staged control. While {% data variables.product.prodname_copilot_short %} is actively working, a single <kbd>Esc</kbd> doesn't cancel right away—it shows a reminder, and a second press carries out the next step: removing the most recently queued prompt, or canceling the operation once nothing is queued.
+* A single <kbd>Esc</kbd> keypress gives you more gradual, staged control. While {% data variables.product.prodname_copilot_short %} is actively working, a single <kbd>Esc</kbd> doesn't cancel right away—it shows a reminder, and a second press interrupts the current operation. In a local session, any queued prompts are then processed as the next turn. In a remote-backed or attached session, the second press fully cancels the operation instead, and queued prompts are not carried over to a follow-up turn.
 
 If {% data variables.product.prodname_copilot_short %} has already made changes and you want to undo them, you can roll back to a previous point in the session. As {% data variables.product.prodname_copilot_short %} works, {% data variables.copilot.copilot_cli_short %} tracks the file changes it makes as it responds to each prompt. This lets you rewind to an earlier point by pressing <kbd>Esc</kbd> twice when {% data variables.product.prodname_copilot_short %} is idle and the input area is empty. When you rewind, you choose whether to rewind the conversation only, or to also restore the files that {% data variables.product.prodname_copilot_short %} changed.
 
@@ -28,26 +28,25 @@ Pressing <kbd>Esc</kbd> once performs different actions depending on the current
 | Current state | What pressing <kbd>Esc</kbd> does |
 | ------------- | --------------------------------- |
 | {% data variables.product.prodname_copilot_short %} is active with no queued prompts. | Shows an "Esc again to cancel" reminder. The running operation is canceled only if you press <kbd>Esc</kbd> again within half a second. |
-| {% data variables.product.prodname_copilot_short %} is active and there are queued prompts. | Shows the "Esc again to cancel" reminder. Pressing <kbd>Esc</kbd> again removes the most recently queued prompt. |
+| {% data variables.product.prodname_copilot_short %} is active and there are queued prompts. | Shows the "Esc again to cancel" reminder. Pressing <kbd>Esc</kbd> again interrupts the current operation. In a local session, the queued prompts are then processed as the next turn; in a remote-backed or attached session, the operation is fully canceled and the queued prompts are not run as a follow-up turn. |
 | A permission dialog is open. | A single <kbd>Esc</kbd> denies the pending request (no second press needed). |
 | A dialog, overlay, or picker is open. | Closes the dialog, overlay, or picker. |
 | {% data variables.product.prodname_copilot_short %} is idle. | Shows a brief reminder that pressing <kbd>Esc</kbd> again quickly will open the rewind picker. See [Rolling back changes](#rolling-back-changes). |
 
-Pressing <kbd>Esc</kbd> twice quickly, when {% data variables.product.prodname_copilot_short %} is idle, allows you to roll back to an earlier point in the session. If an operation is in progress, a double <kbd>Esc</kbd> does one of the following, in this order of priority:
+Pressing <kbd>Esc</kbd> twice quickly, when {% data variables.product.prodname_copilot_short %} is idle and the input area is empty, allows you to roll back to an earlier point in the session. In other situations, a double <kbd>Esc</kbd> does one of the following, in this order of priority:
 
 * Cancels a running shell command.
 * Stops the current response.
 * Stops background agents.
 * Clears text in the input area.
-* Exits shell mode.
 
 If none of these applies, the rewind picker is displayed.
 
 ## When to use Esc instead of Ctrl+C
 
 The main difference between these two ways of canceling an operation is that <kbd>Esc</kbd> is designed for gradual, targeted intervention, while <kbd>Ctrl</kbd>+<kbd>C</kbd> is a hard stop.
 
-Use <kbd>Esc</kbd> when you want to interact with {% data variables.product.prodname_copilot_short %} without necessarily ending the current operation. For example, if a permission dialog appears and you want to deny that specific request, pressing <kbd>Esc</kbd> dismisses the dialog and {% data variables.product.prodname_copilot_short %} continues working—it just won't use the tool you denied. Similarly, if you've queued follow-up prompts and want to cancel them without interrupting the work already in progress, pressing <kbd>Esc</kbd> removes the most recently queued prompt (repeat to remove earlier ones), while the current operation keeps running.
+Use <kbd>Esc</kbd> when you want a confirming keypress before interrupting an operation. If a permission dialog appears and you want to deny that specific request, pressing <kbd>Esc</kbd> once rejects the request and stops the current operation. If you've queued follow-up prompts in a local session, pressing <kbd>Esc</kbd> twice interrupts the current operation and processes the queued prompts as the next turn. In a remote-backed or attached session, pressing <kbd>Esc</kbd> twice fully cancels the operation instead, and queued prompts are not run as a follow-up turn.
 
 Use <kbd>Ctrl</kbd>+<kbd>C</kbd> when you want to cancel without the confirming second press that <kbd>Esc</kbd> requires. If no prompts are queued, a single <kbd>Ctrl</kbd>+<kbd>C</kbd> immediately cancels the active operation. If you have queued prompts, each <kbd>Ctrl</kbd>+<kbd>C</kbd> removes the most recently queued prompt—one per press—and cancels the active operation only once the queue is empty. Any file write that is already in progress will complete—files are not left corrupted mid-write—but any remaining planned changes are abandoned. Pressing <kbd>Ctrl</kbd>+<kbd>C</kbd> a second time within two seconds, when the input area is empty, exits the session entirely.
 

diff --git a/content/copilot/concepts/agents/copilot-cli/tool-search.md b/content/copilot/concepts/agents/copilot-cli/tool-search.md
@@ -47,7 +47,7 @@ Tool search is enabled by default and activates automatically whenever you're on
 
 | Family | Supported versions |
 | ------ | ------------------ |
-| Claude (Anthropic) | Mythos Preview, Fable, Sonnet 4.0+, Opus 4.0+ (not Haiku) |
+| Claude (Anthropic) | Mythos Preview, Fable, Haiku 4.5+, Sonnet 4.0+, Opus 4.0+ |
 | GPT (OpenAI) | GPT-5.4 and later |
 
 On any other model, all tools are loaded up front.

diff --git a/content/copilot/concepts/agents/index.md b/content/copilot/concepts/agents/index.md
@@ -15,14 +15,11 @@ children:
   - /copilot-memory
   - /hooks
   - /about-plugins
-  - /about-enterprise-plugin-standards
   - /about-third-party-coding-agents
   - /agent-apps
   - /openai-codex
   - /anthropic-claude
   - /about-agent-skills
-  - /enterprise-management
-  - /opentelemetry
 contentType: concepts
 ---
 
diff --git a/...terprise-accounts-for-copilot-business.md → ...terprise-accounts-for-copilot-business.md b/...terprise-accounts-for-copilot-business.md → ...terprise-accounts-for-copilot-business.md
@@ -8,6 +8,7 @@ redirect_from:
   - /admin/copilot-business-only
   - /admin/copilot-business-only/about-enterprise-accounts-for-copilot-business
   - /early-access/copilot/managing-copilot-business-licenses-with-an-enterprise-account
+  - /copilot/concepts/about-enterprise-accounts-for-copilot-business
 contentType: concepts
 category:
   - Learn about Copilot

diff --git a/.../concepts/agents/enterprise-management.md → ...t/concepts/enterprise/agent-management.md b/.../concepts/agents/enterprise-management.md → ...t/concepts/enterprise/agent-management.md
@@ -1,12 +1,14 @@
 ---
 title: Agent management for enterprises
-shortTitle: Enterprise management
-intro: 'Maintain your enterprise''s security and compliance standards and supercharge your developers by managing agents with AI Controls.'
+shortTitle: Agent management
+intro: Maintain your enterprise's security and compliance standards and supercharge your developers by managing agents with AI Controls.
 versions:
   feature: copilot
 contentType: concepts
 category:
   - Learn about Copilot
+redirect_from:
+  - /copilot/concepts/agents/enterprise-management
 ---
 
 ## Overview
@@ -83,4 +85,3 @@ For more information, see [AUTOTITLE](/copilot/how-tos/administer-copilot/manage
 ## Agent mode in the IDE
 
 Enterprise and organization owners can separately control whether their users have access to agent mode in IDE chat, independently from the "Chat in IDE" policy. This gives you finer-grained control over agentic capabilities in your developers' IDEs.
-
diff --git a/...s/agents/cloud-agent/access-management.md → ...concepts/enterprise/cloud-agent-access.md b/...s/agents/cloud-agent/access-management.md → ...concepts/enterprise/cloud-agent-access.md
@@ -1,6 +1,6 @@
 ---
 title: Managing access to GitHub Copilot cloud agent
-shortTitle: Access management
+shortTitle: Cloud agent access
 allowTitleToDifferFromFilename: true
 intro: Find out about {% data variables.copilot.copilot_cloud_agent %} policies available for {% data variables.copilot.copilot_enterprise %} and {% data variables.copilot.copilot_for_business %}, and about disabling the agent for specific repositories.
 product: '{% data reusables.gated-features.copilot-cloud-agent %}<br><a href="https://github.com/features/copilot/plans?ref_product=copilot&ref_type=engagement&ref_style=button" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Sign up for {% data variables.product.prodname_copilot_short %}</span> {% octicon "link-external" height:16 %}</a>'
@@ -18,6 +18,7 @@ redirect_from:
   - /copilot/how-tos/agents/copilot-coding-agent/enabling-copilot-coding-agent
   - /copilot/concepts/agents/coding-agent/coding-agent-for-business-and-enterprise
   - /copilot/concepts/agents/coding-agent/managing-access
+  - /copilot/concepts/agents/cloud-agent/access-management
 contentType: concepts
 category:
   - Manage Copilot for a team

diff --git a/...t/concepts/models/default-availability.md → .../enterprise/default-model-availability.md b/...t/concepts/models/default-availability.md → .../enterprise/default-model-availability.md
@@ -1,6 +1,6 @@
 ---
 title: About default availability of {% data variables.product.prodname_copilot_short %} models
-shortTitle: Default availability
+shortTitle: Default model availability
 intro: A policy controls whether unconfigured models default to enabled or disabled.
 product: '{% data variables.copilot.copilot_business_short %} and {% data variables.copilot.copilot_enterprise_short %}'
 versions:
@@ -11,6 +11,8 @@ category:
   - Manage Copilot for a team
 redirect_from:
   - /copilot/concepts/models/automatic-enablement
+  - /copilot/concepts/models/default-availability
+  - /copilot/concepts/enterprise/default-availability
 ---
 
 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.

diff --git a/...copilot/concepts/models/fedramp-models.md → ...lot/concepts/enterprise/fedramp-models.md b/...copilot/concepts/models/fedramp-models.md → ...lot/concepts/enterprise/fedramp-models.md
@@ -8,6 +8,7 @@ product: '{% data variables.enterprise.data_residency %}'
 contentType: concepts
 redirect_from:
   - /copilot/concepts/fedramp-models
+  - /copilot/concepts/models/fedramp-models
 ---
 
 If your enterprise uses {% data variables.enterprise.data_residency %} in the US, you can enable a policy to ensure that users on your {% data variables.product.prodname_copilot_short %} plan can only use models with **FedRAMP Moderate** certification.

diff --git a/content/copilot/concepts/enterprise/index.md b/content/copilot/concepts/enterprise/index.md
@@ -0,0 +1,20 @@
+---
+title: Enterprise concepts for GitHub Copilot
+shortTitle: Enterprise
+intro: Understand how to govern and manage {% data variables.product.prodname_copilot %} across your enterprise.
+versions:
+  feature: copilot
+children:
+  - /policies
+  - /default-model-availability
+  - /fedramp-models
+  - /learning-about-new-features-and-models
+  - /agent-management
+  - /mcp-management
+  - /plugin-standards
+  - /opentelemetry
+  - /cloud-agent-access
+  - /about-enterprise-accounts-for-copilot-business
+contentType: concepts
+---
+
diff --git a/...learning-about-new-features-and-models.md → ...learning-about-new-features-and-models.md b/...learning-about-new-features-and-models.md → ...learning-about-new-features-and-models.md
@@ -9,6 +9,7 @@ category:
   - Learn about Copilot
 redirect_from:
   - /copilot/concepts/preparing-for-new-features-and-models
+  - /copilot/concepts/learning-about-new-features-and-models
 ---
 
 {% data variables.product.prodname_copilot %} is evolving rapidly, with new features and models released regularly. If you're an enterprise administrator, staying informed helps you make confident decisions about which capabilities to enable, when to adopt them, and how to manage risk across your organizations.

diff --git a/content/copilot/concepts/mcp-management.md → ...lot/concepts/enterprise/mcp-management.md b/content/copilot/concepts/mcp-management.md → ...lot/concepts/enterprise/mcp-management.md
@@ -1,13 +1,15 @@
 ---
 title: MCP server usage in your company
 shortTitle: MCP management
-intro: 'You can manage MCP server usage to provide your developers with valuable tools while maintaining security and compliance.'
+intro: You can manage MCP server usage to provide your developers with valuable tools while maintaining security and compliance.
 versions:
   feature: copilot
 contentType: concepts
 category:
   - Learn about Copilot
   - Manage Copilot for a team
+redirect_from:
+  - /copilot/concepts/mcp-management
 ---
 
 {% data reusables.copilot.mcp.intro %}

diff --git a/.../copilot/concepts/agents/opentelemetry.md → ...ilot/concepts/enterprise/opentelemetry.md b/.../copilot/concepts/agents/opentelemetry.md → ...ilot/concepts/enterprise/opentelemetry.md
@@ -7,6 +7,8 @@ versions:
 contentType: concepts
 category:
   - Manage Copilot for a team
+redirect_from:
+  - /copilot/concepts/agents/opentelemetry
 ---
 
 OpenTelemetry (OTel) is an open source observability framework. It provides a standard way to collect telemetry events and metrics and export them to compatible observability tools. For more information, see [What is OpenTelemetry?](https://opentelemetry.io/docs/what-is-opentelemetry/) on the OTel website.

diff --git a/...ents/about-enterprise-plugin-standards.md → ...t/concepts/enterprise/plugin-standards.md b/...ents/about-enterprise-plugin-standards.md → ...t/concepts/enterprise/plugin-standards.md
@@ -1,6 +1,6 @@
 ---
 title: About enterprise-managed plugin standards
-shortTitle: Enterprise plugin standards
+shortTitle: Plugin standards
 allowTitleToDifferFromFilename: true
 intro: Enterprise administrators can centrally define plugin policies for users, ensuring consistent plugin availability.
 versions:
@@ -13,6 +13,7 @@ docsTeamMetrics:
   - copilot-cli
 redirect_from:
   - /copilot/concepts/agents/copilot-cli/about-enterprise-plugin-standards
+  - /copilot/concepts/agents/about-enterprise-plugin-standards
 ---
 
 Enterprise-managed plugin standards allow administrators to **define and enforce policies for plugin availability**. By configuring a `{% data variables.copilot.managed_setting_file %}` file, administrators can specify which plugin marketplaces are available to users and which plugins are installed automatically.

diff --git a/content/copilot/concepts/policies.md → ...t/copilot/concepts/enterprise/policies.md b/content/copilot/concepts/policies.md → ...t/copilot/concepts/enterprise/policies.md
@@ -6,6 +6,8 @@ intro: 'Control the availability of {% data variables.product.prodname_copilot %
 versions:
   feature: copilot
 contentType: concepts
+redirect_from:
+  - /copilot/concepts/policies
 category:
   - Manage Copilot for a team
 ---
@@ -26,7 +28,7 @@ A small number of policies work differently and govern a setting for everyone. F
 
 ## What about users with multiple licenses?
 
-A user can receive access to {% data variables.product.prodname_copilot_short %} from multiple organizations in the same enterprise. If these organizations have configured the same policy differently, the **least restrictive** policy usually applies, but there are some exceptions. 
+A user can receive access to {% data variables.product.prodname_copilot_short %} from multiple organizations in the same enterprise. If these organizations have configured the same policy differently, the **least restrictive** policy usually applies, but there are some exceptions.
 
 More rarely, if a user receives a license from multiple different enterprises, the **most restrictive** policy across enterprises almost always applies. For example, if any enterprise disables {% data variables.copilot.copilot_chat_dotcom_short %}, that feature is disabled for the user.
 

diff --git a/content/copilot/concepts/index.md b/content/copilot/concepts/index.md
@@ -16,10 +16,8 @@ children:
   - /models
   - /usage-limits
   - /billing
-  - /about-enterprise-accounts-for-copilot-business
-  - /policies
-  - /mcp-management
   - /network-settings
-  - /learning-about-new-features-and-models
+  - /enterprise
 contentType: concepts
 ---
+
diff --git a/content/copilot/concepts/models/index.md b/content/copilot/concepts/models/index.md
@@ -6,11 +6,9 @@ versions:
   feature: copilot
 contentType: concepts
 children:
-  - /default-availability
   - /bring-your-own-key
   - /utility-models
   - /auto-model-selection
-  - /fedramp-models
   - /fallback-and-lts-models
 ---
 
diff --git a/content/copilot/how-tos/administer-copilot/manage-for-enterprise/index.md b/content/copilot/how-tos/administer-copilot/manage-for-enterprise/index.md
@@ -8,6 +8,7 @@ children:
   - /manage-plan
   - /manage-access
   - /manage-enterprise-policies
+  - /use-managed-settings
   - /manage-agents
   - /manage-availability-of-default-models
   - /enable-custom-models