Update data residency details for GitHub Copilot#44117
Update data residency details for GitHub Copilot#44117Sharra-writes merged 5 commits intogithub:mainfrom
Conversation
Clarified data residency information for GitHub Copilot, including details on data storage and compliance options.
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
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. |
There was a problem hiding this comment.
Pull request overview
Clarifies how {% data variables.product.prodname_copilot %} data is handled in the data residency “data stored outside your region” section, including what changes when an enterprise enables the data residency-compliant model restriction policy.
Changes:
- Expands the “{% data variables.product.prodname_copilot %} data” table row with default storage behavior and in-region behavior when the relevant policy is enabled.
- Adds a cross-reference link to the “{% data variables.product.prodname_copilot %} with data residency” article.
Show a summary per file
| File | Description |
|---|---|
| content/admin/data-residency/about-storage-of-your-data-with-data-residency.md | Updates the Copilot row in the “Data stored outside your region” table to clarify default vs policy-enabled behavior and link to Copilot-specific data residency details. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 3
| | Information that GitHub needs to administer a paid plan | <ul><li>Contact information</li><li>Billing, purchase, payment, or license information</li></ul> | | ||
| | Support and feedback data | <ul><li>Support requests or case notes</li><li>Phone conversations</li><li>Online chat sessions</li><li>Remote assistance sessions</li></ul> | | ||
| | {% data variables.product.prodname_copilot %} data | Data and logs for {% data variables.product.prodname_copilot %} | | ||
| | {% data variables.product.prodname_copilot %} data | Data and logs for {% data variables.product.prodname_copilot %} — by default stored outside your region. If you enable the Restrict Copilot to data residency compliant models policy, inference, prompts, responses, logs, and telemetry remain in-region. See [GitHub Copilot with data residency](./github-copilot-with-data-residency).| |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Clarified data residency information for GitHub Copilot, including details on data storage and compliance options.
I created this clarification as it is causing confusion with customer that are in regulated industries.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Clarification that we have got Copilot with EU Data residency in the meantime
Check off the following: