Clarify "do not create an organization" warning for Copilot Business standalone setup#44596
Conversation
…alone setup The previous warning was a single unbolded paragraph buried under the trial button. Customers setting up a dedicated enterprise account for Copilot Business were missing it, creating an organization during the trial flow, and getting billed for GitHub Enterprise licenses they did not need. Changes: - Promote the warning to a [!WARNING] callout so it visually stands out - State the explicit goal-state (0 seats of GitHub Enterprise) - Add the consequence (billing for GitHub Enterprise) so readers understand the cost impact, not just the policy - Tell the reader what to do instead (add users directly to the enterprise) - Add one line calling out that this path is correct for ADO-only / non- GitHub-hosted code customers, which is the most common scenario for Copilot Business standalone Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the setup instructions for creating a dedicated enterprise account for Copilot Business by emphasizing license/billing implications and clarifying the recommended configuration.
Changes:
- Replaces a single caution sentence with a structured warning callout explaining why not to create an organization.
- Adds explicit guidance to keep the enterprise at 0 GitHub Enterprise seats and to add users directly to the enterprise.
- Adds additional context for customers whose code is hosted outside GitHub (e.g., Azure DevOps).
Show a summary per file
| File | Description |
|---|---|
| content/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-a-dedicated-enterprise-for-copilot-business.md | Clarifies enterprise setup to avoid unintended GitHub Enterprise licensing and adds a recommended-path note for non-GitHub code hosting. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
| > **Do not create an organization during setup.** This enterprise account exists only as a billing and identity container for {% data variables.copilot.copilot_business_short %} licenses - it should have **0 seats of {% data variables.product.prodname_enterprise %}** when you are done. | ||
| > | ||
| > Creating an organization, or adding users to an organization later, will assign {% data variables.product.prodname_enterprise %} licenses and bill your account for {% data variables.product.prodname_enterprise %} - which you do not need for {% data variables.copilot.copilot_business_short %}. | ||
| > | ||
| > Instead, add users **directly to the enterprise** (see the next section). They will receive {% data variables.copilot.copilot_business_short %} licenses without any {% data variables.product.prodname_enterprise %} cost. |
github-actions
Bot
added
the
triage
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
|
Closing - I should have opened this in the private |
Why
Customers setting up a dedicated enterprise account for Copilot Business standalone (no GitHub Enterprise) are repeatedly creating an organization during the trial flow because the warning in the current article is a single, unbolded paragraph buried under the trial button. This results in surprise GitHub Enterprise license assignments and billing, which then has to be walked back via Support.
What changed
[!WARNING]callout so it visually stands out from the surrounding setup instructions.Signal from the field
Multiple Digital Sales reps and SDRs have flagged this in internal channels when customers ask why they are being billed for GitHub Enterprise they did not intend to buy. There is an internal text expander maintained by Sales that calls this step out as its own bold heading - this PR brings the public docs closer to that internal guidance.
Preview
Before: one short paragraph easily scrolled past.
After: a
[!WARNING]callout with bolded directive, consequence, goal-state, and the corrective action.