Answer: GitHub automatically resolves conflicts and applies a single active policy and registry. The resolution logic is: policies set by a parent enterprise override those set by an organization, Registry only takes precedence over Allow all since it is more restrictive, and if two policies have the same scope and strictness, the most recently uploaded registry is applied. Status: Confirmed Entry: tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution Revision: 3 Digest: sha256:cb51eaa3a21a76b4 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:32:25Z Last changed: 2026-11-18T13:10:25Z (recency rule: — → the most recently uploaded registry will be applied) Last verified: 2026-11-20T13:14:07Z Next check: 2026-11-21T13:14:07Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of resolution behavior | GitHub automatically resolves conflicts and applies a single active policy and registry | [1] | 2026-11-20 scope precedence | Policies set by a parent enterprise override those set by an organization | [1] | 2026-11-20 strictness precedence | Registry only is more restrictive than Allow all | [1] | 2026-11-20 recency rule | the most recently uploaded registry will be applied | [1] | 2026-11-20 Sources: [1] GitHub. "MCP private registry enforcement - GitHub Docs". https://docs.github.com/en/copilot/reference/enterprise-administrators/mcp-private-registry-enforcement Role: primary. Accessed: 2026-11-20T13:14:07Z Quote: "If a user has multiple seats, GitHub automatically resolves conflicts and applies a single active policy and registry." (Supports: resolution behavior) Quote: "Policies set by a parent enterprise override those set by an organization." (Supports: scope precedence) Quote: "Since Registry only is more restrictive than Allow all , it will always take precedence." (Supports: strictness precedence) Quote: "If two policies have the same scope and strictness, the most recently uploaded registry will be applied." (Supports: recency rule) Snapshot SHA-256: 12abe9c63f241dcfe5048e064adf7464718aa7b7a9bd7438fb9cac801183b68d (captured 2026-11-18T13:10:21Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-18T13:10:25Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:14:07Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:14:07Z Last attempt: 2026-11-20T13:14:07Z Notes and limitations: Extracted automatically from a single official source (section "Policy resolution for users with multiple seats"). Related: https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-prerequisites What are the prerequisites for configuring an MCP registry in GitHub Copilot? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-prerequisites-2 What are the prerequisites for restricting GitHub Copilot MCP server access to a custom registry? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-supported-surfaces Which GitHub Copilot surfaces does MCP private registry enforcement apply to? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-allowlist-prerequisites What are the prerequisites for configuring an MCP server allowlist in GitHub Copilot? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-enforcement-limitations What are the current limitations of GitHub Copilot MCP private registry enforcement? https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-local-server-enforcement How does GitHub Copilot enforce MCP private registry policy for local servers? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:10:25Z | changed | recency rule: — → the most recently uploaded registry will be applied | [1] 2026-11-18T13:10:25Z | changed | strictness precedence: — → Registry only is more restrictive than Allow all | [1] 2026-11-18T13:10:25Z | changed | scope precedence: — → Policies set by a parent enterprise override those set by an organization | [1] 2026-11-18T13:10:25Z | changed | resolution behavior: — → GitHub automatically resolves conflicts and applies a single active policy and registry | [1] 2026-11-18T13:10:25Z | changed | Recency rule: the most recently uploaded registry will be applied → — | [1] 2026-11-18T13:10:25Z | changed | Strictness precedence: Registry only is more restrictive than Allow all → — | [1] 2026-11-18T13:10:25Z | changed | Scope precedence: Policies set by a parent enterprise override those set by an organization → — | [1] 2026-11-18T13:10:25Z | changed | Conflict resolution: GitHub automatically resolves conflicts and applies a single active policy and registry → — | [1] 2026-11-16T12:58:30Z | changed | Strictness precedence: — → Registry only is more restrictive than Allow all | [1] 2026-11-16T12:58:30Z | changed | Scope precedence: — → Policies set by a parent enterprise override those set by an organization | [1] 2026-11-16T12:58:30Z | changed | Conflict resolution: — → GitHub automatically resolves conflicts and applies a single active policy and registry | [1] 2026-11-16T12:58:30Z | changed | Strictness rule: Registry only is more restrictive than Allow all → — | [1] 2026-11-16T12:58:30Z | changed | Scope rule: Policies set by a parent enterprise override those set by an organization → — | [1] 2026-11-16T12:58:30Z | changed | Resolution behavior: GitHub automatically resolves conflicts and applies a single active policy and registry → — | [1] 2026-11-13T03:32:25Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution POST: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How is MCP private registry policy resolved for GitHub Copilot users with multiple seats? Revision 3, last verified 2026-11-20T13:14:07Z. https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution (accessed 2026-11-21T10:06:55Z). @misc{LatestN_tool_github_copilot_admin_and_enterprise_mcp_registry_multi_seat_policy_resolution_r3, title = {How is MCP private registry policy resolved for GitHub Copilot users with multiple seats?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution}}, note = {Revision 3; digest sha256:cb51eaa3a21a76b4; last verified 2026-11-20T13:14:07Z; accessed 2026-11-21T10:06:55Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/admin-and-enterprise/mcp-registry-multi-seat-policy-resolution