Microsoft AI系統編 — Microsoft Copilot / Copilot Studio / Microsoft Foundry / GitHub Copilot / Microsoft Graph・SharePoint・Teamsを「一つの製品」としてではなく、相互に接続される複数のAI運用面として記述するための境界地図

台帳EA-002はMicrosoft 365 Copilot、Copilot Studio、Foundry、GitHub Copilot、Teams、SharePoint、OneDrive等を一つの系統として扱う構想である。2026年9月時点では名称・製品境界・Agent経路が急速に再編されており、Microsoft 365 Copilotは公式文書上「Microsoft Copilot」へ改称中である一方、Copilot Studio、Microsoft Foundry、GitHub Copilotは別ライセンス・別管理面・別監査面を持つ。公開後版では単一の「Microsoft Copilot」機能表ではなく、利用者面・maker面・pro-code runtime面・developer面・data/identity/governance面を分離した系統地図が必要である。

Enterprise AI Core: identity/permission-aware retrieval、agent governance、connector/data movement、audit/retention、availability gate。 Provider mapping: Microsoft ecosystem。 Organization overlay: Microsoft Entra、Microsoft 365 admin center、Teams/SharePoint/Purview/Power Platform管理、GitHub Enterprise policy。 Interoperability: Microsoft Graph、Copilot connectors、MCP-based federated connectors、Agent Store/Agent Registry、Teams/Microsoft Copilot publishing。 Implementation: Copilot Studio standard harness、Microsoft Foundry Agent Service、GitHub Copilot enterprise controls。

Q1. Microsoft AI系統は、Microsoft Copilotを中心とする単一製品群としてではなく、複数のruntime・管理面・データ境界を持つ接続系として記述すべきか。 Q2. M365/Graph/SharePointの既存permissionを尊重することは、oversharingを防ぐ十分条件か。 Q3. Copilot StudioとFoundryは同じ「agent builder」として同格に比較できるか、それともmaker SaaSとpro-code runtimeとして別レイヤーか。 Q4. GitHub CopilotはMicrosoft系統に含めつつも、Microsoft 365 tenant governanceとは別のGitHub enterprise policy/audit境界として分離すべきか。

• source class: official architecture documentation exact title: Microsoft Copilot architecture and how it works author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-architecture publication/update/access: last updated 2026-08-18 / accessed 2026-09-11 version/release: current Microsoft Copilot architecture evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / boundary supporting locator: tenant/service boundary; User prompts and Copilot responses; User access and data privacy; Conditional Access and MFA established: CopilotはMicrosoft 365 service boundary内でMicrosoft Graphをgroundingに利用するがtenant-wide visibilityを自動取得せず、signed-in userの既存権限を境界とする。Conditional Access/MFAも既存M365制御を継承する。

• source class: official privacy/security documentation exact title: Data, Privacy, and Security for Microsoft Copilot author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy publication/update/access: last updated 2026-07-09 / accessed 2026-09-11 version/release: current; document states Microsoft 365 Copilot is now named Microsoft Copilot evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / limit / naming-change supporting locator: introductory Note; organizational data; stored interaction data; extensibility; connected experiences controls established: prompts/responses/Graph-accessed dataはfoundation LLM trainingに使われない。interaction contentは保存され、Purview retention/eDiscovery対象となり得る。agents/Graph connectorsは拡張経路であり、admin permissionとagent側terms/privacyの確認が必要。connected experiences privacy controlsを無効化すると一部Copilot機能自体が利用不能になる。名称移行中で旧称が資料・license・capabilityに残る。

• source class: official SharePoint governance documentation exact title: Restrict discovery of SharePoint sites and content author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/sharepoint/restricted-content-discovery publication/update/access: last updated 2026-08-18 / accessed 2026-09-11 version/release: Restricted Content Discovery current evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: counter / limit / governance supporting locator: notes/caution; prerequisites; propagation; FAQ established: RCDはdiscoverabilityを制限するが既存permissionsを変更しない。SharePoint siteだけが対象でOneDrive sites非対応。過剰適用はCopilot responseの完全性・関連性を下げ得る。500,000 items超のsiteでは反映に1週間超かかる場合がある。よって「permission-respecting=oversharing解決済み」は成立しない。

