Clarify that content exclusion requires Copilot Business or Enterprise plan

[samueltauil]

Why

The Excluding content from GitHub Copilot how-to page and the Content exclusion concepts page do not explicitly state that repository-level content exclusion settings require the repository to belong to an organization with a Copilot Business or Enterprise plan.

While the page has a product frontmatter gate that renders a banner, the banner is easy to miss. The repository configuration section begins with "You can use your repository settings…" without clarifying that the Copilot option will not appear for repositories owned by personal accounts (even with Copilot Pro or Pro+).

This leads to confusion when users follow the instructions and cannot find the settings.

What

How-to page (exclude-content-from-copilot.md):

• Adds a > [!NOTE] callout in the "Configuring content exclusion for your repository" section explicitly stating the plan and organization ownership requirement, and that personal-account repos will not show the Copilot settings option.

Concepts page (content-exclusion.md):

• Expands the "Who can configure content exclusion" section to explicitly list the plan requirement (Copilot Business or Enterprise) and clarify that personal-account plans (Copilot Free, Pro, Pro+) are not eligible.

Validation

• All {% data variables %} references verified against data/variables/copilot.yml
• Changes follow existing doc conventions (NOTE callouts, variable references)
• No structural or formatting changes to surrounding content

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
copilot/concepts/context/content-exclusion.md	fpt ghec	fpt ghec
copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md	fpt ghec	fpt ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

Clarifies eligibility requirements for repository-level content exclusion so readers understand it requires an organization-owned repository with a Copilot Business or Copilot Enterprise plan (and won’t appear for personal-account repositories).

Changes:

• Added a NOTE callout to the how-to page to state the organization ownership + plan requirement and clarify UI visibility for personal accounts.
• Expanded the concepts page “Who can configure content exclusion” section to explicitly document plan eligibility and ineligibility for personal-account plans.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
content/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot.md	Adds an eligibility NOTE in the repository configuration section to reduce user confusion about missing settings.
content/copilot/concepts/context/content-exclusion.md	Explicitly documents plan requirements and clarifies that personal-account plans are not eligible for content exclusion settings.

[Copilot]

There are two consecutive alert callouts (> [!NOTE]) here (lines 33–37). Our content style guidelines recommend avoiding consecutive alerts; consider merging these into a single NOTE (e.g., include both the plan/org-ownership requirement and the unsupported-tools note in one callout), and trim the repeated plan/subscription sentence to keep the alert concise.

Suggested change

	> Content exclusion settings are only available for repositories owned by an organization with a {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} plan. If your repository is owned by a personal account, the **{% data variables.product.prodname_copilot_short %}** option will not appear in your repository settings. To configure content exclusion, the repository must belong to an organization that has a {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} subscription.
	> [!NOTE]
	> {% data variables.copilot.copilot_cli %}, {% data variables.copilot.copilot_cloud_agent %}, and Agent mode in {% data variables.copilot.copilot_chat_short %} in IDEs, do not support content exclusion. For more information about these {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli), [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent), and [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide).
	> Content exclusion settings are only available for repositories owned by an organization with a {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} plan. If your repository is owned by a personal account, the **{% data variables.product.prodname_copilot_short %}** option will not appear in your repository settings. {% data variables.copilot.copilot_cli %}, {% data variables.copilot.copilot_cloud_agent %}, and Agent mode in {% data variables.copilot.copilot_chat_short %} in IDEs do not support content exclusion. For more information about these {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/concepts/agents/about-copilot-cli), [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent), and [AUTOTITLE](/copilot/how-tos/chat-with-copilot/chat-in-ide).