Repo sync

.github/workflows/confirm-internal-staff-work-in-docs.yml

@@ -73,7 +73,7 @@ jobs:
 
             core.setOutput('did_warn', 'true')
 
-      - name: Send Slack notification if a GitHub employee who isn't on the docs team opens an issue in public
+      - name: Send Slack notification if a GitHub employee who isn't on the Technical Content team opens an issue in public
         if: ${{ steps.membership_check.outputs.did_warn && github.repository == 'github/docs' }}
         uses: slackapi/slack-github-action@dcb1066f776dd043e64d0e8ba94ca15cc7e1875d # v4.0.0
         env:

.github/workflows/content-pipelines.yml

@@ -168,7 +168,7 @@ jobs:
             PR_BODY+="> * Internal or feature-flagged details that shouldn't be public"$'\n'
             PR_BODY+="> * Excessive or low-value detail"$'\n'
             PR_BODY+=">"$'\n'
-            PR_BODY+="> Cross-check changes against the source docs linked below. If in doubt, leave the review to a subject-matter expert on the docs team."$'\n\n'
+            PR_BODY+="> Cross-check changes against the source docs linked below. If in doubt, leave the review to a subject-matter expert on the Technical Content team."$'\n\n'
             PR_BODY+="## What this does"$'\n\n'
             PR_BODY+="Runs the \`content-pipeline-update\` agent (${PIPELINE_ID}) against the latest source docs and updates official articles under \`content/\` that have fallen out of sync."$'\n\n'
             PR_BODY+="## Source changes"$'\n\n'

.github/workflows/feedback-prompt.yml

@@ -1,4 +1,4 @@
-name: Feedback prompt for non-Docs team contributors when a PR is closed
+name: Feedback prompt for non-Technical Content team contributors when a PR is closed
 
 on:
   pull_request:

.github/workflows/hubber-contribution-help.yml

@@ -44,15 +44,15 @@ jobs:
       - name: Comment on the PR
         if: steps.membership_check.outputs.result == 'false'
         run: |
-          gh pr comment $PR --body "## Requesting a review from the Docs team
+          gh pr comment $PR --body "## Requesting a review from the Technical Content team
 
           ### 🚧 Draft PRs
 
           To add the PR to the Docs Content review board, click **Ready for review** in the merge box.
 
           ### 🚀 Non-draft PRs
 
-          The PR is **ready** and has automatically been added to the Docs Content review board. The docs team will review it as soon as possible.
+          The PR is **ready** and has automatically been added to the Docs Content review board. The Technical Content team will review it as soon as possible.
 
           ### Lead time for review
 

.github/workflows/needs-sme-stale-check.yaml

@@ -24,10 +24,10 @@ jobs:
         with:
           only-labels: needs SME
           days-before-stale: 28 # adds stale label if no activity for 7 days - temporarily changed to 28 days as we work through the backlog
-          stale-issue-message: 'This is a gentle reminder for the docs team that this issue is waiting for technical review by a subject matter expert (SME).'
+          stale-issue-message: 'This is a gentle reminder for the Technical Content team that this issue is waiting for technical review by a subject matter expert (SME).'
           stale-issue-label: 'Waiting on SME review'
           days-before-issue-close: -1 # never close
-          stale-pr-message: 'This is a gentle reminder for the docs team that this PR is waiting for technical review by a subject matter expert.'
+          stale-pr-message: 'This is a gentle reminder for the Technical Content team that this PR is waiting for technical review by a subject matter expert.'
           stale-pr-label: 'Waiting on SME review'
           days-before-pr-close: -1 # never close
 

.github/workflows/site-policy-reminder.yml

@@ -26,4 +26,4 @@ jobs:
           body: |
             Before merging, please remember to change the title of this PR to a description of its changes that is suitable for public viewing on github/site-policy.
 
