Clarify authentication for data residency API requests

[becco]

GitHub Copilot generated this pull request.

Summary

Clarifies that every API request to GitHub Enterprise Cloud with data residency must be authenticated with an access token, including endpoints that do not require authentication on GitHub.com.

Validation

• npm run lint-content -- --precommit --paths content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md

Fixes github/api-platform#9973

[github-actions]

Thanks for submitting a PR to the GitHub Docs project!

In order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, see the documentation.

[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
admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md	ghec	ghec

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

🤖 This comment is automatically generated.

[Copilot]

Pull request overview

Clarifies authentication requirements for data residency API requests.

Changes:

• Requires authentication for all API requests, including normally unauthenticated endpoints.

Show a summary per file

File	Description
content/admin/data-residency/feature-overview-for-github-enterprise-cloud-with-data-residency.md	Documents API authentication requirements.

Review details

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Balanced

[Copilot]

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0 new
• Review effort level: Lite

[subatoi]

Thanks, @becco!