--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/microsoft-copilot-vs-t3-chat/" data_url: "https://onaihq.com/compare/agents/microsoft-copilot-vs-t3-chat/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # Microsoft Copilot vs T3 Chat > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 26 criteria with sourced findings for both products, including 26 that a second agent cross-checked for both. 50 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - Microsoft Copilot source checks: 2026-10-21 to 2026-10-26. - T3 Chat source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/microsoft-copilot-vs-t3-chat/ - Machine-readable JSON: https://onaihq.com/compare/agents/microsoft-copilot-vs-t3-chat/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Commercial PowerPoint editing offers Auto, ChatGPT and Claude; this is not a catalogue for every Copilot chat or agent. Availability: generally-available Delivery: native Scope: surfaces=Copilot in Microsoft 365 apps and Teams; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Commercial Microsoft Copilot subscription: PowerPoint editing mode only; add_ons=Eligible Microsoft 365/PowerPoint subscription, Commercial Microsoft Copilot subscription, Anthropic subprocessor enabled by the enterprise administrator for Claude; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Scope is commercial PowerPoint editing, with regional/subscription availability limits; no tenant picker or multimodal fixture was observed. - Cowork and Studio roadmap launches are separate experiences and are excluded from this current-model finding. - providers — Which model providers are available? [supported]: PowerPoint editing names OpenAI ChatGPT and Anthropic Claude; the enterprise administrator must enable Anthropic before Claude appears. Sources: microsoft-copilot:ms-ppt-model-r2. - current_models — Which current models are selectable on this plan? [partial]: This PowerPoint selector names ChatGPT and Claude, without versioned build IDs. GPT-6 Astra/Fable roadmap entries for Cowork/Studio do not establish PowerPoint or standalone Chat availability. Sources: microsoft-copilot:ms-ppt-model-r2. - user_choice — Can users pick the model per chat? [supported]: In PowerPoint editing mode, the user chooses Auto, ChatGPT or Claude; the choice resets to Auto after the session. Sources: microsoft-copilot:ms-ppt-model-r2. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: PowerPoint Auto chooses a model; exact routed version and routing rationale are not established by this guide. Sources: microsoft-copilot:ms-ppt-model-r2. - multimodal_input — Which models accept images, audio or files? [unknown]: Per-model image/audio/file modalities and a separate plan-specific standalone Chat picker remain unverified after reviewing PowerPoint selection and commercial model documentation. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-ppt-model-r2 #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid-account vendor replies establish manual model switching and provider routes, while the current plan-specific catalogue is unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 vendor-support context; no Free or Premier catalogue parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - providers — Which model providers are available? [partial]: Pro-context vendor replies discuss Gemini, Claude and GPT routes; the FAQ separately describes OpenAI/Anthropic/Google/OpenRouter data handling. Those policy/provider names are not a complete tier-entitlement or underlying-lab catalogue. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls. - current_models — Which current models are selectable on this plan? [unknown]: A complete current selectable-model list for Pro, Free or Premier is unverified. The FAQ claude-4.6-sonnet URL is an example, and undated support model names are not a current plan catalogue. - user_choice — Can users pick the model per chat? [partial]: In the USD8 context discussion the vendor recommends manually switching to Gemini Flash or summarizing into a new chat with another chosen model. This supports Pro model selection as described there, but not a current all-model, effort or Free/Premier entitlement matrix. Sources: t3-chat:t3-chat:r2-pro-context-byok. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? The public T3 FAQ, Terms, Privacy/Security policies, official feedback statuses and identifiable vendor replies did not establish this detail. No authenticated account, enterprise quote or bounded fixture was used. - multimodal_input — Which models accept images, audio or files? [unknown]: No current Pro model-by-model image/audio/file compatibility matrix was retrieved. The generic privacy upload categories do not establish a plan entitlement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok ### MOD-02: Model freshness Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated release information exists; a comparable three-release lag series remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: release_lag_days, deprecation_notice, version_pinning. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unverified after checking Microsoft release notes and AI at Work Roadmap; exact provider GA dates were not paired with three product release dates per provider. - changelog — Is there a dated public model changelog? [supported]: Microsoft publishes dated product release notes and roadmap launches. Sources: microsoft-copilot:ms-release, microsoft-copilot:ms-roadmap. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unverified after checking Microsoft release notes and AI at Work Roadmap; exact provider GA dates were not paired with three product release dates per provider. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unverified after checking Microsoft release notes and AI at Work Roadmap; exact provider GA dates were not paired with three product release dates per provider. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-release, microsoft-copilot:ms-roadmap #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public feature-release information is described; plan-specific pinning and version guarantees remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Public T3 Chat release information; no verified Free/Pro/Premier picker/pinning entitlement; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved. - changelog — Is there a dated public model changelog? [partial]: A vendor reply says major-feature changelog lives in Discord and a website version is planned. No accessible dated model-by-model release ledger was retrieved. Sources: t3-chat:t3-chat:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved. - version_pinning — Can an admin keep an older model version? [unknown]: The vendor describes pinning and a Legacy designation in the general picker discussion, without a named individual tier. Plan-specific pinning, retained model versions and admin locks remain unverified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:changelog ### MOD-03: Bring-your-own keys and provider contracts Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract. #### Microsoft Copilot Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Vendor replies support a Pro own-OpenRouter-key route, without establishing universal provider/model coverage. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 with optional customer OpenRouter key; no Free BYOK entitlement asserted; add_ons=Customer-paid OpenRouter/provider usage; model routing and verification prerequisites apply; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - own_api_keys — Can the customer use its own provider API keys? [supported]: In the paid USD8 usage discussion, staff explicitly offers a customer OpenRouter key for direct request billing; the USD8 context discussion describes OpenRouter fallback. No all-provider/all-model BYOK entitlement follows. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unknown]: Can it use its own Azure OpenAI, Bedrock or Vertex deployment? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved. - byo_pricing — Does BYO change the licence price? [partial]: The paid subscription and direct-provider charges are separate in the vendor discussion. A discounted BYOK-only licence and exact customer provider rates are not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls. - byo_restrictions — Which features stop working with BYO? [unknown]: Current all-model BYOK compatibility is unknown: the OpenRouter-coverage request is marked Completed while the vendor says those model routes do not run through OpenRouter and rerouting requires future work. The old OpenAI GPT5 setup reply does not establish a complete current route matrix. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok ### MOD-04: Local and self-hosted models Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work. #### Microsoft Copilot Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Provider-level access and mode selection are documented; detailed quota and group tests remain open. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - No two-group model restriction test was performed. - model_allowlist_by_group — Can admins limit models per group? [partial]: Admins select No users, All users or specific users/groups for Anthropic; this is provider-level rather than arbitrary per-model policy. Sources: microsoft-copilot:ms-anthropic. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unverified after checking Microsoft Copilot privacy, commercial pricing, connector documentation, Agent Builder, and dated release notes on 2026-10-21; no licensed test tenant. - default_model — Can admins set the default model? [unknown]: Can admins set the default model? Unverified after checking Microsoft Copilot privacy, commercial pricing, connector documentation, Agent Builder, and dated release notes on 2026-10-21; no licensed test tenant. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Chat provides standard access while paid Copilot has priority; numerical chat/token entitlements are not established here. Sources: microsoft-copilot:ms-price-us. - limit_behaviour — What happens when a limit is reached? [unknown]: What happens when a limit is reached? Unverified after checking Microsoft Copilot privacy, commercial pricing, connector documentation, Agent Builder, and dated release notes on 2026-10-21; no licensed test tenant. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-anthropic, microsoft-copilot:ms-price-us #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individuals have cost-based refill limits; enterprise group governance is unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 cost-limit discussion and Premier account bucket reply; Free excluded from this mechanics finding; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - default_model — Can admins set the default model? [unknown]: Can admins set the default model? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Pro cost-limit replies and a Premier-specific vendor support reply tie paid usage to the FAQ Base/Overage mechanics: four-hour Base refill and monthly Overage refill. No fixed token/message allowance is published;20/200 example points are illustrative, not plan capacities. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets. - limit_behaviour — What happens when a limit is reached? [supported]: For these documented paid-account bucket routes, expected request cost is reserved then settled after completion; when both balances are exhausted the FAQ says to wait for refill. No Free-tier behaviour is inferred. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets, t3-chat:t3-chat:r2-paid-tier-controls. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets ## Company knowledge ### KNOW-01: Files in chat Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Documented upload formats and limits are available; fixture fidelity remains untested. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: ocr, spreadsheets, full_vs_chunked. - formats — Which formats are accepted? [supported]: PDF, DOCX, XLSX, PPTX; PNG/JPEG/PJP/JFIF; TXT/TEXT/JSON/CSV/MD. Sources: microsoft-copilot:ms-upload. - limits — What size and count limits apply per file and chat? [supported]: Up to 20 files per conversation and 50 MB per file in the cited all-experiences support article. Sources: microsoft-copilot:ms-upload. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unverified after checking File upload in Microsoft Copilot; the long PDF, scanned contract, formula workbook and presentation fixtures were not run. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? Unverified after checking File upload in Microsoft Copilot; the long PDF, scanned contract, formula workbook and presentation fixtures were not run. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? Unverified after checking File upload in Microsoft Copilot; the long PDF, scanned contract, formula workbook and presentation fixtures were not run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-upload #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Pro context limits and own-key fallback are documented; plan-specific upload formats/caps remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 context restrictions and optional BYOK fallback; exact upload entitlement by tier unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - formats — Which formats are accepted? [unknown]: The privacy policy mentions PDF/images/text and the request is Completed, but no current individual-tier format entitlement was verified. The earlier sentence attributing browser/file-specific PDF upload bugs to a vendor reply is withdrawn because no precise reply locator was reproduced. - limits — What size and count limits apply per file and chat? [partial]: Vendor replies distinguish context restrictions on USD8 Pro from higher-tier allowances and own-key fallback. They do not publish a complete current per-model file size/count or context-cap matrix; no32K or user-suggested MB cap is adopted. Sources: t3-chat:t3-chat:r2-pro-context-byok. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. - spreadsheets — Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-pro-context-byok ### KNOW-02: Knowledge bases and shared collections Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Notebooks persist references and instructions, with plan-dependent reference limits. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Read each atomic answer for its plan, access and feature limits. - persistent_collections — Can users keep document collections across chats? [supported]: Copilot Notebooks retain selected reference collections. Sources: microsoft-copilot:ms-notebooks. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [partial]: Notebooks can be shared for collaborative editing; full user/group/organization sharing matrix was not verified. Sources: microsoft-copilot:ms-notebook-instructions. - size_limits — What are the collection limits? [supported]: Chat notebook grounding uses up to 50 references; paid grounding uses up to 300, with broader supported entities. Sources: microsoft-copilot:ms-notebooks. - assistant_binding — Can collections be bound to an assistant? [partial]: Agent Builder can bind SharePoint and connector knowledge; independent notebook-to-agent binding was not verified. Sources: microsoft-copilot:ms-builder. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-notebooks, microsoft-copilot:ms-notebook-instructions, microsoft-copilot:ms-builder #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-03: Enterprise connectors Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02). #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Copilot grounding supports synced and federated external sources; metered Copilot Chat agents have a narrower route. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot add-on (Microsoft 365 Copilot in licensing docs), or Microsoft 365 E7; commercial tenant. Synced-data metered Chat agents are a separately identified route, not paid-work-chat parity.; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - This is not a blanket connector entitlement for included Copilot Chat. The licence matrix permits Studio/pay-as-you-go synced data in agents only and excludes federation. - External-service subscriptions/permissions and connector-specific regional rollout remain prerequisites. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Paid Copilot grounds on Microsoft Graph work content. Without that add-on, shared SharePoint/synced-connector data requires an eligible metered agent; ordinary Copilot Chat is not assigned equivalent grounding. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-connector-license-r2. - google_workspace — Which Google sources are connected? [partial]: Google Drive is a synced connector for licensed Copilot grounding; the federated list includes Gmail for paid eligible users. Each source requires its own authorization. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2. - atlassian — Confluence and Jira? [partial]: Confluence/Jira synced data can ground paid Copilot; their personal self-serve variants are limited preview. Metered agents can use synced data only, not the federated route. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-personal-sync-r2, microsoft-copilot:ms-connector-license-r2. - other_systems — Which other business systems? [partial]: Synced examples include Box, Salesforce, ServiceNow, Dynamics365, Workday, Zendesk and SAP; this is the paid-grounding route, with source credentials and individual setup requirements. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2. - on_prem_sources — Can on-prem file shares or databases be connected? [supported]: File-share/SQL/Oracle sources can be indexed by a synced connector/connector agent for paid grounding or separately metered synced-data agents; this does not run Copilot on premises. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2. - connector_provider — Who builds and maintains each connector? [supported]: Microsoft/partner/custom synced connectors coexist. Federation can use Microsoft-published or approved partners, and custom MCP has its own admin setup. All federated querying requires the paid add-on/E7. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-custom-mcp-r2, microsoft-copilot:ms-connector-license-r2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-connector-license-r2, microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-personal-sync-r2, microsoft-copilot:ms-custom-mcp-r2 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft documents source-permission controls; the required restricted-document test was not run. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot add-on (Microsoft 365 Copilot in licensing docs), or Microsoft 365 E7; commercial tenant. Synced-data metered Chat agents are a separately identified route, not paid-work-chat parity.; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - All positive permission findings use the paid work-grounding route, not included Copilot Chat. Purview/SAM require their applicable entitlements. - No two-user restricted-document or revocation test; connector disable propagation is not proof of source-ACL revocation timing. - source_permissions_respected — Are source permissions enforced per user? [supported]: In licensed Copilot work grounding, Graph data is limited to the requesting user's access; this was not tested. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-connector-license-r2. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Paid synced grounding filters item ACLs in Graph; paid federated access executes with the authenticated source-user identity. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unverified after checking Copilot privacy, connector architecture and Purview DLP; no two-user or permission-revocation fixture. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Licensed Copilot deployment guidance documents restricted SharePoint search/SAM; federated access also intersects tenant User access and connector staging. Sources: microsoft-copilot:ms-setup, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [supported]: Purview can exclude labelled content from processing through configured DLP rules. Sources: microsoft-copilot:ms-dlp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-connector-license-r2, microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-setup, microsoft-copilot:ms-dlp #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-05: Freshness and sync model Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Both copied Graph indexes and live MCP federation are documented. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot add-on (Microsoft 365 Copilot in licensing docs), or Microsoft 365 E7; commercial tenant. Synced-data metered Chat agents are a separately identified route, not paid-work-chat parity.; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Copilot Chat without the add-on is not included as a general indexed/federated grounding entitlement. - No edit/delete propagation fixture; self-serve Confluence/Jira remains limited preview. - live_or_indexed — Is content searched live or copied into an index? [supported]: Licensed Copilot can ground on synced Graph copies or query federated sources live without a separate external-content index. The licence matrix allows metered Chat agents to use synced data only. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2. - sync_interval — How often does an index refresh? [partial]: For the limited-preview personal Confluence/Jira synced route, docs describe roughly15-minute incremental and seven-day full crawls; this is not a general federated or connector SLA. Sources: microsoft-copilot:ms-personal-sync-r2, microsoft-copilot:ms-connector-license-r2. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unverified after checking connector overview and personal-sync documentation; no edit/delete propagation fixture. - index_location — Where is indexed content stored? [partial]: Paid synced grounding uses the Microsoft365 tenant Graph cloud index; federation does not copy that external content into an index. A country-level index map remains unverified. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2, microsoft-copilot:ms-personal-sync-r2 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-06: Grounding and retrieval quality Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Source links are documented; retrieval quality and cross-language accuracy remain unmeasured. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot/E7 connector-grounded responses only; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Documented citations apply to the licensed connector-grounding route; no equivalent included-Chat entitlement or measured citation accuracy is claimed. - No DE/FR/EN grounding, cross-language, unanswerable-question or restricted-document fixture was run. - citations — Are answers linked to specific sources? [supported]: For licensed Copilot connector-grounded responses, Microsoft documents source citations and links to referenced external items. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unverified after checking connector response documentation; no shared DE/FR/EN corpus or answer set was executed. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unverified after checking connector response documentation; no shared DE/FR/EN corpus or answer set was executed. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unverified after checking connector response documentation; no shared DE/FR/EN corpus or answer set was executed. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unverified after checking connector response documentation; no shared DE/FR/EN corpus or answer set was executed. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### KNOW-07: Memory and personal context Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Saved memory, history-based personalization and instructions have user controls. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: admin_memory_controls. - Read each atomic answer for its plan, access and feature limits. - custom_instructions — Can users set persistent instructions? [supported]: Users set personal instructions; notebooks have their own instructions. Sources: microsoft-copilot:ms-memory, microsoft-copilot:ms-notebook-instructions. - cross_chat_memory — Does the product remember facts across chats? [supported]: Enabled memory stores preferences and can use prior-chat inferences; work insights depend on plan. Sources: microsoft-copilot:ms-memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users can inspect what Copilot knows, ask it to forget details and use temporary chat. Complete saved-memory editing behavior was not tested. Sources: microsoft-copilot:ms-memory. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? Unverified after checking personalization documentation and Copilot management; organization-wide memory policy behavior not independently established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-memory, microsoft-copilot:ms-notebook-instructions #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent Builder and the agent catalogue cover shared assistants; external actions need a different authoring route. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Microsoft Copilot Chat web app, Copilot Studio extension and agent builder, separate licensing where stated; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Read each atomic answer for its plan, access and feature limits. - create_assistants — Can users create assistants with instructions, knowledge and tools? [partial]: Agent Builder combines instructions and selected knowledge; external action authoring requires Copilot Studio. Sources: microsoft-copilot:ms-builder. - creator_permissions — Can admins limit who creates them? [supported]: Admins control whether users can access Agent Builder. Sources: microsoft-copilot:ms-builder. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Agent links can be shared; the complete user/group/organization permission matrix was not checked. Sources: microsoft-copilot:ms-agents. - catalogue — Is there an internal assistant directory? [supported]: The app lists prebuilt, shared and organization agents. Sources: microsoft-copilot:ms-agents. - prompt_library — Are shared prompt templates available? [supported]: The commercial page links Copilot Prompt Gallery. Sources: microsoft-copilot:ms-price-us. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-builder, microsoft-copilot:ms-agents, microsoft-copilot:ms-price-us #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-02: Tools, actions and MCP Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Copilot documents authenticated MCP tools and conditional writes; the October16 detailed guide supersedes the older generic read-only rollout description. Availability: unknown Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot Studio extension and agent builder, separate licensing where stated; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot/E7 federated connectors and paid Copilot Agent Builder; Studio is only the separately licensed extension route; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Reconciliation: October6 overview retains read-only/early-October text; October16 detailed federation/setup pages explicitly document writes. The current finding is conditional protocol behavior, with actual tenant write availability unknown. - Researcher has an explicit read-only boundary. No external call, approval or access-boundary fixture was executed. - builtin_tools — Which tools are built in? [supported]: Paid experiences include Researcher, Analyst and Facilitator. Sources: microsoft-copilot:ms-price-us. - custom_actions — Can admins add API actions? [partial]: Agent Builder directs authored external-action scenarios to Copilot Studio. Separately, paid federated MCP connectors can expose create/update/delete tools where supplied by the publisher. Sources: microsoft-copilot:ms-builder, microsoft-copilot:ms-custom-mcp-r2, microsoft-copilot:ms-federated-r2. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Custom federation accepts a remote MCP server with search/fetch/query and optional create/update/delete tools. Federation requires the querying user's paid add-on/E7; Studio/pay-as-you-go alone is insufficient. Sources: microsoft-copilot:ms-custom-mcp-r2, microsoft-copilot:ms-connector-license-r2. - tool_auth — Do tools act as the user or as a shared account? [supported]: Federated authenticated tools use OAuth/source-user identity and source permissions. Tenant User access, publisher controls and staged rollout also apply. Sources: microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-custom-mcp-r2. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Where a connector supplies writes, October16 docs require initial explicit approval with per-tool Allow once/conversation/Always allow settings. Researcher remains read-only. The Coming soon label concerns the admin Tools list. Sources: microsoft-copilot:ms-federated-r2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-builder, microsoft-copilot:ms-custom-mcp-r2, microsoft-copilot:ms-federated-r2, microsoft-copilot:ms-connector-license-r2 #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Pro search is discussed by the vendor; image-tier entitlement, custom actions and MCP remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 for evidenced search use; image and MCP plan entitlement unknown; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - builtin_tools — Which tools are built in? [partial]: The Pro/Premier pricing discussion explicitly describes frequent search and search-token overhead in the USD8 paid context. An OpenAI image integration has separate support evidence, but its plan entitlement is not verified and is not included as a Pro tool promise. Sources: t3-chat:t3-chat:r2-paid-tier-controls. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - mcp_client — Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - tool_auth — Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls ### AGT-03: Web search and deep research Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: supported Web search is policy-controlled and uses Bing outside the Microsoft 365 search-query boundary. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. - web_search — Is web search available? [supported]: Chat can ground answers in web search. Sources: microsoft-copilot:ms-chat-privacy. - admin_toggle — Can admins disable it per organisation or group? [supported]: Allow web search can target the tenant, groups or users. Sources: microsoft-copilot:ms-manage. - search_provider — Which search provider handles queries, and where? [supported]: Bing receives generated queries under separate data-handling terms; those queries are outside EUDB. Sources: microsoft-copilot:ms-chat-privacy. - deep_research — Is multi-step research with a report available? [supported]: Researcher is included in paid Copilot; a report fixture was not run. Sources: microsoft-copilot:ms-price-us. - web_citations — Are web sources cited? [supported]: Responses include web citations and show generated query details for 24 hours. Sources: microsoft-copilot:ms-chat-privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-chat-privacy, microsoft-copilot:ms-manage, microsoft-copilot:ms-price-us #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Search is user-selectable, with a documented one-to-five search limit; a separate deep-research product is unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 paid-search discussion; no Free parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - web_search — Is web search available? [partial]: Staff’s paid USD8 discussion confirms search consumes API/query and context costs. The FAQ exposes search on/off and1..5 URL limits, but a complete current tier-specific limit/feature matrix was not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url. - admin_toggle — Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - deep_research — Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. - web_citations — Are web sources cited? [unknown]: Are web sources cited? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url ### AGT-04: Workflows and automation Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Paid Copilot schedules prompts; advanced workflow authoring has separate Studio dependencies. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot Studio extension and agent builder, separate licensing where stated; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: event_triggers. - Read each atomic answer for its plan, access and feature limits. - workflow_builder — Is there a workflow or chain builder? [partial]: Agent Builder directs low-code actions and workflows to Copilot Studio. Sources: microsoft-copilot:ms-builder. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Paid users can create up to ten scheduled prompts and manage their recurrence. Sources: microsoft-copilot:ms-schedule. - event_triggers — Can external events start a workflow? [unknown]: Can external events start a workflow? Unverified after checking scheduled prompt and Agent Builder documentation; external-event trigger availability was not scoped. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Agent Builder uses natural-language configuration; Studio is the low-code extension route. Sources: microsoft-copilot:ms-builder. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-builder, microsoft-copilot:ms-schedule #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-05: Agentic task execution Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cowork documents multi-step tool execution with visible progress and user controls. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot with Cowork enabled; add_ons=Qualifying Microsoft 365 licence, Enabled usage-based Cowork billing; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Documented behavior only; no three-document/email fixture or interventions were observed. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Cowork handles multi-step work with enabled usage billing and a paid licence. Sources: microsoft-copilot:ms-cowork. - visible_steps — Are steps and tool calls shown? [supported]: The interface exposes skill messages and tool steps. Sources: microsoft-copilot:ms-cowork. - side_effect_confirmation — Must the user confirm actions with side effects? [supported]: Side effects require approval; users can allow similar actions for the current session. Sources: microsoft-copilot:ms-cowork. - stop_control — Can the user stop a running task? [supported]: Users can pause immediately or after the current step, resume or cancel. Sources: microsoft-copilot:ms-cowork. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-cowork #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### AGT-06: Programmable access Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial The Chat API and the Work IQ API public preview are separate programmable routes. Availability: beta Delivery: native Scope: surfaces=Microsoft Copilot Chat API preview, Work IQ API public preview, MCP/A2A/REST; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Chat API preview requires the paid Copilot add-on per calling user; Work IQ MCP public-preview prerequisites unverified; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - API preview terms apply. This is a distinct API surface, not included Copilot Chat or an assertion of interactive/API feature parity. No API call was executed. - Work IQ MCP is a roadmap-described public preview; no endpoint or API was invoked. - chat_api — Is there an API for chat and assistants? [partial]: The preview text API is included for paid-add-on users; unlicensed users are explicitly excluded. It supports work/web grounding but not code interpreter, graphic art, action skills or long-running tasks. Sources: microsoft-copilot:ms-chat-api-r2. - knowledge_api — Can documents be loaded through an API? [partial]: Separately configured synced content can be ingested through Graph connector APIs for licensed grounding; this does not establish a complete workspace knowledge-management API. Sources: microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: The Chat API retains source-permission/compliance boundaries; full budget/audit parity was not independently tested. Sources: microsoft-copilot:ms-chat-api-r2. - mcp_server — Does the product expose itself to other agents over MCP? [partial]: Microsoft advertises Work IQ API public preview with MCP, A2A and REST access to work context. Endpoint, authentication and plan details were not verified; this does not make the separate Copilot Chat API an MCP server. Sources: microsoft-copilot:microsoft-copilot:r4-roadmap-work-iq. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-chat-api-r2, microsoft-copilot:ms-connectors-r2, microsoft-copilot:ms-connector-license-r2, microsoft-copilot:microsoft-copilot:r4-roadmap-work-iq #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial No official programmable enterprise interface was established; subscription-backed external-agent API usage was rejected. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_api — Is there an API for chat and assistants? [partial]: An official feedback request asks to apply subscription quota to external coding agents/API; staff closes it because the economics do not work. The FAQ URL launches a browser chat and is not a documented chat API. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url. - knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. - api_governance — Do audit, budgets and model rules apply to API use? [unknown]: Do audit, budgets and model rules apply to API use? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url ## Daily work ### WORK-01: Clients and access points Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web and native access are documented, with authoring gaps on mobile. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Windows MDM deployment is documented; full mobile deployment/configuration parity was not tested. - web — Is a full web client available? [supported]: The browser client is available for paid Copilot and Copilot Chat. Sources: microsoft-copilot:ms-price-us. - desktop_apps — Windows and macOS apps? [supported]: Cowork documentation lists Windows and macOS Copilot clients. Sources: microsoft-copilot:ms-cowork. - mobile_apps — iOS and Android apps with SSO? [partial]: Cowork lists iPhone and Android apps under the licensed account; mobile SSO was not trialled. Sources: microsoft-copilot:ms-cowork. - browser_extension — Is there a browser extension or sidebar? [partial]: Copilot is available in the Edge sidebar; this does not establish a separate third-party browser extension. Sources: microsoft-copilot:ms-chat-usage. - managed_deployment — Can IT deploy and configure clients through MDM? [supported]: For Windows, IT can distribute the Copilot executable through Intune, Configuration Manager, Group Policy or another MDM and control automatic installation. EEA, government and channel exclusions apply to automatic installation; full mobile policy parity was not tested. Sources: microsoft-copilot:microsoft-copilot:r4-mdm-deployment. - client_feature_gaps — Which features are missing on mobile? [partial]: Agent Builder is unavailable on mobile; other feature differences vary by release. Sources: microsoft-copilot:ms-builder. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-cowork, microsoft-copilot:ms-chat-usage, microsoft-copilot:ms-builder, microsoft-copilot:microsoft-copilot:r4-mdm-deployment #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial A browser client and iOS TestFlight beta are documented; desktop, Android release and managed clients remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application, T3 Chat iOS TestFlight beta; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Browser account plan; iOS TestFlight beta; enterprise SSO unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=iOS. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: T3 Chat is delivered as a browser service; the FAQ documents launching new conversations through public URLs. Sources: t3-chat:t3-chat:faq-url. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - mobile_apps — iOS and Android apps with SSO? [partial]: The vendor’s September10,2026 announcement releases iOS via TestFlight explicitly as beta; Android beta is coming soon. Neither corporate SSO nor a production app-store release was verified. Sources: t3-chat:t3-chat:mobile. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-url, t3-chat:t3-chat:mobile ### WORK-02: Office suite and Teams integration Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial The paid offering works inside Microsoft 365 apps; Chat has narrower contextual access. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: google_workspace_apps. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [supported]: Paid Copilot is integrated in Word, Excel and PowerPoint; Chat open-content interactions are narrower. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-chat-privacy. - outlook — Does it work inside Outlook? [supported]: Chat in Outlook can use the user mailbox/calendar and a limited set of accessible files. Sources: microsoft-copilot:ms-chat-privacy. - teams — Is there a Teams app or bot? [supported]: Paid Copilot includes Teams; the Chat entry point also appears in Teams. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-chat-usage. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unverified after checking pricing, Chat organizational-data and deployment documentation; native Google Workspace editing integrations not established. - licence_prerequisites — Which licences or consents are needed? [supported]: Paid Copilot requires an eligible M365 base licence; compliance capabilities may need further entitlements. Sources: microsoft-copilot:ms-setup. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-chat-privacy, microsoft-copilot:ms-chat-usage, microsoft-copilot:ms-setup #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Copilot Chat can translate referenced document text and accept tone/audience instructions. Format-preserving Word Translator and SharePoint glossary translation are separately scoped workflows. Availability: generally-available Delivery: native Scope: surfaces=Copilot in Microsoft 365 apps and Teams, Microsoft Copilot paid work chat; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Commercial Microsoft Copilot add-on for Word writing examples; general work-chat prompts where the support guide explicitly applies; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Copilot’s prompted translation does not establish preserved page/table layout or a managed corporate glossary. - Word Translator is a separate base-app command; SharePoint/OneDrive glossary translation is separately metered document processing requiring Azure billing and permissions. - No shared translation/glossary/Swiss-language fixture or complete dedicated-engine specification was verified. - document_translation — Can whole documents be translated with formatting kept? [partial]: Copilot Chat documents translation of attached or referenced file content. Microsoft separately documents Word Translator creating a formatted translated copy; that is a Word command, not a Copilot Chat formatting guarantee. No DE-to-FR/IT layout fixture was run. Sources: microsoft-copilot:microsoft-copilot:r5-chat-translation, microsoft-copilot:microsoft-copilot:r5-word-translation-boundary. - translation_engine — Which engine translates? [unknown]: Unresolved on 2026-10-26. Re-read https://support.microsoft.com/en-us/microsoft-365-copilot/translate-files-into-another-language-in-microsoft-365-copilot-chat and https://word.cloud.microsoft/create/en/blog/how-to-translate-documents-in-word/ . The latter identifies Word Translator as a separate formatting-preserving command and Copilot as a drafting/rewriting route, but does not specify a dedicated Copilot translation engine/model contract. No engine was inferred from the separate Word/SharePoint services. - glossaries — Are company glossaries supported? [unknown]: Unresolved on 2026-10-26. Re-read the Copilot translation support page and https://learn.microsoft.com/en-us/microsoft-365/documentprocessing/translation-glossary?view=o365-worldwide plus https://learn.microsoft.com/en-us/microsoft-365/documentprocessing/syntex-azure-billing?view=o365-worldwide . SharePoint supports glossary files in separately metered document processing; a maintained glossary enforced by Copilot Chat/Word prompts or included with a Copilot seat was not established. No glossary fixture was run. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Official Copilot examples accept tone/style/country and region-specific wording instructions, including refining translated Word content. A deterministic de-CH preset, terminology enforcement and dialect-quality result were not established. Sources: microsoft-copilot:microsoft-copilot:r5-chat-translation, microsoft-copilot:microsoft-copilot:r5-word-translation-boundary. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: The direct support guide documents drafting from prompts and Word paragraph rewriting; work-data-grounded prompts require the commercial Copilot subscription. Sources: microsoft-copilot:ms-writing-r2. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-writing-r2, microsoft-copilot:microsoft-copilot:r5-chat-translation, microsoft-copilot:microsoft-copilot:r5-word-translation-boundary, microsoft-copilot:microsoft-copilot:r5-sharepoint-translation, microsoft-copilot:microsoft-copilot:r5-sharepoint-glossary, microsoft-copilot:microsoft-copilot:r5-sharepoint-metering #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and an administrator restriction are documented. General output ownership terms apply; editing and image-model-specific rights remain incomplete. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Image editing remains unverified. - Administrator image-generation controls are documented; full image-model-specific output rights remain unverified. - image_generation — Can users generate images, with which models? [partial]: Create/image generation appears in Chat and paid offerings; the current image-model mapping was not established. Sources: microsoft-copilot:ms-price-us. - image_editing — Can users edit uploaded images? [unknown]: Can users edit uploaded images? Unverified after checking Copilot commercial comparison and release notes; current editing, model-specific cost, image policy and output licence terms not fully retrieved. - admin_control — Can admins restrict image generation? [supported]: An authorized administrator can allow or prevent supported image generation under Copilot Settings. Availability depends on the tenant licence, enabled features and rollout; group-level behavior was not tested. Sources: microsoft-copilot:microsoft-copilot:r4-image-admin. - usage_terms — What usage rights apply to output? [partial]: The commercial Generative AI Product Terms treat output as Customer Data and state Microsoft does not own it. A complete image-model-specific rights or third-party restriction matrix was not verified. Sources: microsoft-copilot:microsoft-copilot:r4-online-service-terms. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:microsoft-copilot:r4-image-admin, microsoft-copilot:microsoft-copilot:r4-online-service-terms #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-05: Voice and meetings Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Work-account dictation, read-aloud and live voice are documented with availability limits. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: meeting_summaries, swiss_german_speech. - Read each atomic answer for its plan, access and feature limits. - dictation — Can users dictate prompts? [supported]: Work/school dictation sends speech to Microsoft for transcription without retaining dictation audio. Sources: microsoft-copilot:ms-voice. - read_aloud — Can answers be read aloud? [supported]: Read-aloud uses client-side text-to-speech. Sources: microsoft-copilot:ms-voice. - voice_conversation — Is a live voice mode available? [partial]: Live voice is documented for work/school accounts, subject to subscription and region; feedback audio is removed after 48 hours. Sources: microsoft-copilot:ms-voice. - meeting_summaries — Are meetings transcribed and summarised? [unknown]: Are meetings transcribed and summarised? Unverified after checking Copilot Voice and work-language pages; meeting transcription prerequisites and Swiss German dialect recognition not tested or established. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unverified after checking Copilot Voice and work-language pages; meeting transcription prerequisites and Swiss German dialect recognition not tested or established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-voice #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-06: Data analysis and document output Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Python execution and downloadable Office files are documented. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Microsoft Copilot with code interpreter/eligible Agent Builder agents; generated Word/Excel/PowerPoint files as documented for Chat; add_ons=Eligible Microsoft 365 base subscription, Paid Microsoft Copilot add-on; called Microsoft 365 Copilot in some source pages, Source-service credentials/subscriptions and Purview entitlements where required; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - No analysis entitlement is inferred for every included-Chat client. Scope uses the paid Copilot code path explicitly named by the security architecture. - No spreadsheet/formula or editable-PowerPoint fixture was run. Notebook instruction sharing is not counted as an output canvas. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: In the paid Copilot/eligible agent code-interpreter path, LLM-generated Python runs in isolated Azure VMs with no network traffic. Sources: microsoft-copilot:ms-code-r2. - charts — Can it produce charts? [supported]: The same paid code-interpreter path can generate data visualizations. Sources: microsoft-copilot:ms-code-r2. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Chat's Word/Excel/PowerPoint agents generate files: Word/Excel download; PowerPoint uses OneDrive when available, otherwise download. Sources: microsoft-copilot:ms-chat-privacy-r2. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: Notebook instruction editing does not establish an editor for generated output. Output-canvas behavior remains unverified after checking code-interpreter, file-generation and notebook instruction documentation. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-code-r2, microsoft-copilot:ms-chat-privacy-r2 #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-07: Sharing and team spaces Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared notebooks and agents are documented; chat-sharing boundaries remain untested. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: share_chats, group_chat, share_permission_boundary. - share_chats — Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? Unverified after checking notebook sharing and Agent Builder limitations; no cross-group chat-sharing or group-chat test. - team_spaces — Are shared projects or workspaces available? [supported]: Users can collaborate on shared notebooks and share agents. Sources: microsoft-copilot:ms-notebook-instructions, microsoft-copilot:ms-agents. - group_chat — Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unverified after checking notebook sharing and Agent Builder limitations; no cross-group chat-sharing or group-chat test. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unverified after checking notebook sharing and Agent Builder limitations; no cross-group chat-sharing or group-chat test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-notebook-instructions, microsoft-copilot:ms-agents #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-08: Interface languages and accessibility Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft lists the target European languages; naturalness and conformance remain unchecked. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Localization availability is documented; linguistic quality was not observed. - ui_languages — Which UI languages are offered? [supported]: Microsoft lists English, German, French and Italian among supported work languages and states localization. Sources: microsoft-copilot:ms-language. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unverified after checking supported-language page; no localized UI inspection, admin-language pass or product-specific WCAG report. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unverified after checking supported-language page; no localized UI inspection, admin-language pass or product-specific WCAG report. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unverified after checking supported-language page; no localized UI inspection, admin-language pass or product-specific WCAG report. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-language #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Administration and governance ### ADM-01: Single sign-on and authentication Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft 365 identity, MFA and conditional-access setup are documented. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: domain_capture. - Read each atomic answer for its plan, access and feature limits. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Copilot uses Microsoft 365/Entra work accounts; exact application protocol and direct LDAP alternatives were not verified. Sources: microsoft-copilot:ms-price-us. - sso_plan — Which plan includes SSO? [supported]: Chat requires an eligible M365 account; paid access adds a Copilot licence. Sources: microsoft-copilot:ms-price-us. - mfa — Can MFA be enforced? [supported]: Deployment guidance documents enforcing MFA through Entra policies. Sources: microsoft-copilot:ms-setup. - conditional_access — Do Entra conditional-access policies apply? [partial]: Setup guidance documents conditional access, including SharePoint tenant-level policies. Sources: microsoft-copilot:ms-setup. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unverified after checking Copilot licence and deployment guidance; no trial SSO login or domain-claim test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-setup #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The security policy asserts MFA support without documenting enterprise SAML/OIDC administration. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - sso_protocols — Which SSO protocols and identity providers work? [partial]: Security policy refers to OAuth provider accounts and standard authentication without naming enterprise SAML/OIDC protocols or supported corporate IdPs. Sources: t3-chat:t3-chat:security. - sso_plan — Which plan includes SSO? [unknown]: Which plan includes SSO? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. - mfa — Can MFA be enforced? [partial]: The vendor asserts MFA support and recommends two-factor protection at the OAuth provider. Enforceable organization-wide MFA settings were not established. Sources: t3-chat:t3-chat:security. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:security ### ADM-02: User provisioning and lifecycle Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Seat assignment is tenant-managed; provisioning and content-transfer details remain open. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: scim, group_sync, jit_provisioning, deprovisioning. - scim — Is SCIM provisioning supported? [unknown]: Is SCIM provisioning supported? Unverified after checking Microsoft Copilot setup; SCIM/JIT, group provisioning and leaver asset transfer were not separately documented or tested. - group_sync — Are identity-provider groups synced? [unknown]: Are identity-provider groups synced? Unverified after checking Microsoft Copilot setup; SCIM/JIT, group provisioning and leaver asset transfer were not separately documented or tested. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Unverified after checking Microsoft Copilot setup; SCIM/JIT, group provisioning and leaver asset transfer were not separately documented or tested. - deprovisioning — What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unverified after checking Microsoft Copilot setup; SCIM/JIT, group provisioning and leaver asset transfer were not separately documented or tested. - seat_assignment — Can admins assign and reclaim seats? [supported]: M365 administrators assign purchased Copilot licences to users. Sources: microsoft-copilot:ms-setup. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-setup #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Administrative roles and selected group-targeted controls are documented. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - No disabled-feature test with two groups was performed. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: M365, SharePoint, Purview and billing functions use distinct administrator roles. Sources: microsoft-copilot:ms-setup, microsoft-copilot:ms-cost-setup. - groups — Can permissions be set per group? [supported]: Web-search and Anthropic settings can target groups. Sources: microsoft-copilot:ms-manage, microsoft-copilot:ms-anthropic. - feature_toggles — Which features can be switched on or off per group? [partial]: Admins control web search and Agent Builder; Anthropic access has separate user/group controls. Sources: microsoft-copilot:ms-manage, microsoft-copilot:ms-builder, microsoft-copilot:ms-anthropic. - multi_entity — Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? Unverified after checking Copilot admin controls; complete feature-by-group and subsidiary isolation behavior not tested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-setup, microsoft-copilot:ms-cost-setup, microsoft-copilot:ms-manage, microsoft-copilot:ms-anthropic, microsoft-copilot:ms-builder #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat and paid usage reports are separate and have privacy controls. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Read each atomic answer for its plan, access and feature limits. - adoption_dashboard — Is there an adoption dashboard? [supported]: Microsoft publishes distinct paid Copilot and unlicensed Chat usage dashboards. Sources: microsoft-copilot:ms-usage, microsoft-copilot:ms-chat-usage. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Reports include application entry points and user activity; complete model/group/assistant breakdowns were not verified. Sources: microsoft-copilot:ms-usage, microsoft-copilot:ms-chat-usage. - export — Can usage data be exported? [supported]: The Chat report exports all reported user usage as CSV. Sources: microsoft-copilot:ms-chat-usage. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Identifying user, group and site fields are hidden by default; administrators can change report settings. Sources: microsoft-copilot:ms-usage. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-usage, microsoft-copilot:ms-chat-usage #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Metered-service cost management supports limits; exact stop semantics need verification. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Prepaid-credit exhaustion alone can continue into PAYG; it is not itself a hard budget. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: The cost dashboard shows credit consumption and billing configuration; complete cost-centre mapping was not verified. Sources: microsoft-copilot:ms-cost-setup. - budgets — Can budgets be set per user or group? [supported]: Policies support monthly spending limits and optional per-user limits. Sources: microsoft-copilot:ms-cost-setup. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: The setup describes limits on monthly credit spend, but overshoot, timing and enforcement were not tested. Sources: microsoft-copilot:ms-cost-setup. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? Unverified after checking Copilot Credits cost management and rate documentation; chargeback exports and enforced-stop timing not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-cost-setup #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual consumption indicators exist; organization budgets and chargeback remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 and Premier account consumption mechanics; no organization/admin budget offer asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: The paid Pro discussion and Premier support reply describe per-account cost/bucket consumption. The FAQ describes separate balance displays; exact placement and model-cost indicators are not a customer organization reporting entitlement. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets. - budgets — Can budgets be set per user or group? [unknown]: Can budgets be set per user or group? No customer organization/user-group budget assignment or cost-centre export was retrieved. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: For the documented paid-account bucket routes, exhausting both balances requires waiting for refill. This does not establish configurable user/group currency budgets, alerts or downgrade policies. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No customer organization/user-group budget assignment or cost-centre export was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Purview provides interaction records and compliance retention, with licence-dependent policies. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Compliance copies differ from the visible chat history. No export or hold test was run. - admin_events — Are admin and security events logged? [supported]: With auditing enabled, Purview logs Copilot admin changes and user resource/agent metadata. Sources: microsoft-copilot:ms-audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Prompts/responses are retained in Exchange-backed compliance copies; administrators can apply retention. Sources: microsoft-copilot:ms-retention. - siem_export — Can logs stream to a SIEM or be exported? [supported]: Purview supports export of Copilot audit events. Microsoft documents EXO CSV export and Office 365 Management Activity API streaming of CopilotInteraction events to a SIEM; this does not imply full prompt/response content in audit metadata. Sources: microsoft-copilot:microsoft-copilot:r4-audit-export, microsoft-copilot:microsoft-copilot:r4-audit-api. - ediscovery — Are eDiscovery and legal hold supported? [supported]: Hidden interaction copies are searchable through eDiscovery and remain subject to holds. Sources: microsoft-copilot:ms-retention. - log_retention — How long are logs kept? [partial]: Audit Standard and Premium have distinct retention entitlements; a product-specific integrity and exact retention configuration was not verified. Sources: microsoft-copilot:ms-audit-standard. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-audit, microsoft-copilot:ms-retention, microsoft-copilot:ms-audit-standard, microsoft-copilot:microsoft-copilot:r4-audit-export, microsoft-copilot:microsoft-copilot:r4-audit-api #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The privacy policy describes vendor telemetry, not a customer compliance logging service. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [unknown]: Are admin and security events logged? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: The privacy policy collects prompts/uploads and Terms reserve review/removal for violations. A configurable customer prompt/answer compliance archive was not established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. - log_retention — How long are logs kept? [unknown]: How long are logs kept? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ### ADM-07: Data loss prevention and personal data Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Purview can block sensitive prompts when configured; its default policy simulates. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - No Swiss AHV or IBAN test was performed. - pii_detection — Is personal data detected in prompts and files? [supported]: Purview DLP can match selected sensitive information types in prompts. Sources: microsoft-copilot:ms-dlp. - pii_action — Is it redacted, masked, blocked or only warned? [supported]: Configured policies prevent prompt processing; the default policy is simulation/alert mode. Sources: microsoft-copilot:ms-dlp, microsoft-copilot:ms-dlp-default. - custom_patterns — Can admins add custom patterns or terms? [supported]: The Copilot DLP location supports custom sensitive-information types for prompt blocking. This control is in preview and subject to tenant rollout and licensing; the location does not scan files uploaded directly in prompts. No AHV/IBAN fixture was run. Sources: microsoft-copilot:microsoft-copilot:r4-custom-dlp-types. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Microsoft Purview is the documented integration; base subscription entitlements determine available controls. Sources: microsoft-copilot:ms-dlp, microsoft-copilot:ms-setup. - filter_location — Where does filtering run? [unknown]: Where does filtering run? Unverified after checking Purview DLP documentation; custom AHV/IBAN patterns, filtering geography and fixture behavior unverified. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:ms-dlp, microsoft-copilot:ms-dlp-default, microsoft-copilot:ms-setup, microsoft-copilot:microsoft-copilot:r4-custom-dlp-types #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft documents safety controls and policy metadata; organization-wide instruction enforcement remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: org_instructions, usage_notice. - Read each atomic answer for its plan, access and feature limits. - org_instructions — Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? Unverified after checking Copilot privacy and audit schemas; organization-wide instructions and mandatory AUP acknowledgement not established. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unverified after checking Copilot privacy and audit schemas; organization-wide instructions and mandatory AUP acknowledgement not established. - content_filters — Are content filters configurable? [partial]: Copilot documents harmful-content and prompt-injection protections; customer configurability was not established. Sources: microsoft-copilot:ms-privacy. - violation_reporting — Are policy hits visible to admins? [partial]: Audit resource metadata can include policy restrictions and prompt-injection detection; complete violation coverage was not established. Sources: microsoft-copilot:ms-audit. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-audit #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Acceptable-use terms apply, while organization policy controls remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. - content_filters — Are content filters configurable? [partial]: Terms prohibit categories of unlawful/harmful content and permit vendor review/removal or suspension. Customer configurable content filters are not established. Sources: t3-chat:t3-chat:terms. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ## Data protection and sovereignty ### DATA-01: Hosting location and data residency Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial EU/EFTA commitments have separate model, web-search and operational exceptions. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Bing web queries are outside EUDB. Anthropic opt-in changes the model-processing scope. No sovereign-cloud claims are made. - storage_region — Where are chats, files and indexes stored? [partial]: Microsoft 365 tenant commitments govern interaction storage and OneDrive files; EUDB covers qualifying EU/EFTA configurations, not a universal Swiss-only deployment. Sources: microsoft-copilot:ms-chat-privacy, microsoft-copilot:ms-eudb. - inference_region — Where do model calls run, per provider? [partial]: EU traffic has EUDB safeguards; optional Anthropic is excluded from EUDB and in-country processing commitments. Sources: microsoft-copilot:ms-privacy, microsoft-copilot:ms-anthropic. - backups_logs_region — Where are backups, logs and telemetry? [partial]: EUDB includes pseudonymized personal system logs subject to limited-transfer exceptions; a separate backup/telemetry country map was not retrieved. Sources: microsoft-copilot:ms-eudb. - support_access_region — From where can vendor staff access data? [partial]: EUDB professional-services data is committed at rest; operational transfers remain possible. This does not prove EU-only staff access. Sources: microsoft-copilot:ms-eudb. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unverified after checking Copilot privacy, EUDB and residency documentation; no comprehensive Swiss storage/inference/support matrix. - residency_plan — Which plan or option provides residency? [partial]: Chat and paid Copilot use M365 commitments; model and service-specific exceptions must be applied separately. Sources: microsoft-copilot:ms-edp, microsoft-copilot:ms-anthropic. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-chat-privacy, microsoft-copilot:ms-eudb, microsoft-copilot:ms-privacy, microsoft-copilot:ms-anthropic, microsoft-copilot:ms-edp #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The privacy policy places the service under US/international processing; no EU/Swiss end-to-end option was established. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: The policy says services are provided in the United States and information is processed there or in other countries; Azure, AWS and Vercel are named. Component-specific chat/file/index storage regions are not enumerated. Sources: t3-chat:t3-chat:privacy. - inference_region — Where do model calls run, per provider? [partial]: The policy names OpenAI, Google, Anthropic and OpenRouter processing, but no provider-by-provider region, EU-only switch or customer region guarantee is supplied. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - support_access_region — From where can vendor staff access data? [unknown]: From where can vendor staff access data? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. - residency_plan — Which plan or option provides residency? [unknown]: Which plan or option provides residency? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training ### DATA-02: Deployment options Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial The researched offering is Microsoft-operated tenant SaaS; other deployment contracts remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: dedicated_instance, customer_cloud, on_premise, air_gapped, mode_feature_gaps. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Enterprise protection documents isolated customer tenants in Microsoft 365. Sources: microsoft-copilot:ms-edp. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unverified after checking Microsoft Copilot commercial plans and architecture; dedicated-instance, customer-cloud, full on-premises and air-gapped offerings and thresholds not established. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unverified after checking Microsoft Copilot commercial plans and architecture; dedicated-instance, customer-cloud, full on-premises and air-gapped offerings and thresholds not established. - on_premise — Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? Unverified after checking Microsoft Copilot commercial plans and architecture; dedicated-instance, customer-cloud, full on-premises and air-gapped offerings and thresholds not established. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unverified after checking Microsoft Copilot commercial plans and architecture; dedicated-instance, customer-cloud, full on-premises and air-gapped offerings and thresholds not established. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? Unverified after checking Microsoft Copilot commercial plans and architecture; dedicated-instance, customer-cloud, full on-premises and air-gapped offerings and thresholds not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-edp #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial A hosted web service is offered; tenant architecture and alternative deployment contracts remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [partial]: The public web service accepts individual accounts and processes content with hosting/model providers. Its exact multitenant architecture and boundaries are not documented in the retrieved public material. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - on_premise — Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy ### DATA-03: Training use and provider retention Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial No-training assertions and provider exceptions are recorded separately from customer retention. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - No-training statements remain vendor assertions pending direct contract verification. Stored tenant chat history is distinct from provider retention. - vendor_training — Does the vendor train on customer content? [partial]: Microsoft states commercial prompts, responses and Graph data do not train foundation models; the underlying DPA text was not inspected. Sources: microsoft-copilot:ms-no-training. - provider_training — Do model providers train on it under this product's contracts? [partial]: Microsoft makes the same foundation-model statement; separate Data Retention model terms require their own review. Sources: microsoft-copilot:ms-no-training, microsoft-copilot:ms-anthropic. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Some Anthropic models explicitly retain data under separate Anthropic terms; ordinary eligible subprocessor models are described differently. No universal retention period is established. Sources: microsoft-copilot:ms-anthropic. - zero_retention — Is zero data retention available, and on which plan? [partial]: Eligible Anthropic subprocessor offerings are described as not retaining customer content; this is not zero retention for M365 interactions. Sources: microsoft-copilot:ms-anthropic. - human_review — Can provider staff review content? [partial]: Copilot opts out of Azure OpenAI abuse-monitoring human review; Anthropic illegal-content safeguards are separate. Sources: microsoft-copilot:ms-no-training, microsoft-copilot:ms-anthropic. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-no-training, microsoft-copilot:ms-anthropic #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial No vendor training is asserted, with provider exceptions and customer-key responsibility explicitly retained. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - vendor_training — Does the vendor train on customer content? [supported]: FAQ says T3 does not train its own models and the privacy policy says personal information is not used to train AI models. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy. - provider_training — Do model providers train on it under this product's contracts? [supported]: The FAQ says OpenAI/Anthropic defaults are not opted into training, Google paid models disable training and OpenRouter training routes are disabled. Some new models may require training and are labeled; BYOK customers manage their own provider settings. Sources: t3-chat:t3-chat:faq-training. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Purview governs retained Exchange copies of managed Copilot interactions; uploaded-file repository retention is outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Managed work/school Microsoft Copilot and Copilot Chat with EDP; Exchange prompt/response copies governed by applicable Purview retention/holds; add_ons=Eligible Microsoft365 tenant, Applicable Purview retention/eDiscovery licensing and configured policies; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Narrowed scope resolves the publication conflict for this finding: Exchange interaction copies are separate from uploaded-file repositories and temporary prompt context. - No universal18-month file-retention promise or immediate-deletion guarantee is made. Full repository/post-termination behavior needs a separate source/tenant check. - default_retention — What is retained and for how long by default? [partial]: Prompts/responses are logged in Exchange; retention depends on tenant policies. A universal default duration for uploaded files/indexes is not established and is excluded from this Exchange-interaction scope. Sources: microsoft-copilot:ms-chat-privacy-r2, microsoft-copilot:ms-retention-r2. - admin_retention — Can admins set retention periods? [supported]: Purview can retain/delete interaction copies; retention and eDiscovery holds can suspend permanent deletion. Sources: microsoft-copilot:ms-retention-r2. - user_deletion — Can users delete their chats and files permanently? [partial]: Removing visible history does not immediately delete retained Exchange copies; retention/hold processing continues asynchronously. Sources: microsoft-copilot:ms-retention-r2. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Unverified after checking Purview retention and privacy documentation; complete post-termination deletion terms were not retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-chat-privacy-r2, microsoft-copilot:ms-retention-r2 #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Termination export responsibilities are contractual; plan-specific temporary-chat behaviour and retention remain unknown. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual T3 Chat service Terms; temporary-chat Free/Pro/Premier entitlement not established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved. - default_retention — What is retained and for how long by default? [unknown]: The generic URL FAQ distinguishes temporary and persisted threads but does not map that feature to a named individual tier or specify server/provider/file/backup retention. No plan-specific temporary-chat retention claim is made. - admin_retention — Can admins set retention periods? [unknown]: Can admins set retention periods? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved. - user_deletion — Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved. - contract_end_deletion — What is deleted at contract end, and when? [partial]: Terms put responsibility on users to export before termination and endeavor to provide a reasonable retrieval opportunity only for vendor-convenience termination; deletion timing and certificate are unspecified. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft publishes subprocessor governance and change-notification routes; legal transfer details need direct contract review. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: subprocessor_countries, parent_jurisdiction, transfer_mechanism, government_access_policy. - Read each atomic answer for its plan, access and feature limits. - subprocessor_list — Is a dated sub-processor list published? [partial]: The AI subprocessor overview links the Online Services Subprocessors List; a dated country-by-country copy was not downloaded. Sources: microsoft-copilot:ms-subprocessors. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? Unverified after checking AI subprocessor overview and linked Service Trust Portal; countries, contracting jurisdiction, transfer clauses and government-access policy not retrieved in this pass. - change_notification — Are customers notified of sub-processor changes? [partial]: Customers can subscribe to list updates. Exact advance-notice periods were not established. Sources: microsoft-copilot:ms-subprocessors. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [unknown]: Which jurisdiction governs the vendor and its parent? Unverified after checking AI subprocessor overview and linked Service Trust Portal; countries, contracting jurisdiction, transfer clauses and government-access policy not retrieved in this pass. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? Unverified after checking AI subprocessor overview and linked Service Trust Portal; countries, contracting jurisdiction, transfer clauses and government-access policy not retrieved in this pass. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: Is there a published government-access or transparency policy? Unverified after checking AI subprocessor overview and linked Service Trust Portal; countries, contracting jurisdiction, transfer clauses and government-access policy not retrieved in this pass. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-subprocessors #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Named providers and a US vendor address are public, without a complete processor-country or transfer contract matrix. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [partial]: The May31,2025 privacy policy names Azure, AWS, Vercel, OpenAI, Google, Anthropic and OpenRouter, explicitly non-exhaustively. This is not established as a complete Article28 subprocessor schedule. Sources: t3-chat:t3-chat:privacy. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved. - change_notification — Are customers notified of sub-processor changes? [partial]: Privacy policy says material changes are posted with an updated effective date. A processor-addition notice period and objection right are not specified. Sources: t3-chat:t3-chat:privacy. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The policy and Terms identify T3 Tools Inc with a San Francisco address and US/California legal context. A separate parent entity, incorporation jurisdiction and ownership were not independently established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The policy allows disclosures for subpoenas, warrants and legal investigations. No separate transparency report or detailed challenge/notification policy was retrieved. Sources: t3-chat:t3-chat:privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ### DATA-06: Contracts and regulatory coverage Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise data protection links a DPA and Product Terms; no regulatory compliance verdict is made. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: governing_law, ai_act_materials, sector_materials. - Read each atomic answer for its plan, access and feature limits. - dpa — Is a DPA available, and is it negotiable? [partial]: Microsoft says commercial Copilot/Chat are covered by its DPA and Product Terms; negotiability was not verified. Sources: microsoft-copilot:ms-edp. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: The enterprise protection page names GDPR; Swiss revDSG wording was not inspected. Sources: microsoft-copilot:ms-edp. - governing_law — Which law and court govern the contract? [unknown]: Which law and court govern the contract? Unverified after checking Enterprise data protection; the public DPA document index timed out, so law/court, AI Act and sector clauses remain unverified. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Unverified after checking Enterprise data protection; the public DPA document index timed out, so law/court, AI Act and sector clauses remain unverified. - sector_materials — Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? Unverified after checking Enterprise data protection; the public DPA document index timed out, so law/court, AI Act and sector clauses remain unverified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-edp #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public consumer/service terms use California law; an enterprise GDPR/Swiss DPA remains unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [unknown]: Is a DPA available, and is it negotiable? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [unknown]: Does the DPA cover revDSG and GDPR? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - governing_law — Which law and court govern the contract? [supported]: Terms section19 uses California law and individual JAMS arbitration in Santa Clara County, with small-claims/injunction exceptions and state/federal Santa Clara courts where arbitration does not apply. Sources: t3-chat:t3-chat:terms. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. - sector_materials — Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### DATA-07: Certifications and attestations Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial BSI’s public registry verifies Microsoft 365 ISMS/privacy certificates with validity through July 28, 2027. A Copilot-specific certificate schedule and current SOC/C5 reports remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Registry verification covers the named Microsoft 365 ISMS/privacy scope; the issuer entries do not separately enumerate Copilot. - No restricted Service Trust Portal document, Copilot ISO 42001 certificate schedule, current SOC 2 audit period or C5 report was inspected. - Vendor-listed ISO 42001 scope is distinguished from issuer-verified ISO 27001/27701 metadata. - iso_27001 — ISO 27001 with scope and validity? [partial]: BSI registry entry IS 552878 verifies Microsoft Corporation’s Microsoft 365 services ISMS against ISO/IEC 27001:2022, effective July 29, 2024 through July 28, 2027, under a February 14, 2024 applicability statement. Microsoft places Copilot under Microsoft 365 compliance commitments; the issuer entry does not separately enumerate Copilot, so exact app-scope verification remains incomplete. Sources: microsoft-copilot:microsoft-copilot:r5-bsi-iso27001, microsoft-copilot:microsoft-copilot:r5-copilot-compliance-boundary. - soc2 — SOC 2 type, period and covered service? [unknown]: Unresolved on 2026-10-26. Searched https://servicetrust.microsoft.com/ViewPage/HomePageV2 and its public search index, https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2 and BSI’s Microsoft certificate directory. STP retrieval returned a JavaScript shell; indexed report/bridge-letter titles are not an inspected auditor opinion, audit period or Copilot-specific system description. No authenticated report was accessed. - c5 — BSI C5 attestation? [unknown]: Unresolved on 2026-10-26. Searched https://servicetrust.microsoft.com/ViewPage/HomePageV2 and its public report index plus https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2 . Microsoft describes C5 controls in Office 365 SOC reporting, but a current C5 report and exact Copilot service scope/period were not retrieved; no Azure-only attestation was transferred to Copilot. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: BSI PM 741035 verifies Microsoft 365 services’ processor privacy-management scope against ISO/IEC 27701:2019, effective July 29, 2024 through July 28, 2027. Microsoft’s public ISO 42001 page names Copilot/Chat, but its product-specific certificate issuer/validity were not obtained. No TISAX evidence or separately enumerated Copilot 27701 scope was verified. Sources: microsoft-copilot:microsoft-copilot:r5-bsi-iso27701, microsoft-copilot:microsoft-copilot:r5-iso42001-scope. - report_access — How can customers obtain reports? [supported]: Customers use the Microsoft Service Trust Portal for audit reports. Some downloads require an Entra organizational cloud-services account and acceptance of a compliance-material NDA. No restricted document was accessed in this research. Sources: microsoft-copilot:microsoft-copilot:r4-report-access. - pentest — Are independent penetration test summaries available? [partial]: STP documents a Pen Test and Security Assessments category for third-party attestations. No Copilot-specific assessment scope, date or summary was downloaded. Sources: microsoft-copilot:microsoft-copilot:r4-report-access. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:microsoft-copilot:r4-report-access, microsoft-copilot:microsoft-copilot:r5-bsi-iso27001, microsoft-copilot:microsoft-copilot:r5-bsi-iso27701, microsoft-copilot:microsoft-copilot:r5-copilot-compliance-boundary, microsoft-copilot:microsoft-copilot:r5-iso42001-scope #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### DATA-08: Encryption and key control Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN). #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft documents encryption and tenant separation; key-control coverage varies by component. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: private_networking. - Read each atomic answer for its plan, access and feature limits. - encryption_at_rest — Is data encrypted at rest? [supported]: Enterprise protection documents encryption at rest and in transit. Sources: microsoft-copilot:ms-edp. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: Agent Builder explicitly does not support customer-managed keys; this does not establish the key policy of every M365 workload. Sources: microsoft-copilot:ms-builder. - private_networking — Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unverified after checking enterprise data protection and Agent Builder limitations; private networking/IP restrictions and complete key-location matrix not established. - tenant_isolation — How are customers separated in shared SaaS? [supported]: Microsoft documents separation of customer tenants; isolation was not tested. Sources: microsoft-copilot:ms-edp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-edp, microsoft-copilot:ms-builder #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Commercial data protection and model-specific access safeguards are documented; a scoped professional-secrecy undertaking was not verified. Availability: unknown Delivery: unknown Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=German §203 StGB and Swiss Art.321 StGB use cases; existing hosting, support and provider-location exceptions still apply.; os=not specified. Limitations: - General confidentiality, a DPA and no-training commitments do not establish a professional-secrecy undertaking. No vendor/sales contact or agreement signing was performed. - No legal compliance verdict; unknown does not mean the offering is unavailable. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? Unverified after checking commercial Copilot/Chat enterprise-data-protection, privacy, EU Data Boundary and Anthropic processing pages, plus official-domain searches for professional secrecy, §203 and Art.321. The Microsoft-hosted German data-secrecy amendment PDF redirected to login, so its current text, Copilot plan coverage, subprocessor obligations, signatures, price and Swiss applicability were not verified. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: Does the undertaking extend to its sub-processors, and is that documented? Unverified after checking commercial Copilot/Chat enterprise-data-protection, privacy, EU Data Boundary and Anthropic processing pages, plus official-domain searches for professional secrecy, §203 and Art.321. The Microsoft-hosted German data-secrecy amendment PDF redirected to login, so its current text, Copilot plan coverage, subprocessor obligations, signatures, price and Swiss applicability were not verified. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: Is it a dedicated offering or add-on, and on which plan? Unverified after checking commercial Copilot/Chat enterprise-data-protection, privacy, EU Data Boundary and Anthropic processing pages, plus official-domain searches for professional secrecy, §203 and Art.321. The Microsoft-hosted German data-secrecy amendment PDF redirected to login, so its current text, Copilot plan coverage, subprocessor obligations, signatures, price and Swiss applicability were not verified. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Microsoft documents Azure OpenAI abuse-monitoring human-review exclusion and distinguishes optional Anthropic subprocessor models from models under separate retention terms. This does not establish a complete staff/subprocessor plain-text access matrix or a §203/Art.321 restriction. Sources: microsoft-copilot:ms-no-training, microsoft-copilot:ms-anthropic, microsoft-copilot:ms-eudb. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? Unverified after checking commercial Copilot/Chat enterprise-data-protection, privacy, EU Data Boundary and Anthropic processing pages, plus official-domain searches for professional secrecy, §203 and Art.321. The Microsoft-hosted German data-secrecy amendment PDF redirected to login, so its current text, Copilot plan coverage, subprocessor obligations, signatures, price and Swiss applicability were not verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-no-training, microsoft-copilot:ms-anthropic, microsoft-copilot:ms-eudb #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public policies describe vendor/provider content processing, but professional-secrecy contracts and a business plan remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual account service; no business/professional-secrecy offer verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US/international policy; no DE/CH-specific arrangement verified; os=not specified. Limitations: - No-training statements and personal account terms are not a professional-secrecy undertaking. - No legal suitability or compliance conclusion. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public DPA or signed/signon §203 StGB/Art321 StGB professional-secrecy undertaking covering T3 staff was retrieved from the Terms, privacy/security policies or targeted first-party searches. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy names hosting/model services but does not establish a dedicated professional-secrecy undertaking binding them. Its existence and flow-down are unknown. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: A team/business offer itself remains unverified; no professional-secrecy-specific tier, dedicated package or paid add-on was established. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Privacy policy sends input to selected OpenAI/Google/Anthropic/OpenRouter services; Terms reserve vendor review/removal of content upon apparent violations. This establishes processing/review possibilities, not an exhaustive plaintext staff/provider access matrix or protected-profession arrangement. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public consumer/service Terms and privacy/security pages were reviewed, with targeted §203/Art321/professional-secrecy searches. No specific template, protected-profession data-flow statement or professional-body guidance was retrieved; no private agreement was requested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms ## Commercials and vendor ### VEN-01: Pricing model and list prices Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pricing combines seat licensing with usage-based extensions and base-suite prerequisites. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Read each atomic answer for its plan, access and feature limits. - pricing_unit — What is the pricing unit? [supported]: Paid Copilot is a per-user add-on; Chat is included with eligible M365 and some extensions are metered. Sources: microsoft-copilot:ms-price-us. - list_prices — What are list prices per plan, with date and currency? [supported]: Retrieved 2026-10-21: US USD 30/user/month billed annually; Germany EUR 26/user/month billed annually, excluding VAT. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-price-de. - included_usage — What usage is included? [partial]: Paid users have included qualifying assistive-agent usage; exact limits and exclusions depend on the scenario. Sources: microsoft-copilot:ms-credit-rates. - add_ons — Which features cost extra? [supported]: Qualifying M365 licensing is separate; Cowork is metered and compliance tools can need further entitlements. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-setup. - overage — What do usage beyond limits and premium models cost? [partial]: Credits have feature-dependent rates; prepaid exhaustion may continue into PAYG. Currency-per-credit and full premium-model rate mapping were not retrieved. Sources: microsoft-copilot:ms-credit-rates, microsoft-copilot:ms-cost-setup. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-us, microsoft-copilot:ms-price-de, microsoft-copilot:ms-credit-rates, microsoft-copilot:ms-setup, microsoft-copilot:ms-cost-setup #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual subscription prices are supported by vendor replies; quotas are cost-based and checkout/organization details are incomplete. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Staff pricing replies are first-party but undated; current checkout amounts and tax/plan availability were not observed. - pricing_unit — What is the pricing unit? [supported]: Evidence describes monthly individual Pro/Premier subscriptions, optional customer provider keys and cost-based included use. No organizational seat/pool contract is established. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage. - list_prices — What are list prices per plan, with date and currency? [partial]: Vendor replies confirm USD8/month paid-tier context and Premier USD50/month plus applicable tax. No checkout was completed and no business price was retrieved; dates of the undated replies are unknown. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility. - included_usage — What usage is included? [supported]: Included usage is represented by Base and Overage balances, refilling four-hourly/monthly. The FAQ’s20/200 example is not the actual plan quota and the former1500+100 message claim is not used. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:billing-change. - add_ons — Which features cost extra? [partial]: Customer OpenRouter/OpenAI API keys incur direct provider charges. Staff says a top-up product has not been offered since the new billing model and options are only being considered. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai. - overage — What do usage beyond limits and premium models cost? [partial]: The Overage bucket is a monthly included-usage bucket, not an established published dollar-per-token overage tariff. Extra usage via own keys is billed by the customer provider; current model/route tariffs are not fully mapped. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:premier. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai ### VEN-02: Scenario cost Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial A reproducible licence-only scenario is available; full rollout cost remains open. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Shared assumptions v1.3; ECB 2026-10-20 EUR 1 = USD 1.1215 = CHF 0.9237. The stated mix is a research assumption, not an observed workload or entitlement. - Full totals remain baseline + unknown because additional licences, workload capacity, optional support and deployment costs were not priced. - cost_200 — Year-one cost at 200 users? [partial]: From EUR 62400.00 + unknown, or CHF 57638.88 + unknown, for 12 months excluding VAT. Licence-only incremental add-on baseline at EUR 26/user/month; eligible M365 licences assumed already owned. ALM-14 shared cost assumptions v1.4, 2026-10-21: 60% light at 100, 30% regular at 400, 10% power at 1,500 messages/user/month; 3,000 input and 600 output tokens/message where usage is billed separately. No metered agent/Cowork usage or discounts assumed; included-capacity sufficiency is unverified. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:fx-20261020. - cost_1000 — Year-one cost at 1,000 users? [partial]: From EUR 312000.00 + unknown, or CHF 288194.40 + unknown, for 12 months excluding VAT. Licence-only incremental add-on baseline at EUR 26/user/month; eligible M365 licences assumed already owned. ALM-14 shared cost assumptions v1.4, 2026-10-21: 60% light at 100, 30% regular at 400, 10% power at 1,500 messages/user/month; 3,000 input and 600 output tokens/message where usage is billed separately. No metered agent/Cowork usage or discounts assumed; included-capacity sufficiency is unverified. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:fx-20261020. - cost_5000 — Year-one cost at 5,000 users? [partial]: From EUR 1560000.00 + unknown, or CHF 1440972.00 + unknown, for 12 months excluding VAT. Licence-only incremental add-on baseline at EUR 26/user/month; eligible M365 licences assumed already owned. ALM-14 shared cost assumptions v1.4, 2026-10-21: 60% light at 100, 30% regular at 400, 10% power at 1,500 messages/user/month; 3,000 input and 600 output tokens/message where usage is billed separately. No metered agent/Cowork usage or discounts assumed; included-capacity sufficiency is unverified. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:fx-20261020. - variable_share — Which part depends on usage? [partial]: Cowork and uncovered agent/credit usage add variable charges. No model/task tariff is substituted where the product does not publish the required rate. Sources: microsoft-copilot:ms-price-us. - unknown_parts — Which costs could not be priced? [partial]: Base-suite renewal costs, metered workload, usage headroom, implementation and optional compliance/support charges remain unpriced. Sources: microsoft-copilot:ms-price-us. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:fx-20261020, microsoft-copilot:ms-price-us #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multiplying individual list prices yields conditional licence floors, not a verified organization quote or usage-complete TCO. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Conditional independent Pro/Premier account multiplication; no organization plan verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Known price floor + unknown components; no complete year-one TCO, seat commitment or sufficient-usage guarantee. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months,list prices,exVAT,no negotiated discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330,each3000 input+600 output tokens incl retrieval. Vendor subscription usage remains subject to cost/refill limits; no fixed default/recommended model or complete tariff is published, so coverage and variable extra cost stay unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; divideUSD by1.1215 then multiplyEUR by0.9237. For200 separate accounts: Pro from USD19,200/EUR17,119.93/CHF15,813.68 + unknown; Premier reference USD120,000/EUR106,999.55/CHF98,835.49 + unknown. Bulk purchase and business-governance fit unverified. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - cost_1000 — Year-one cost at 1,000 users? [partial]: Same assumptions,1000 separate accounts: Pro from USD96,000/EUR85,599.64/CHF79,068.39 + unknown; Premier reference USD600,000/EUR534,997.77/CHF494,177.44 + unknown. Not a1000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - cost_5000 — Year-one cost at 5,000 users? [partial]: Same assumptions,5000 separate accounts: Pro from USD480,000/EUR427,998.22/CHF395,341.95 + unknown; Premier reference USD3,000,000/EUR2,674,988.85/CHF2,470,887.20 + unknown. Not a5000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx. - variable_share — Which part depends on usage? [partial]: Included usage consumes a cost meter with no complete published tariff/default model. For an optional direct-provider BYOK comparison only, the shared gpt-6-luna effort-none Standard proxy is USD0.10 input/USD0.50 output per1M and USD2.376/user/year at the shared mix, excluding cache/tools/embeddings/regional uplift. This exact model/route is not verified selectable in T3 and is not added to the subscription floor as though it were a vendor tariff. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model. - unknown_parts — Which costs could not be priced? [supported]: Unpriced: enterprise/bulk entitlement, organization features, exact current checkout prices, model availability and complete token/search/file tariff, whether the shared workload fits refill quotas, direct-provider/OpenRouter route charges, regional processing and support/implementation. No assumed wholesale discount or model-cost subsidy. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:byok-router. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:byok-router ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Eligible M365 users can evaluate Copilot Chat directly; paid pilot terms remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: sales_gate. - Read each atomic answer for its plan, access and feature limits. - free_tier — Is there a free tier for business use? [supported]: Chat has no incremental charge for eligible M365 work accounts, with enterprise protections. Sources: microsoft-copilot:ms-price-us. - self_serve_trial — Is a self-serve business trial available? [partial]: The enterprise page offers Chat access as the evaluation path; a timed paid add-on trial was not established. Sources: microsoft-copilot:ms-price-us. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Chat includes enterprise protection and agent management, but full paid work grounding and other enterprise scenarios need their prerequisites. Sources: microsoft-copilot:ms-price-us. - sales_gate — Does meaningful evaluation require sales contact? [unknown]: Does meaningful evaluation require sales contact? Unverified after checking enterprise pricing FAQ; no signup, card check or enterprise trial was performed. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-us #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Free usage is in the Terms; a business-specific trial and enterprise evaluation path remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [partial]: Terms say services are free up to unspecified usage limits and paid resources may be required. Organizational acceptance is allowed, but no free business admin entitlement is established. Sources: t3-chat:t3-chat:terms. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created. - sales_gate — Does meaningful evaluation require sales contact? [partial]: A public browser service and free-limited offer are documented; business-specific meaningful evaluation and any sales gate cannot be determined without an established business offer. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public seat prices are visible; procurement and cancellation details remain partly specified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: minimum_commitment, cancellation, local_invoicing. - Read each atomic answer for its plan, access and feature limits. - minimum_commitment — What seat or spend minimum applies? [unknown]: What seat or spend minimum applies? Unverified after checking enterprise price cards and FAQ; seat minimums, downgrade/cancellation rules and contracting-entity currency terms not retrieved. - contract_length — What contract lengths are offered? [supported]: The quoted add-on price uses annual auto-renewing subscription billing. Sources: microsoft-copilot:ms-price-de. - cancellation — How can the contract be cancelled or reduced? [unknown]: How can the contract be cancelled or reduced? Unverified after checking enterprise price cards and FAQ; seat minimums, downgrade/cancellation rules and contracting-entity currency terms not retrieved. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? Unverified after checking enterprise price cards and FAQ; seat minimums, downgrade/cancellation rules and contracting-entity currency terms not retrieved. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: list seat prices exist, while base licensing, metered services and negotiated terms change total cost. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:ms-price-us. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-price-de, microsoft-copilot:ms-price-us #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual monthly upgrades/downgrades are documented; business minimums and European invoicing remain unverified. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [partial]: The public evidence concerns individual accounts and monthly prices, not a minimum team-seat/spend commitment. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier. - contract_length — What contract lengths are offered? [supported]: Vendor replies confirm monthly Premier pricing and billing periods; no signed annual or business-term offer was retrieved. Sources: t3-chat:t3-chat:premier. - cancellation — How can the contract be cancelled or reduced? [supported]: Terms permit account cancellation at any time without refunds. Staff says upgrades take effect immediately and downgrades at the billing-period end. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? No team minimum, European contracting entity or CHF/EUR invoice entitlement was retrieved. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: some individual prices are confirmed in undated staff replies, complete final checkout requires billing information, quotas are not a public token tariff, and a business offer remains unverified. Sources: t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage ### VEN-05: Source licence Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Commercial hosted-service use is governed by restrictive Microsoft licence terms; component source licences remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - This records hosted-service contractual rights, not an audited licence inventory for every client, sample or connector. - licence_type — Which licence applies to each component? [partial]: The hosted commercial service uses Microsoft Online Services Product Terms. Use is limited to the licensing agreement, rights are reserved, and reverse engineering is restricted. Individual client and connector source licences were not inventoried. Sources: microsoft-copilot:microsoft-copilot:r4-online-service-terms. - branding_restrictions — Do licence terms restrict branding or user counts? [unknown]: Do licence terms restrict branding or user counts? Unverified after checking Microsoft product, licensing and Agent Builder documentation; no service/client/connector source-licence inventory or current product licence grant was inspected. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unverified after checking Microsoft product, licensing and Agent Builder documentation; no service/client/connector source-licence inventory or current product licence grant was inspected. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:microsoft-copilot:r4-online-service-terms #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial The hosted service is proprietary; clone hackathons and T3 Code are separate products. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - licence_type — Which licence applies to each component? [supported]: Terms grant a personal nonassignable service licence and prohibit copying, modification, reverse engineering and source extraction, subject to third-party software rights. Sources: t3-chat:t3-chat:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: Terms reserve vendor trademarks and prohibit sublicensing/renting/providing service access to others; each account is personal and cannot be shared. Sources: t3-chat:t3-chat:terms. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? No supported self-host licence, open-source core/enterprise split or enterprise edition licence was retrieved. Public third-party clones are not licensed distributions of the hosted product. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Compliance search/export is distinct from a reusable complete workspace exit. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: assistant_export, knowledge_export, post_termination_window. - Read each atomic answer for its plan, access and feature limits. - chat_export — Can admins export all chats? [partial]: Microsoft documents Content search/Purview access and Teams Export APIs for stored interaction data; completeness across every chat surface was not tested. Sources: microsoft-copilot:ms-privacy. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unverified after checking Copilot privacy, retention and Agent Builder documentation; no admin export or post-contract retrieval test. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unverified after checking Copilot privacy, retention and Agent Builder documentation; no admin export or post-contract retrieval test. - export_format — Are formats documented and machine-readable? [partial]: Teams has an export API route; a complete reusable chat/assistant/knowledge format was not established. Sources: microsoft-copilot:ms-privacy. - post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? Unverified after checking Copilot privacy, retention and Agent Builder documentation; no admin export or post-contract retrieval test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-privacy #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Terms require pre-termination export, but a documented organizational export package was not established. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - export_format — Are formats documented and machine-readable? [unknown]: Are formats documented and machine-readable? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees. - post_termination_window — How long can data be retrieved after termination? [partial]: Users must export before termination. If the vendor terminates for convenience it will endeavor to allow a reasonable retrieval opportunity; no fixed post-termination window is guaranteed. Sources: t3-chat:t3-chat:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms ### VEN-07: Support and service levels Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Copilot support entry points are documented; plan-specific response, language and SLA commitments remain gaps. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Developer/extensibility support route only; no support case or sales request was opened. - support_channels — Which support channels are available on each plan? [partial]: Copilot service/development support uses Admin Center Help and Support; the extensibility guide ties service requests to a Premier/Unified support agreement. General questions can use Microsoft Q&A. A complete plan/language/SLA matrix was not retrieved. Sources: microsoft-copilot:microsoft-copilot:r4-support-channels. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unverified after checking https://status.cloud.microsoft/ returned a JavaScript-only shell; Copilot setup and enterprise plans did not establish language-specific support hours, regional team, response targets or applicable SLA credits. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: Is there a DACH or Swiss entity, team or partner? Unverified after checking https://status.cloud.microsoft/ returned a JavaScript-only shell; Copilot setup and enterprise plans did not establish language-specific support hours, regional team, response targets or applicable SLA credits. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unverified after checking https://status.cloud.microsoft/ returned a JavaScript-only shell; Copilot setup and enterprise plans did not establish language-specific support hours, regional team, response targets or applicable SLA credits. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unverified after checking https://status.cloud.microsoft/ returned a JavaScript-only shell; Copilot setup and enterprise plans did not establish language-specific support hours, regional team, response targets or applicable SLA credits. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: microsoft-copilot:microsoft-copilot:r4-support-channels #### T3 Chat Verification status: Agent cross-checked (agent-cross-checked) Support: partial Email support and official feedback are public, without a retrieved SLA or regional-language contract. Availability: generally-available Delivery: native Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: The FAQ lists a support email and official feature/bug board; plan-specific response targets are not published there. Sources: t3-chat:t3-chat:faq-support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: The vendor publishes a San Francisco contact address. A DACH/Swiss entity, partner or support team was not established. Sources: t3-chat:t3-chat:privacy. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-support, t3-chat:t3-chat:privacy ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### Microsoft Copilot Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft publishes role-based learning and adoption materials. Availability: generally-available Delivery: native Scope: surfaces=Microsoft Copilot Chat web app, Microsoft Copilot paid work chat, Copilot in Microsoft 365 apps and Teams, Microsoft Copilot desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Microsoft Copilot Chat with eligible Microsoft 365 subscription; paid Microsoft Copilot add-on where stated; add_ons=Qualifying Microsoft 365 base licence, Purview and SharePoint Advanced Management entitlements where stated, Copilot Credits usage-based billing for Cowork and other metered features where stated; deployment_mode=multi-tenant-saas; region=Commercial cloud; EU/EFTA tenant scope where stated, including Switzerland; no government-cloud generalisation; os=not specified. Limitations: - Unverified parts: onboarding_service, service_cost. - Read each atomic answer for its plan, access and feature limits. - onboarding_service — Is guided onboarding included? [unknown]: Is guided onboarding included? Unverified after checking Copilot Skilling Center and commercial resources; included onboarding entitlements, service language and professional-service fees not established. - user_training — Is end-user training offered, in which languages? [partial]: The Skilling Center lists Academy learning, webinars and instructor-led events; exact DE/FR/IT delivery was not checked. Sources: microsoft-copilot:ms-training. - use_case_library — Are role-based use cases and templates provided? [supported]: Copilot Prompt Gallery offers starter prompts. Sources: microsoft-copilot:ms-price-us. - adoption_programme — Is there a champion or adoption programme? [supported]: Microsoft links its Champion programme and adoption resources. Sources: microsoft-copilot:ms-training. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unverified after checking Copilot Skilling Center and commercial resources; included onboarding entitlements, service language and professional-service fees not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: microsoft-copilot:ms-training, microsoft-copilot:ms-price-us #### T3 Chat Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Sources ### microsoft-copilot:ms-ppt-model-r2 Choose your model when editing with Copilot in PowerPoint. Commercial PowerPoint editing documents Auto, ChatGPT and Claude choices, with Anthropic admin enablement and session/region limits. - URL: https://support.microsoft.com/en-us/office/choose-your-model-when-editing-with-copilot-in-powerpoint - Locator: Commercial subscription requirement; editing-mode selector; session and region limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:faq-training T3 Chat FAQ. The vendor says it does not train models, configures OpenAI/Anthropic/paid Google/OpenRouter no-training where possible, labels exceptions and makes BYOK customers responsible for settings. - URL: https://t3.chat/faq - Locator: Do you use my data for training? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:billing-change Usage model change. Vendor replies confirm current cost-based usage and that an USD8 subscription can still use expensive models within cost limits. - URL: https://feedback.t3.chat/p/t3-feels-nerfed-now - Locator: Mark Florkowski Team replies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-paid-tier-controls Pro/Premier vendor replies. The vendor discusses USD8 Pro usage/search costs, optional OpenRouter keys and Premier USD50/month; this does not establish Free parity or a complete model matrix. - URL: https://feedback.t3.chat/p/new-tier-in-between-pro-and-premier - Locator: Mark Florkowski Team: cost explanation, OpenRouter direct billing, USD50 Premier and plan changes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-pro-context-byok Context and own-key controls. Vendor replies document context restrictions on the USD8 tier and optional own-key fallback without publishing a complete current model/file matrix. - URL: https://feedback.t3.chat/p/premium-requests-for-large-context-windows - Locator: Mark Florkowski Team replies on USD8 limits, higher tier, model switching and OpenRouter fallback - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-roadmap AI at Work Roadmap. The roadmap contains dated model launches, identifies Office in Copilot as Frontier and lists Cowork as generally available. - URL: https://www.microsoft.com/en-us/microsoft-365/roadmap - Locator: September model entries; October 9 Office Frontier; June 16 Cowork GA - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-release Microsoft 365 Copilot release notes. Release notes distinguish platform availability and describe gradual tenant rollout. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/release-notes - Locator: October 6 2026; gradual release policy - Evidence kind: documented - Source date: 2026-10-06 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:changelog Changelog of new features. A vendor reply says major-feature changelog is in Discord and a website version is intended; the website request remains Planned. - URL: https://feedback.t3.chat/p/changelog-of-new-features - Locator: Planned status and Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-anthropic Anthropic models in Microsoft Online Services. Anthropic is disabled by default for EU/EFTA/UK tenants, excluded from EU/in-country processing commitments, and retention-labelled models have separate terms. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connect-to-ai-subprocessor - Locator: Opt-in regions; admin settings; Anthropic models with Data Retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-price-us Microsoft Copilot Plans and Pricing - Enterprise. The US page lists Copilot Chat at no additional cost with eligible M365, a USD 30 annual-billing monthly add-on, separate base licensing and metered agent/Cowork use. - URL: https://www.microsoft.com/en-us/copilot/pricing/enterprise - Locator: Copilot Chat; paid add-on; compare plans; FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:faq-usage T3 Chat FAQ. Base refills every four hours and Overage monthly; usage reserves then settles request cost and blocks until refill when both are depleted. Example20/200 points are illustrative, not published quota sizes. - URL: https://t3.chat/faq - Locator: How does the usage meter work? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:r2-premier-buckets Premier usage-limit support. The identifiable vendor reply specifically applies the FAQ bucket mechanics to a Premier account. - URL: https://feedback.t3.chat/p/quickly-reaching-usage-limits-on-premier-plan - Locator: Mark Florkowski Team reply explaining exhausted monthly overage and four-hour bucket - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-upload File upload in Microsoft Copilot. The support article names document/image/text formats and a limit of 20 files per conversation and 50 MB per file. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/file-upload-in-microsoft-copilot - Locator: Supported file formats; file limits; files handling - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-notebooks Get answers and insights about your Microsoft Copilot Notebook. Free Copilot Chat notebooks use up to 50 references; paid notebook grounding uses up to 300, with broader entity types. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/get-answers-and-insights-about-your-microsoft-365-copilot-notebook - Locator: Reference limits and supported content types - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-notebook-instructions Provide custom instructions for your Microsoft Copilot Notebook. Notebook instructions can be edited and shared collaboratively; a SharePoint or OneDrive service plan is required. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/provide-custom-instructions-for-your-microsoft-365-copilot-notebook - Locator: Instructions; sharing note; prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-builder Agent Builder in Microsoft 365 Copilot. Agent Builder creates knowledge/instruction agents, has admin access controls and requires Copilot Studio for authored external actions. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/agent-builder - Locator: Knowledge; licensing; admin controls; known limitations - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-privacy Data, Privacy, and Security for Microsoft Copilot. Microsoft documents the rename, Graph permissions, protected interaction storage, no foundation-model training and residency exceptions. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy - Locator: Rename note; organizational data; stored interactions; EU Data Boundary - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-connector-license-r2 Prerequisites for deploying connectors. Paid Copilot/E7 supports connector grounding and federation; Studio/pay-as-you-go supports synced data in agents only, with no federated entitlement. - URL: https://learn.microsoft.com/en-us/microsoftsearch/licensing - Locator: Licensing matrix; federated prerequisites; synced versus agents - Evidence kind: documented - Source date: 2026-06-02 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-connectors-r2 Copilot connectors overview. Synced connectors index content/ACLs and provide citations; federation fetches live, while this October6 overview retains earlier read-only rollout wording. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/overview - Locator: Architecture; source examples; citations; October rollout note - Evidence kind: documented - Source date: 2026-10-06 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-federated-r2 Federated connectors overview. The October16 detailed guide documents source-authorized writes and per-tool approval; Researcher stays read-only and Coming soon labels the admin Tools view. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/federated-connectors-overview - Locator: Supported experiences; user licence; actions and confirmation; Tools view - Evidence kind: documented - Source date: 2026-10-16 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-custom-mcp-r2 Set up custom federated connectors. Custom MCP prerequisites include create/update/delete tools; user access requires the Copilot licence and intersecting tenant/staging controls. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/set-up-custom-federated-connectors - Locator: MCP prerequisites; OAuth; tenant controls and staged rollout - Evidence kind: documented - Source date: 2026-10-16 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-personal-sync-r2 Self-serve sync connectors overview. Self-serve Confluence/Jira synchronization is a limited-preview per-user route with documented incremental/full crawl intervals. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/personal-sync-connectors-overview - Locator: Limited preview; Confluence/Jira; incremental/full synchronization - Evidence kind: documented - Source date: 2026-08-13 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-setup Set up Microsoft Copilot and assign licenses. IT assigns paid licences through M365; Microsoft documents Entra MFA, conditional access and additional Purview/SAM licensing dependencies. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-setup - Locator: Prerequisites; security; get started and deploy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-dlp Microsoft Purview DLP for Microsoft 365 Copilot and Cowork. Purview policies can detect sensitive prompt types and block Copilot processing; file-label and prompt paths have distinct conditions. - URL: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about - Locator: Sensitive information types; prevent processing prompts; sensitivity labels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-memory Personalize what Microsoft Copilot remembers. Microsoft documents saved memories, prior-chat inferences, custom instructions and user removal controls, with work insights depending on plan. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/personalize-what-microsoft-365-copilot-remembers - Locator: Saved memory; history; work insights; custom instructions; temporary chat - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-agents Get started with agents in the Microsoft Copilot app. Users can discover prebuilt and organization agents and share agent links, subject to account and organization settings. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-agents-in-the-microsoft-365-copilot-app - Locator: Explore agents; create and share - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-chat-privacy Microsoft Copilot Chat Privacy and Protections. Copilot Chat has limited contextual work access, Exchange interaction logging, OneDrive uploads and a separate Bing web-query boundary. - URL: https://learn.microsoft.com/en-us/copilot/privacy-and-protections - Locator: Grounding; organizational data; logging; generated files; EUDB - Evidence kind: documented - Source date: 2026-08-24 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-manage Manage Microsoft Copilot Chat. The Allow web search policy can target the tenant, groups and users and also applies to paid Copilot. - URL: https://learn.microsoft.com/en-us/copilot/manage - Locator: Manage web search queries; Cloud Policy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:faq-url T3 Chat FAQ. A new-chat URL selects a model, reasoning effort, search on/off, one to five searches, a profile and temporary/persisted storage mode. - URL: https://t3.chat/faq - Locator: Custom search URLs and query parameter table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-schedule Schedule your most used Copilot prompts. Paid Copilot users can schedule up to ten prompts and edit, disable or delete schedules. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/schedule-your-most-used-copilot-prompts - Locator: Prerequisites; create; manage scheduled prompts - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-cowork Get started with Copilot Cowork. Cowork requires paid Copilot and enabled usage billing, exposes tool steps, and supports action approval and pause/cancel controls. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/cowork/get-started - Locator: Prerequisites; watch Cowork work; approve actions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-chat-api-r2 Microsoft 365 Copilot Chat API overview. The text Chat API preview requires each user to have the paid add-on, uses grounding/compliance, and excludes graphical/code/action skills. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/api/ai-services/chat/overview - Locator: Licensing; preview terms; limitations - Evidence kind: documented - Source date: 2026-07-02 - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-roadmap-work-iq Microsoft AI at Work roadmap. The roadmap describes Work IQ API public preview with MCP, REST and A2A access to work context. This does not establish that the separate Chat API is an MCP server or confirm endpoint/plan prerequisites. - URL: https://www.microsoft.com/en-us/microsoft-365/roadmap - Locator: April 30, Work IQ API public preview; October 15 legal announcement - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### t3-chat:t3-chat:api-request Subscription-backed API request. Staff rejects the economics of applying a T3 Chat subscription to external coding-agent/API usage; an official general chat API is not established. - URL: https://feedback.t3.chat/p/allow-t3-chat-subscription-to-power-external-coding-agents-or - Locator: Closed status and Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-chat-usage Microsoft Copilot Chat usage report. Unlicensed Copilot Chat usage is reported separately, anonymized by default, with per-user metrics and CSV export. - URL: https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/microsoft-copilot-usage - Locator: Audience; metrics; export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-mdm-deployment Microsoft Copilot app deployment. The Windows Copilot installer can be distributed through Intune, Configuration Manager, Group Policy or another MDM. Automatic Microsoft 365 Apps installation has EEA/government/channel exclusions. The article confirms the Microsoft Copilot rename. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/deploy-microsoft-365-copilot-app - Locator: Deploy via any MDM; prevent automatic installation; rename note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### t3-chat:t3-chat:mobile Mobile App. The vendor released an iOS TestFlight beta on September10,2026 and says Android beta is coming soon. - URL: https://feedback.t3.chat/en/p/mobile-app-77 - Locator: Mark Florkowski, Team, pinned September10,2026 announcement - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-writing-r2 Get started writing prompts in Microsoft Copilot. The support guide gives drafting and Word rewrite examples and separately requires the commercial Copilot subscription for work-data grounding. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-writing-prompts-in-microsoft-365-copilot - Locator: Scope note; draft/edit examples; work-content licence - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r5-chat-translation Copilot Chat file-content translation. Documents can be attached/referenced for prompted translation in Copilot Chat. The page documents tone and audience instructions, not a formatting-preservation guarantee or managed terminology glossary. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/translate-files-into-another-language-in-microsoft-365-copilot-chat - Locator: Translate a file; tone/style/country examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-word-translation-boundary Word Translator and Copilot translation workflow. Word Translator creates a separate translated copy while retaining formatting; Copilot adapts wording, tone and audience. The page still asks users to review tables/layout after translation and does not make Translator the Copilot Chat engine. - URL: https://word.cloud.microsoft/create/en/blog/how-to-translate-documents-in-word/ - Locator: Translate a Word document with Translator; Rewrite translated content with AI; Review checks - Evidence kind: documented - Source date: 2026-09-16 - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-sharepoint-translation SharePoint document translation scope. SharePoint/OneDrive document processing offers format/structure-preserving translated copies, with 40 MB limits and file/permission restrictions. It is a separate service from Copilot Chat. - URL: https://learn.microsoft.com/en-us/microsoft-365/documentprocessing/translation-overview?view=o365-worldwide - Locator: Requirements; translated file copy; release limitations - Evidence kind: documented - Source date: 2026-04-23 - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-sharepoint-glossary SharePoint terminology glossary. Document processing accepts language-pair glossary files, including CSV/TSV/TAB/XLF, selected in its translation workflow. This does not establish a managed glossary in Copilot Chat. - URL: https://learn.microsoft.com/en-us/microsoft-365/documentprocessing/translation-glossary?view=o365-worldwide - Locator: Create and use a custom glossary for document translation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-sharepoint-metering Document processing separate metered billing. Document processing uses an Azure subscription/resource group and a pay-as-you-go meter. A Copilot seat alone is not evidence that the separate glossary translation service is included. - URL: https://learn.microsoft.com/en-us/microsoft-365/documentprocessing/syntex-azure-billing?view=o365-worldwide - Locator: Prerequisites; services list including document translation - Evidence kind: documented - Source date: 2025-08-04 - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r4-image-admin Configure Microsoft Copilot settings. Copilot Settings exposes an image-generation allow/prevent control. Available settings depend on licences, enabled features and rollout; AI Administrator is an example of the required admin role. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/configure-copilot-admin-center - Locator: Configure Copilot actions; Before you begin - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r4-online-service-terms Microsoft Product Terms for Online Services. Commercial use is limited to the licensing agreement and Microsoft reserves other rights. Reverse engineering is restricted. Generative-AI output is Customer Data and Microsoft does not own it; this is not a component-by-component source-licence inventory. - URL: https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all - Locator: Using the Online Services; Acceptable Use; Generative AI Output Content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:ms-voice Get started with Copilot Voice. Work/school dictation and read-aloud are documented, while Voice availability varies and feedback audio is removed after 48 hours. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/get-started-with-voice-features-in-microsoft-365-copilot - Locator: Feature/account matrix; work/school data and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-code-r2 Code interpreter security architecture. Code interpreter in Copilot/eligible declarative agents runs Python analysis and charts in session-isolated Azure VMs with no network traffic. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/code-interpreter-security - Locator: Availability; isolated Azure VM; Python analysis - Evidence kind: documented - Source date: 2025-11-26 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-chat-privacy-r2 Copilot Chat privacy and protections. Managed work Chat logs prompts/responses in Exchange and places uploads in OneDrive for Business; generated Office files have separate download/storage paths. - URL: https://learn.microsoft.com/en-us/copilot/privacy-and-protections - Locator: Exchange logging; OneDrive uploads; Office file generation - Evidence kind: documented - Source date: 2026-08-24 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-language Supported languages for Microsoft Copilot. The supported work/school language list includes English, German, French and Italian, with localization asserted by Microsoft. - URL: https://support.microsoft.com/en-us/microsoft-365-copilot/supported-languages-for-microsoft-365-copilot - Locator: Work or school accounts; localization description - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:security T3 Chat security policy. The vendor asserts TLS, MFA support, secure sessions/access control and regular audits; no independent report or enterprise enforcement configuration is supplied. - URL: https://t3.chat/security-policy - Locator: Data protection, authentication and disclosure program - Evidence kind: vendor-claimed - Source date: 2025-02-14 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-cost-setup Set up usage-based billing for Copilot Credits. The cost dashboard exposes policy and per-user monthly limits and consumes prepaid credit before PAYG overage. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/usage-based-billing-copilot-credits-setup - Locator: Roles; monthly limits; prepaid and PAYG - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-usage Microsoft Copilot usage report. The paid report tracks adoption and application activity and hides identifying user, group and site fields by default. - URL: https://learn.microsoft.com/en-us/microsoft-365/admin/activity-reports/microsoft-365-copilot-usage - Locator: Report metrics and privacy note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-audit Audit logs for Copilot and AI applications. Enabled Purview Audit records Copilot admin changes, users, accessed resources, agent identifiers and policy metadata. - URL: https://learn.microsoft.com/en-us/purview/audit-copilot - Locator: Admin and user activities; common properties - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-audit-standard Learn about auditing solutions in Microsoft Purview. Purview distinguishes standard audit retention from separately licensed longer-retention capabilities. - URL: https://learn.microsoft.com/en-us/purview/audit-solutions-overview - Locator: Audit Standard and Premium retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-retention Learn about retention for Copilot and AI apps. Copilot interaction copies live in hidden Exchange folders, can have Purview retention policies and remain subject to legal holds. - URL: https://learn.microsoft.com/en-us/purview/retention-policies-copilot - Locator: What is included; mailbox retention flow; holds - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-audit-export Audit logs for Copilot and AI applications. Purview supports searching and exporting Copilot audit events, then filtering exported AppIdentity values. This is metadata export, not a claim that audit events contain full prompts and responses. - URL: https://learn.microsoft.com/en-us/purview/audit-copilot - Locator: Accessing Copilot audit logs; Next steps - Evidence kind: documented - Source date: 2026-08-26 - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r4-audit-api Microsoft 365 usage reports in Microsoft Graph. The document identifies EXO Search-UnifiedAuditLog CSV export and Office 365 Management Activity API streaming to SIEM for CopilotInteraction events. It distinguishes these from Graph usage-report APIs. - URL: https://learn.microsoft.com/en-us/graph/api/resources/report?view=graph-rest-beta - Locator: Programmatically export unlicensed Copilot Chat usage - Evidence kind: documented - Source date: 2025-12-23 - Retrieved: 2026-10-26 ### t3-chat:t3-chat:privacy T3 Chat privacy policy. The policy covers user uploads, named hosting/model providers, no AI training, US/international processing and general disclosure practices. - URL: https://t3.chat/privacy-policy - Locator: Sections1-7 and11 - Evidence kind: documented - Source date: 2025-05-31 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:terms T3 Chat Terms of Service. T3 Tools Inc permits organizational acceptance but each account is personal; proprietary restrictions, cancellation/export responsibilities and California dispute terms apply. - URL: https://t3.chat/terms-of-service - Locator: Sections1-6,9,19 and21 - Evidence kind: documented - Source date: 2025-11-15 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-dlp-default Learn about the default DLP policy for Microsoft 365 Copilot location. The default sensitive-prompt DLP policy simulates and alerts rather than blocking until configured otherwise. - URL: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-default-policy - Locator: Simulation mode default - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-custom-dlp-types Purview DLP for Copilot and Cowork. Prompt blocking supports built-in and custom sensitive-information types in preview with tenant rollout caveats. Uploaded-file contents are not scanned by this Copilot DLP location. - URL: https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about - Locator: Block sensitive information types in prompts; Files uploaded in prompts; Availability - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:ms-edp Enterprise data protection in Microsoft Copilot and Microsoft Copilot Chat. Enterprise data protection applies Microsoft DPA/Product Terms and documents encryption and tenant separation. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/enterprise-data-protection - Locator: DPA; protection of prompts and responses - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-eudb What is the EU Data Boundary?. The EU/EFTA boundary covers customer data and pseudonymized personal logs subject to transfer exceptions, with professional-services data committed at rest. - URL: https://learn.microsoft.com/en-us/privacy/eudb/eu-data-boundary-learn - Locator: Overview; logs; countries; configuration - Evidence kind: documented - Source date: 2025-02-26 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-no-training Microsoft Copilot no-training statement. Microsoft states that prompts, responses and Graph data do not train foundation models and that the Copilot service opts out of Azure OpenAI abuse monitoring. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy - Locator: Important; abuse monitoring - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-retention-r2 Learn about retention for Copilot and AI apps. Purview governs Exchange copies of AI interactions and holds, with asynchronous deletion processing distinct from uploaded-file storage. - URL: https://learn.microsoft.com/en-us/purview/retention-policies-copilot - Locator: Interaction storage; retention/hold processing; deleted users - Evidence kind: documented - Source date: 2025-09-26 - Retrieved: 2026-10-21 ### microsoft-copilot:ms-subprocessors Overview of AI Subprocessors. Microsoft links its Online Services Subprocessors List and subscriptions for change notifications. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/copilot-subprocessor-overview - Locator: Subprocessor governance; customer notification - Evidence kind: documented - Source date: 2026-08-18 - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-report-access Microsoft Service Trust Portal access. Microsoft publishes external audit reports and third-party penetration-test attestations in STP; some downloads require an Entra organization account and acceptance of the compliance-material NDA. No report was downloaded. - URL: https://learn.microsoft.com/en-us/compliance/assurance/stp-get-started - Locator: Accessing the Service Trust Portal; Reports, Whitepapers and Artifacts - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-bsi-iso27001 BSI certificate registry: Microsoft 365 ISMS IS 552878. BSI registry verifies Microsoft Corporation IS 552878 for the Microsoft 365 services ISMS, development, operations and PII protection, with a February 14, 2024 applicability statement. It does not name Copilot separately. - URL: https://www.bsigroup.com/en-GB/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/IS%20552878/ - Locator: ISO/IEC 27001:2022; Microsoft Corporation; scope and effective/expiry dates - Evidence kind: certificate-verified - Source date: 2024-07-26 - Retrieved: 2026-10-26 - Issuer: BSI - Certificate scope: Microsoft Corporation; Microsoft 365 services ISMS, development, operations and PII protection; Statement of Applicability dated 2024-02-14. No explicit Copilot-specific scope list was obtained from this registry entry. - Valid: 2024-07-29 to 2027-07-28 - Registry: https://www.bsigroup.com/en-GB/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/IS%20552878/ ### microsoft-copilot:microsoft-copilot:r5-bsi-iso27701 BSI certificate registry: Microsoft 365 privacy PM 741035. BSI verifies the Microsoft 365 services processor privacy-management scope, referring to IS 552878 and the February 14, 2024 applicability statement. Copilot-specific applicability is not independently enumerated. - URL: https://www.bsigroup.com/en-GB/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/PM%20741035/ - Locator: ISO/IEC 27701:2019; processor scope; effective/expiry dates - Evidence kind: certificate-verified - Source date: 2024-07-26 - Retrieved: 2026-10-26 - Issuer: BSI - Certificate scope: Microsoft Corporation; Microsoft 365 services ISMS, development, operations, support and PII protection as a processor; Statement of Applicability dated 2024-02-14; references IS 552878. Not a separately enumerated Copilot certificate. - Valid: 2024-07-29 to 2027-07-28 - Registry: https://www.bsigroup.com/en-GB/products-and-services/assessment-and-certification/validation-and-verification/client-directory-certificate/PM%20741035/ ### microsoft-copilot:microsoft-copilot:r5-copilot-compliance-boundary Copilot Microsoft 365 compliance relationship. Microsoft includes Copilot in its existing Microsoft 365 privacy/security/compliance commitments and lists ISO 27001/42001. This is vendor scope documentation, not the issuer’s Copilot-specific certificate schedule. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/microsoft-365-copilot-privacy - Locator: Meeting regulatory compliance requirements - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### microsoft-copilot:microsoft-copilot:r5-iso42001-scope Microsoft public ISO 42001 service scope. Microsoft explicitly lists Copilot and Copilot Chat in its ISO 42001 service scope. The public page points to STP but does not provide an issuer/certificate validity interval for those products. - URL: https://learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001 - Locator: Microsoft AI services in scope; report route - Evidence kind: vendor-claimed - Source date: 2026-09-11 - Retrieved: 2026-10-26 ### microsoft-copilot:ms-price-de Microsoft Copilot - Pläne und Preise für Unternehmen. The German page lists EUR 26 per user per month billed annually excluding VAT, plus a qualifying M365 subscription. - URL: https://www.microsoft.com/de-de/copilot/pricing/enterprise - Locator: Paid Microsoft 365 Copilot price card and tax notice - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-credit-rates Billing rates and management. Studio billing uses feature-dependent credits, with qualifying paid-user assistive scenarios listed at no charge. - URL: https://learn.microsoft.com/en-us/microsoft-copilot-studio/requirements-messages-management - Locator: Copilot Credits billing table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:overage Overage bucket refill option. The vendor says top-up refill has not been offered since the new billing model. - URL: https://feedback.t3.chat/p/overage-bucket-refill-option - Locator: Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:premier Pro and Premier pricing discussion. The vendor confirms Premier USD50/month plus tax, immediate upgrades and end-period downgrades, and customer OpenRouter keys for direct usage billing. - URL: https://feedback.t3.chat/p/new-tier-in-between-pro-and-premier - Locator: Mark Florkowski Team replies on price, OpenRouter, upgrades and downgrades - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:price-visibility Paid price visibility. Staff says billing information is needed for final tax-inclusive pricing; no checkout was completed. - URL: https://feedback.t3.chat/p/ability-to-see-paid-plan-price-without-going-into-checkout - Locator: Mark Florkowski Team replies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:byok-openai OpenAI BYOK. Staff confirms GPT5 BYOK and recommends fallback priority plus a verified OpenAI organization or removing the key; this is historical model-specific setup, not a complete current model list. - URL: https://feedback.t3.chat/p/enable-byo-api-key-for-gpt-5-and-gpt-5 - Locator: Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:fx-20261020 Euro foreign exchange reference rates. ECB historical XML retrieved directly confirms EUR 1 = USD 1.1215 and CHF 0.9237 for 2026-10-20. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20; USD and CHF entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:byok-router OpenRouter model coverage. The request is marked Completed but the staff reply says those routes do not use OpenRouter and universal rerouting requires future changes. - URL: https://feedback.t3.chat/p/let-openrouter-keys-work-with-more-models - Locator: Completed label versus Mark Florkowski Team reply - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:fx ECB reference exchange rates. EUR1 equals USD1.1215 and CHF0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time2026-10-20 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### t3-chat:t3-chat:openai-price OpenAI API pricing. The shared direct-provider proxy uses USD0.10 input/USD0.50 output per million tokens; T3 availability of this exact route is unverified. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### t3-chat:t3-chat:openai-model GPT-6 Luna documentation. The shared direct-provider proxy uses lowest effort none; this is not a verified T3 default or model-menu entry. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort options - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:microsoft-copilot:r4-support-channels Copilot support and feedback. Copilot extensibility support directs general questions to Microsoft Q&A and service/development issues to Admin Center Help and Support; service requests depend on Premier/Unified support agreement. - URL: https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/feedback - Locator: Developer support channels - Evidence kind: documented - Source date: 2026-01-22 - Retrieved: 2026-10-26 ### t3-chat:t3-chat:faq-support T3 Chat FAQ. The FAQ links its official feedback board and lists support email. - URL: https://t3.chat/faq - Locator: Feature requests and support - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### microsoft-copilot:ms-training Microsoft Copilot Skilling Center. Microsoft publishes admin and user learning resources and links its Champion programme. - URL: https://adoption.microsoft.com/en-us/copilot/skilling-center/ - Locator: Role-based resources; Academy; Champions - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21