• source class: official retirement/governance documentation exact title: Restricted SharePoint Search author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/sharepoint/restricted-sharepoint-search publication/update/access: accessed 2026-09-11; new enablement blocked from 2026-07-31 evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: counter / migration-limit supporting locator: retirement notice; What is Restricted SharePoint Search; Why disable after validation established: RSSは短期対策でsecurity boundaryではなく、2026-07-31から新規enablementがblocked。長期策としてRCD、SharePoint Advanced Management、Purview等へ移行する必要がある。公開後辞典ではRSSを現行推奨策として固定しない。

• source class: official Copilot Studio licensing/access documentation exact title: Assign user licenses and manage access author/org: Microsoft Copilot Studio canonical URL: https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-licensing publication/update/access: last updated 2026-08-03 / accessed 2026-09-11 version/release: current standard harness licensing evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / availability gate / cost supporting locator: required tenant+user licenses; Teams plan; trial; subscription capacity established: Copilot Studio maker accessはtenant licenseとuser license等に依存する。Teams planはclassic orchestration中心で、standaloneとはgenerative orchestration・premium connectors・channels等が異なる。trialでは作成/テストは可能でもpublish不可。agent利用者とmakerのlicense要件も同一ではない。

• source class: official Copilot Studio implementation guidance exact title: Apply generative orchestration capabilities author/org: Microsoft Copilot Studio canonical URL: https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/generative-orchestration publication/update/access: last updated 2026-08-27 / accessed 2026-09-11 version/release: current standard harness evidence label: VERIFIED_SPEC relation: support / implementation supporting locator: generative orchestration; autonomous capabilities; multi-agent orchestration; custom knowledge established: Copilot StudioはLLM-based orchestrationでtopics/actions/knowledgeを選択し、event-driven autonomous agent、multi-agent coordination、custom knowledge integrationまで扱う。単なるM365 Copilotのprompt extensionではない。

• source class: official pro-code agent runtime documentation exact title: What is Microsoft Foundry Agent Service? author/org: Microsoft Foundry canonical URL: https://learn.microsoft.com/en-us/azure/foundry/agents/overview publication/update/access: last updated 2026-08-19 / accessed 2026-09-11 version/release: current Foundry Agent Service evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / implementation / boundary supporting locator: Agent Service at a glance; Agent types; Security, privacy, and compliance established: Foundry Agent ServiceはAgent Runtime、toolboxes/MCP、model catalog、observability/evaluations、Entra/RBAC/VNet、versioned publishingを備える。prompt agentsとhosted agentsを提供し、Teams/Microsoft Copilot/Entra Agent Registryへpublish可能。Copilot Studioと接続可能だが、hosting/scaling/identity/observabilityを含むpro-code runtimeとして独立レイヤーを持つ。

• source class: official connector architecture documentation exact title: Copilot connectors overview author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/overview publication/update/access: last updated 2026-08-04 / accessed 2026-09-11 version/release: current Copilot connectors evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / interoperability supporting locator: connector architecture; prebuilt/custom connectors established: 外部データ接続にはsynced connectorとfederated connector系統があり、syncedはMicrosoft Graphへ取り込み/semantic indexing、federatedはMCPを使うquery-time retrievalでsource側にデータを残す。データ移動・index・authentication・availabilityが異なるため「connector」を単一方式として扱えない。