-            <@github/site-policy-admins>, when these changes are ready to be synced to the site policy repo for the 24-hour or 30-day [review window](https://github.com/github/site-policy#whats-the-process), run the [site policy sync action](https://github.com/github/docs-internal/actions/workflows/site-policy-sync.yml) from this PR's branch. When these changes are ready to be merged in `docs-internal`, let the Docs team know on Slack in #docs-content and a writer will merge this PR.
+            <@github/site-policy-admins>, when these changes are ready to be synced to the site policy repo for the 24-hour or 30-day [review window](https://github.com/github/site-policy#whats-the-process), run the [site policy sync action](https://github.com/github/docs-internal/actions/workflows/site-policy-sync.yml) from this PR's branch. When these changes are ready to be merged in `docs-internal`, let the Technical Content team know on Slack in #docs-content and a writer will merge this PR.

.github/workflows/triage-stale-check.yml

@@ -69,8 +69,8 @@ jobs:
           days-before-pr-close: -1 # Never close
           operations-per-run: 100
 
-          stale-pr-message: 'This is a gentle reminder for the docs team that this pull request is waiting for review.'
-          stale-pr-label: 'Waiting on Docs team review'
+          stale-pr-message: 'This is a gentle reminder for the Technical Content team that this pull request is waiting for review.'
+          stale-pr-label: 'Waiting on Technical Content review'
 
       - name: Print outputs
         env:

content/admin/data-residency/network-details-for-ghecom.md

@@ -99,6 +99,10 @@ For more information about the `/meta` endpoint, see [AUTOTITLE](/rest/meta/meta
 | 40.81.180.112/28         | 40.81.176.224/28            |
 | 4.190.169.192/28         | 4.190.169.240/28            |
 
+## {% data variables.product.prodname_copilot %}
+
+Most {% data variables.product.prodname_copilot %} services require access to your enterprise's subdomain on {% data variables.enterprise.data_residency_site %} and its subdomains. For more information, see [AUTOTITLE](/copilot/reference/copilot-allowlist-reference#copilot-on-ghecom).
+
 ## Supported regions for Azure private networking
 
 {% data variables.product.company_short %} deploys your runners in the same Azure region as the subnet you connect them to. Because of this, your subnet must be in one of the supported regions. If you use Azure private networking for {% data variables.product.company_short %}-hosted runners, the supported Azure regions on {% data variables.enterprise.data_residency_site %} differ from those on {% data variables.product.prodname_dotcom_the_website %}.

content/copilot/concepts/agents/copilot-cli/about-copilot-cli.md

@@ -321,7 +321,7 @@ Alternatively, you can run {% data variables.copilot.copilot_cli_short %} in a v
 * **MCP servers in {% data variables.product.prodname_copilot_short %}**, which controls whether MCP servers can be used at all by {% data variables.product.prodname_copilot_short %}.
 * **MCP Registry URL**, which controls which MCP registry {% data variables.product.prodname_copilot_short %} will allow MCP servers to be used from.
 
-For more information about these policies, see [AUTOTITLE](/copilot/concepts/mcp-management#mcp-policy-settings).
+For more information about these policies, see [AUTOTITLE](/copilot/concepts/mcp-management#mcp-allowlists).
 
 ## Model usage
 

content/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-enterprise-allowlist.md

@@ -30,7 +30,7 @@ You can find these settings in the {% octicon "mcp" aria-hidden="true" aria-labe
 1. Create a `{% data variables.copilot.managed_setting_file %}` file for your enterprise. Most enterprises store this file in a `.github-private` repository. You can also install it directly on users' machines using mobile device management. See [AUTOTITLE](/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-agents/configure-enterprise-managed-settings#deploying-server-managed-settings).
 1. Edit the file to define an allowlist and denylist for MCP servers. You can match by name, server URL, or specific commands. For syntax details, see [allowedMcpServers](/copilot/reference/enterprise-managed-settings-reference#allowedMcpServers), and [deniedMcpServers](/copilot/reference/enterprise-managed-settings-reference#deniedMcpServers) in "Enterprise managed settings reference."
 
-   The following example allows servers that match any of the three allowlist entries. The server at `learn.microsoft.com` is always blocked, even if it also matches an allowlist entry.
+    The following example allows servers that match any of the three allowlist entries. The filesystem server configured to access the root filesystem is always blocked, even if it also matches an allowlist entry.
 
    ```json copy
    {
@@ -40,7 +40,14 @@ You can find these settings in the {% octicon "mcp" aria-hidden="true" aria-labe
        { "serverCommand": ["cmd", "/c", "uvx", "markitdown-mcp"] }
      ],
      "deniedMcpServers": [
-       { "serverUrl": "https://learn.microsoft.com/*" }
+       {
+         "serverCommand": [
+           "npx",
+           "-y",
+           "@modelcontextprotocol/server-filesystem",
+           "/"
+         ]
+       }
      ]
    }
    ```