• source class: official publishing/distribution documentation exact title: Connect and configure an agent for Teams and Microsoft 365 Copilot author/org: Microsoft Copilot Studio canonical URL: https://learn.microsoft.com/en-us/microsoft-copilot-studio/publication-add-bot-to-microsoft-teams publication/update/access: accessed 2026-09-11 evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / availability gate supporting locator: install; share link; Teams app store / Microsoft 365 Agent Store; admin approval established: agentのpublish、userへのshare、organization catalogへの展開は別工程であり、organization-wide availabilityにはadmin approvalが関わる。作成済み・publish済み・利用可能・組織配布済みを同一状態として扱えない。

• source class: official agent governance documentation exact title: Agent Store in Microsoft Copilot author/org: Microsoft canonical URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/copilot-agent-store publication/update/access: last updated 2026-04-20 / accessed 2026-09-11 version/release: current Agent Store / Agent 365 path evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / governance / interoperability supporting locator: admin approval; Agent 365 SDK integration established: Agent Storeにはadmin approvalがあり、Copilot Studio/Foundry/OpenAI Agents SDK/custom code等で構築したagentをAgent 365 SDK経由でEntra-backed identity、managed MCP、observability等へ接続する経路が示される。Microsoft系統は自社builderだけを閉じた世界として記述すべきでない。

• source class: official GitHub enterprise governance documentation exact title: GitHub Copilot policies for enterprises and organizations author/org: GitHub canonical URL: https://docs.github.com/en/copilot/concepts/enterprise/policies publication/update/access: accessed 2026-09-11 evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / boundary / availability gate supporting locator: policy hierarchy; user licenses; supported surfaces; policy drift established: GitHub Copilot Business/EnterpriseはGitHub enterprise/organizationのAI controlsでfeatures/agents/models/clientを統制する。複数organization/enterpriseのpolicy競合ルールがあり、IDE/GitHub web/CLIで適用surfaceも同一ではない。M365 admin policyと混ぜず別管理面にする必要がある。

• source class: official GitHub audit documentation exact title: Reviewing audit logs for GitHub Copilot author/org: GitHub canonical URL: https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot/manage-for-enterprise/review-audit-logs publication/update/access: accessed 2026-09-11 version/release: current GitHub Enterprise Cloud evidence label: VERIFIED_SPEC relation: support / audit-limit supporting locator: logged events; client-session exclusion; retention established: enterprise audit logはpolicy/license changesとGitHub website agent activity等を記録するが、local Copilot prompt等のclient session dataは含まれず、必要ならcustom hooks等の別収集が必要。audit coverageはsurfaceごとに差がある。

• source class: official GitHub content-control documentation exact title: Content exclusion for GitHub Copilot author/org: GitHub canonical URL: https://docs.github.com/en/enterprise-cloud@latest/copilot/concepts/context/content-exclusion publication/update/access: accessed 2026-09-11 version/release: current; some surfaces public preview label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: counter / failure envelope supporting locator: availability; limitations established: content exclusionはBusiness/Enterpriseで利用可能だが、surface差があり、Edit/Agent modes等で非対応の場合がある。IDEから間接的に得たsemantic information等を完全遮断する保証でもない。Microsoft系統全体の「content governance」を一つの万能controlとして表現できない。

• source class: official GitHub model hosting/data-boundary documentation exact title: Hosting of models for GitHub Copilot author/org: GitHub canonical URL: https://docs.github.com/en/copilot/reference/ai-models/model-hosting publication/update/access: accessed 2026-09-11 version/release/model: current multi-provider model catalog; provider/model-dependent retention terms evidence label: VERIFIED_SPEC + PRODUCT_VOLATILE relation: support / limit / data-boundary supporting locator: provider hosting and retention sections established: GitHub Copilot内部でもOpenAI/Anthropic/Google等の複数model providerが使われ、provider/model/preview状態によりZDRやretention条件が異なり得る。Microsoft ecosystemだからdata pathがMicrosoft単独で閉じるとは限らない。

EA-002は採用価値が高いが、章構造は製品一覧ではなく「六面図」にするのが安全である。 A. End-user productivity plane: Microsoft Copilot + Word/Excel/PowerPoint/Outlook/Teams等。Microsoft Graphとuser permissionでgrounding。 B. Maker/low-code agent plane: Copilot Studio。agent作成、knowledge/actions、generative orchestration、Power Platform/Teams接続、publishing。 C. Pro-code/model/runtime plane: Microsoft Foundry。model catalog、agent hosting/runtime、tools/MCP、identity/network、observability/evaluation。 D. Developer-assistance plane: GitHub Copilot。GitHub enterprise/org policy、IDE/web/CLI、model-provider policy、独自audit/content controls。 E. Data/retrieval plane: Microsoft Graph、SharePoint/OneDrive、Copilot connectors。synced indexとfederated/MCP retrievalを分離。 F. Governance/distribution plane: Entra、M365 admin、Purview、SharePoint governance、Agent Store/Agent Registry、Teams distribution、GitHub AI controls。 これらは相互接続するが、license、admin authority、audit coverage、data path、availability gateを共有しない場合がある。したがって「Microsoft製AI」の一語で統合すると運用判断を誤る。

重要な反証は、permission-aware retrievalがoversharingを自動修復しない点である。Copilotは既存permissionを尊重するが、既存permission自体が広すぎれば広すぎる範囲を正しく利用する。RCD/RSS/SAM/Purview等の治理はpermission modelとは別レイヤーである。

また名称変動が大きい。2026-07-09更新のMicrosoft文書は「Microsoft 365 Copilot is now named Microsoft Copilot」と明記する一方、URL、license、他文書には旧称が残る。辞典の索引はcurrent canonical name + historical/transition aliasを併記する必要がある。

• Microsoft製品間で「Copilot」「agent」「connector」「MCP」という語が共通でも、security boundary、runtime、license、admin surface、audit coverageは同一ではない。
• Microsoft Copilotがuser permissionを尊重しても、overshared site/fileはuserに許可済みであるためCopilotにも見える。permission-awareはdata hygieneの代替ではない。
• RCDはpermissionsそのものを変えず、OneDrive sites非対応、反映遅延もあり得る。RSSはretiringでsecurity boundaryではない。
• Copilot Studio trial/Teams plan/standaloneはcapability差が大きい。maker accessとend-user accessを混同しない。
• Foundryの多model/外部model接続、GitHub Copilotのmulti-provider hostingにより「Microsoft系=Microsoft modelのみ」は誤り。
• GitHub Copilot content exclusionは全surface/agent modeへの完全適用ではない。policy/auditもsurface差がある。
• Foundry/Agent 365/Agent Registry/Frontier系は2026年に変動が速く、公開直前再確認が必要。

Microsoft Copilot: M365 subscription/entitlement、user identity、Graph permissions、connected-experience privacy controls、admin-enabled agents、region/data-residency条件。 Copilot Studio: tenant/user licenseまたは該当entitlement、Power Platform environment、Teams plan vs standalone、capacity/Copilot Credits、publish permission、channel/admin approval。 Foundry: Azure subscription/project、model availability、region、Entra/RBAC、network/resource configuration、preview/GA状態。 Copilot connectors: connector type、Entra/app registration、admin consent、source credentials、sync/federated availability、government/cloud environment差。 GitHub Copilot: Business/Enterprise seat、enterprise/org AI policies、client/surface、model policy、data-residency/FedRAMP constraints、provider/model retention条件。 Agent distribution: share/publish/catalog submission/admin approval/installationは別状態。

Microsoft Copilot: production SaaS orchestration/service boundary。 Copilot Studio: maintained low-code/maker agent platform。standard harnessでgenerative/multi-agent/autonomous capabilitiesを提供。 Microsoft Foundry Agent Service: maintained pro-code agent runtime/hosting/evaluation/identity platform。prompt agentとhosted agentを分離。 Copilot connectors: production integration architecture。synced Graph indexingとfederated MCP retrievalの二方式。 Agent Store/Agent Registry/Agent 365: cross-platform governance/distribution layerだが2026年の変動が大きくPRODUCT_VOLATILE。 GitHub Copilot: production developer AI platform with separate enterprise governance surface。

本RUNでは能力benchmarkを行わない。EA-002の目的はecosystem topologyとgovernance boundaryの確定であり、model性能をMicrosoft製品性能へ外挿しない。将来比較する場合は、(1) task completion、(2) permission leakage/oversharing exposure、(3) connector freshness/latency、(4) agent tool-call success、(5) audit completeness、(6) policy propagation latencyを製品面ごとに独立評価する。

Security: identity/permission boundaryとdiscoverability/data hygieneを分離。Entra/M365/Power Platform/GitHub policyのauthority mapを持つ。 Privacy: foundation-model training非利用の約束と、interaction retention/eDiscovery、外部agent/provider termsを別項目にする。 Audit: M365/PurviewとGitHub auditは別系統。client/local sessionが標準auditに含まれないsurfaceもある。 Cost: M365 entitlement、Copilot Studio Credits/capacity、Azure/Foundry consumption、GitHub AI Credits/seatを統合単価にしない。 Operability: create→test→publish→share→catalog/admin approve→install/useを状態機械として分離。policy/connector/index propagation delayを即時反映と仮定しない。

「Microsoftの法人向けAIは、一つのCopilot製品ではなく、複数の運用面が接続した系統として見る方が安全である。Microsoft CopilotはMicrosoft 365の権限とGraphを使う利用者面、Copilot Studioは業務エージェントを組み立てるmaker面、Microsoft Foundryはモデル・ツール・実行・観測を扱うpro-code面、GitHub Copilotは開発者向けの別管理面を持つ。これらはTeams、SharePoint、Graph、MCP、Agent Store等で接続できるが、ライセンス、管理者、監査、データ経路、利用可能条件まで同一になるわけではない。特に『既存権限を尊重する』ことと『既存データが適切に権限設定されている』ことは別問題である。」

• 公開直前にMicrosoft naming mapを再採集し、Microsoft Copilot / Microsoft Copilot Chat / legacy Microsoft 365 Copilot表記、Copilot Studio、Foundry、Agent 365、Agent Registryのcanonical名を固定する。
• 六面図を章の主構造候補とし、各面に「identity / data source / runtime / admin authority / audit / billing meter / publication path / region」を列として持つ。
• M365 data planeはSharePoint、OneDrive、Teams、Exchange/Outlook、Graph、Copilot connectorsを分離し、native Graph content / synced external content / federated MCP contentのdata movementを図示する。
• permission-aware retrieval節には必ずoversharing counterexampleとRCD/RSSの限界を併記する。RSSはretirement history扱いとしcurrent recommendationから外す。
• Copilot StudioはTeams plan / standalone / trial / M365-integrated agent entitlementを公開時点で再照合し、maker vs consumer licenseを分離する。
• FoundryはAgent Service、model catalog、Responses/API/toolbox、Hosted Agent、observability、Entra/RBAC/VNet、M365/Teams publishingを再確認する。preview機能は固定本文へ埋め込まない。
• GitHub CopilotはMicrosoft 365 governanceへ吸収せず独立subchapterにする。enterprise/org policy conflict、model/provider hosting、content exclusion surface差、audit gap、AI Creditsを更新表へ置く。
• Agent Store/Agent Registry/Agent 365 SDKは「Microsoft内外のagentを治理・配布へ接続する層」として再採集し、Copilot Studio専用品と誤記しない。
• TEST_PROFILE候補: 認証済みtenant実験はこのRUNでは未実施。後続Workで安全に実施可能なら、同じSharePoint権限セットでMicrosoft Copilot/SharePoint agent/Copilot Studio agentの可視content差、RCD propagation、publish→admin approval→user availability、audit log coverageを比較する。
• 接続候補: EA-005 MCP実践辞典、EA-006 agent ecosystem、EA-012公称能力vs実効能力、EA-021権限付き検索、EA-036 permission-aware retrieval、EA-054 agent identity、EA-055 multi-agent governance、EA-147 Copilot Studioへcross-reference。

/ STOP_CONDITION

• 2026-09-11時点のAgent 365/Entra Agent Registryの全license/Frontier availabilityとGA/preview境界。
• FoundryからMicrosoft Copilot/Teams/Agent Storeへpublishする全経路のregion/tenant別可用性。
• Microsoft Copilotの各app surfaceでのexact model routingと第三者model選択条件。
• Copilot Studioの全Copilot Credit消費率、agent type/tool別meter。
• GitHub Copilotの各client/agent modeに対するcontent exclusion/audit/data-residencyの完全matrix。
• 特定tenantでのRCD/index/policy propagation実測値。

EA-002の公開後章構造に必要なtopology、主要security/data/governance境界、Copilot Studio/Foundry/GitHubの別管理面、SharePoint oversharing反証まで一次資料で確立した。全SKU・全価格・全preview機能の固定はPRODUCT_VOLATILE化が早いため今回のbounded unitでは行わない。次の未調査最小番号はEA-003 Apple Intelligence／オンデバイスAI編。

• Microsoft 365 Copilot release notes, updated through 2026-10-06: https://learn.microsoft.com/en-us/microsoft-365/copilot/release-notes
• Copilot Studio licensing/access: https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-licensing
• Copilot Studio billing/Copilot Credits: https://learn.microsoft.com/en-us/microsoft-copilot-studio/billing-licensing
• Microsoft Foundry Agent Service: https://learn.microsoft.com/en-us/azure/foundry/agents/overview
• GitHub Copilot enterprise management: https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise
• GitHub Copilot content exclusion: https://docs.github.com/en/copilot/concepts/security-governance-and-network-settings/content-exclusion
• GitHub Copilot audit logging: https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot/manage-for-enterprise/review-audit-logs

• Microsoft 365 Copilot continues active staged rollout; the 2026-10-06 release notes explicitly describe gradual tenant rollout. This reinforces the packet's rule that availability is not a static tenant-wide yes/no.
• Copilot Studio still has separate maker/user and tenant licensing concepts, Teams/trial boundaries, and Copilot Credits/capacity. Trial access can permit building/testing while publication remains restricted. This reinforces maker/consumer/license separation.
• Microsoft Foundry Agent Service is a distinct managed pro-code agent platform with its own runtime, toolboxes, model catalog, identity/network/data controls and publishing/distribution paths. Current docs describe distribution to Microsoft 365 Copilot, Teams and Entra Agent Registry and separate protocol surfaces, so it must not be collapsed into the M365 end-user Copilot surface.
• GitHub Copilot remains a separate enterprise governance plane. Enterprise owners can control models/features/policies; content exclusion has repository/organization/enterprise policy surfaces; audit logs cover policy/license/website-agent events but do not include local client prompt/session data. This supports the packet's warning against assuming one unified Microsoft audit plane.
• Product naming and packaging remain PRODUCT_VOLATILE. This supplement does not freeze every SKU, exact model route, price or preview feature.

Current product documentation strengthens the multi-plane topology but also shows that features, publication paths, billing and audit coverage keep changing. Therefore the candidate must preserve an as-of boundary and must not promote a single naming map or license matrix into a durable invariant.

RESEARCH_GATE: PASS_FOR_BOUNDED_BASE_REVISION — the canonical packet already contains exact topic, claim-level evidence, scope routing, counterevidence/failure envelope, availability gates, security/privacy/audit/cost/operability, SAFE_WORDING and OPEN_UNKNOWN; the 2026-10-11 supplement refreshes the volatile Microsoft/GitHub control-plane boundaries. No tenant live test or independent audit is claimed.

CANDIDATE_IMPLEMENTATION_OVERLAY: