--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/microsoft-copilot-vs-unique-ai/" data_url: "https://onaihq.com/compare/agents/microsoft-copilot-vs-unique-ai/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 Unique AI > 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 47 criteria with sourced findings for both products, including 47 that a second agent cross-checked for both. 51 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. - Unique AI source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/microsoft-copilot-vs-unique-ai/ - Machine-readable JSON: https://onaihq.com/compare/agents/microsoft-copilot-vs-unique-ai/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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform catalogue supports several providers, subject to tenant credentials, contracts and validation status. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - providers — Which model providers are available? [partial]: Catalogue includes Azure OpenAI/OpenAI, Anthropic, Google Gemini/Vertex, Together AI and xAI. Provider use must be agreed with each client; a catalogue row is not proof every tenant has it. Sources: unique-ai:unique-ai:models. - current_models — Which current models are selectable on this plan? [partial]: Release 2026.42, hosted 14 October, explicitly adds Azure GPT-6.1 Sol and Claude Opus/Sonnet 5.5 through Anthropic/Vertex. Availability overview also lists Gemini3.8 Flash; provider/tenant credentials and validation differ. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:models. - user_choice — Can users pick the model per chat? [partial]: Space admins set enabled models; release notes describe chat model switching and API per-message model selection under the same rules. Conduct choices depend on administrator configuration. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - 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? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique publishes dated model additions and retirement/migration notes; a complete provider-release lag series remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - 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? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - changelog — Is there a dated public model changelog? [supported]: Availability overview has a dated Recent changes table through 13 October 2026, with provider retirement sources. Sources: unique-ai:unique-ai:models. - deprecation_notice — How much notice is given before a model is removed? [partial]: Dated 14 October release announces migrations ahead of o-series provider retirement on 19 November 2026. No guaranteed Unique contractual notice period is established. Sources: unique-ai:unique-ai:release42. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:release42 ### 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. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Operators can configure customer model endpoints and credentials through GraphQL. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - own_api_keys — Can the customer use its own provider API keys? [supported]: ExternalLanguageModel accepts provider API credentials stored encrypted as immutable write-only values; OAuth2 is also documented. Sources: unique-ai:unique-ai:customllm. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Custom Azure OpenAI deployment examples specify customer endpoint, deployment, API version and token. Compliance docs mention Bedrock; exact supported Bedrock/Vertex contract routes need deployment scoping. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [partial]: Documents self/cloud-hosted LXM endpoints and an Azure-compatible connection object. Universal support for any OpenAI-compatible endpoint is not guaranteed. Sources: unique-ai:unique-ai:customllm. - byo_pricing — Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unknown. BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - byo_restrictions — Which features stop working with BYO? [partial]: Azure Chat Code Execution requires compatible Azure Responses models; switching a custom model group name/deleting an in-use group can break configured assistants. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code ### 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. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform documents custom model and embedding connections. Tool parity depends on the selected route: Code Execution lists Azure and LiteLLM OpenAI compatibility, while arbitrary self-hosted model parity is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform; custom-model/embedding connectors and optional Code Execution availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Code Execution has a listed Responses-capability/model matrix, not universal support for every custom-hosted model. Azure sandbox controls are not extended to every LiteLLM route. - No customer runtime or feature-parity fixture was used; QA-only Phoeniqs is not presented as GA. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Custom LXM and on-premises architecture allow customer-hosted model connections. Models, endpoint compatibility and enabled modules are selected for the contracted deployment. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: An instance maintainer can configure embedding endpoint, key and deployment; the operator overview allows self-hosted embeddings. Supported non-Azure runtimes and a particular customer configuration were not verified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators. - feature_parity — Which features fail with self-hosted models? [partial]: Changing embeddings requires re-embedding existing files. The Code Execution compatibility section explicitly lists Azure Responses-capable IDs and LiteLLM OpenAI IDs, so no blanket Azure-only restriction is asserted. Its introduction/security section describes an Azure sandbox; the actual LiteLLM execution route and parity for arbitrary self-hosted models remain unverified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:review2-code. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: The model catalogue describes Swiss Phoeniqs open models in QA only, not the UAT01/Prod offer. Production entitlement to a vendor-hosted Swiss open model was not established. Sources: unique-ai:unique-ai:review2-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators, unique-ai:unique-ai:review2-code, unique-ai:unique-ai:review2-models ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Models and knowledge/tools are configured per access-controlled Space; optional beta daily spending caps block calls. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-group restriction fixture was run. Exact contract token/message limits, platform-wide model allow-lists and provider data-routing policy remain unverified. - model_allowlist_by_group — Can admins limit models per group? [partial]: Admins bind deployed/approved models to Spaces and grant people/groups space access. Direct per-group model lists across all chats are not documented. Sources: unique-ai:unique-ai:agent. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: A Space binds one model, selected KB sources and tools, and people/group access. A global connector-content model policy is not established. Sources: unique-ai:unique-ai:agent. - default_model — Can admins set the default model? [supported]: Administrators select the model for each Space. Sources: unique-ai:unique-ai:agent. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Off-by-default beta cost management supports daily USD limits at company/group/user levels, reset at user-local midnight. Public fixed token/message quotas are not established. Sources: unique-ai:unique-ai:cost. - limit_behaviour — What happens when a limit is reached? [supported]: With limits enabled, the next model call is blocked when daily spend reaches the cap. Most permissive group limit wins unless a user override exists. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:cost ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat upload defaults are 512 MB/file and 30 files/batch, with source retrieval for large documents. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Configured scanned-PDF OCR is documented: MDI supports image-based PDFs, Docling has partial support, and Base Unique Ingestion does not support them. MDI must be provisioned and enabled for the folder or chat Space. - Scanned-PDF accuracy, formula preservation, embedded-figure extraction and shared fixture outcomes were not measured. Older general ingestion limits differ from current production chat defaults. - formats — Which formats are accepted? [supported]: Chat supports PDF, DOCX, XLSX, PPTX, CSV, HTML, MD and TXT; PNG/JPEG when enabled per Space. Sources: unique-ai:unique-ai:files. - limits — What size and count limits apply per file and chat? [partial]: Production Chat defaults 512 MB/file, 30 files/upload. Code Execution has separate 100 MB and 10-file limits. Environment overrides and aggregate chat caps need tenant confirmation. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code. - ocr — Are scanned PDFs read? [partial]: The file-ingestion guide explicitly distinguishes methods: Base Unique Ingestion does not support image-based scanned PDFs, MDI supports them, and Docling has partial support. MDI must be provisioned and enabled for the folder or in the chat Space ingestion settings. Experimental image-content extraction and deprecated agentic ingestion are separate. No scanned-document fixture or accuracy measurement was run. Sources: unique-ai:unique-ai:file-ingestion-20261026. - spreadsheets — Are Excel tables read with structure intact? [partial]: Chat guide says default extraction can fail beyond 5,000 rows x 100 columns. General format guide lists 1,000 x 40; formulas and structure retention were not tested. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:filetypes. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Checked uploads force retrieval each turn. Large files contribute selected chunks, not necessarily the full file, and users do not see full coverage. Experimental full-PDF mode is separate. Sources: unique-ai:unique-ai:files. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code, unique-ai:unique-ai:filetypes, unique-ai:unique-ai:file-ingestion-20261026 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge folders persist and can be scoped to users/groups and bound to Spaces. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - persistent_collections — Can users keep document collections across chats? [supported]: Ingested content lives in knowledge-base folders/scopes beyond a chat. Sources: unique-ai:unique-ai:kbpermissions. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: ScopeAccess grants users or groups read/write access. A flat folder permission does not automatically grant subfolder access. Sources: unique-ai:unique-ai:kbpermissions. - size_limits — What are the collection limits? [unknown]: What are the collection limits? Unknown. Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - assistant_binding — Can collections be bound to an assistant? [supported]: Space Internal Search binds selected folders/files and further narrows user permissions. Sources: unique-ai:unique-ai:agent. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:agent ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Indexed SharePoint and Confluence are documented. Current architecture also names Google Drive/Salesforce, and release notes describe Salesforce/Yahoo Finance MCP connector dashboards; detailed entitlements and source permissions remain connector-specific. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Architecture labels and release examples do not prove that every source is enabled or included in every contract. - Future items on the roadmap are not promoted to current connector support. - No source-connection or two-user permission fixture was run. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online connector copies selected content with application consent and optional permission sync. Platform documentation also exposes Teams and Outlook MCP operator guides, but their exact contracted scope and OneDrive coverage were not verified. Sources: unique-ai:unique-ai:sharepoint. - google_workspace — Which Google sources are connected? [partial]: The current Platform Overview names Google Drive as a Knowledge Source feeding the Knowledge Base. It does not establish Gmail/Calendar coverage, a deployment guide, source consent scopes or inclusion in a particular customer contract. This is a documented architecture listing, not an observed enabled connector. Sources: unique-ai:unique-ai:platform-overview-20261026. - atlassian — Confluence and Jira? [partial]: Official Confluence connector supports Cloud and Data Center; Jira connector coverage was not established. Sources: unique-ai:unique-ai:confluence. - other_systems — Which other business systems? [partial]: Release 2026.40 names Salesforce and Yahoo Finance as examples in GA MCP connector dashboards that admins can list, enable and sign in to. Platform Overview also names Salesforce as a Knowledge Source. Exact origin implementation, connector rights, credentials and commercial inclusion vary by configured connector and contract. Sources: unique-ai:unique-ai:release40-20261026, unique-ai:unique-ai:platform-overview-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center sources are supported via REST. Generic file-share/database connector scope was not established. Sources: unique-ai:unique-ai:confluence. - connector_provider — Who builds and maintains each connector? [supported]: Unique publishes Kubernetes operator guides for SharePoint and Confluence; client IT supplies source credentials, consent, scope and deployment configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:platform-overview-20261026, unique-ai:unique-ai:release40-20261026 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint permission mirroring is optional; Confluence does not synchronise source permissions. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user restricted-document/revocation fixture was run. End-to-end revocation SLA and label enforcement are not established. Older folder-permissions documentation says SharePoint never mirrors permissions, conflicting with the newer optional-sync guide. - source_permissions_respected — Are source permissions enforced per user? [partial]: SharePoint content_and_permissions mirrors source rights, while content_only uses Unique scope rules. Confluence explicitly has no source-permission sync, so Unique folder access needs configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed content is filtered through Unique user/group ScopeAccess. This is not source-system live query-time enforcement. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:sharepoint. - revocation_delay — How quickly does a removed permission take effect? [partial]: SharePoint source rights refresh periodically, default scans 15 minutes. Internal gatekeeper changes usually propagate under one second but have no hard upper bound; degraded/missed broadcasts can leave old rules active. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:permissioncache. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins allow SharePoint sites/libraries and require a sync flag, Confluence labels, and Space KB restrictions. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:agent. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: July SharePoint connector explicitly excludes sensitivity/classification-level detection. Separately, release2026.42 documents experimental Purview-protected-file decryption using uploader rights, gated by MIP_DECRYPTION_ENABLED and Entra/operator changes. This is not proof of general label-policy enforcement. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:sharepoint. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:permissioncache, unique-ai:unique-ai:agent, unique-ai:unique-ai:release42 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint and Confluence copy content to Unique indexes on configurable scans, default every 15 minutes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No source-edit/delete fixture was run. Actual sync duration, strict deletion SLA and index/backup region per contract remain unverified. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connectors ingest documents/page attachments into the Unique knowledge base for RAG. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - sync_interval — How often does an index refresh? [supported]: Default 15-minute scan for both connectors; schedules are configurable. Real-time sync is explicitly not supported. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Diff processing detects deleted source files/pages and removes them on a sync run. A strict completion bound is not provided. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - index_location — Where is indexed content stored? [partial]: Hosted documents use Azure storage; embeddings Qdrant and search vectors on managed disks in the selected deployment. Exact per-client index region needs the MSA/architecture. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:keys. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:retention, unique-ai:unique-ai:keys ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents source-linked answers and reference limits, without a shared-corpus accuracy result. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - citations — Are answers linked to specific sources? [supported]: Chat retrieval cites sources; Conduct links source facts, with PDF/Word page-level references and other formats at document level. Generated files are not citation-linked or hallucination-checked. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Context Memory provides a private cross-chat user profile with edit and opt-out controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No authenticated memory fixture or permanent deletion test was run. The guide explicitly contradicts the settings deletion promise. - custom_instructions — Can users set persistent instructions? [partial]: Admins configure Space instructions; memory learns preferences. A separate persistent user-authored global instruction field was not established. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: One per-user profile is loaded across enabled spaces/chats and updated after answers; stored in a private unindexed KB folder. Sources: unique-ai:unique-ai:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users view/edit the profile and disable updates/loading. Docs explicitly say disabling does not delete the profile despite contrary settings text; a delete control is not established. Sources: unique-ai:unique-ai:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Release2026.42 makes Context Memory GA, with per-company enable/disable feature flag and per-Space activation. Users can opt out; Web Search combinations remain restricted by default. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory, unique-ai:unique-ai:release42 ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins configure Spaces with instructions, models, knowledge, tools, prompts and group access. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Assistant versioning, organisation-wide directory discovery and unrestricted end-user creation were not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Space setup includes model, instructions, knowledge sources and tools. Sources: unique-ai:unique-ai:agent. - creator_permissions — Can admins limit who creates them? [supported]: Space creation/management requires delegated role permissions; Can manage grants space configuration access. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Share through Access with people/groups as Can chat or Can manage. Sources: unique-ai:unique-ai:agent. - catalogue — Is there an internal assistant directory? [partial]: Space Management lists configured workspaces; a dedicated employee assistant-discovery directory is not described. Sources: unique-ai:unique-ai:agent. - prompt_library — Are shared prompt templates available? [supported]: Admins publish Suggested Prompts with a Space; users also have personal saved prompts. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:roles, unique-ai:unique-ai:chat ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in tools and beta MCP connectors are governed at organisation and Space levels. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted platform with MCP beta feature flag and configured connectors; add_ons=MCP entitlement and enablement per contract; deployment_mode=not specified; region=Tenant plus downstream connector/provider regions; os=not specified. Limitations: - Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - builtin_tools — Which tools are built in? [supported]: Internal search, web search, Deep Research and Code Execution are documented; Deep Research is experimental and code has model restrictions. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: MCP Tools for Spaces is beta, off until enabled for the organisation; connector admins and space managers can selectively expose connectors/tools. Sources: unique-ai:unique-ai:mcp. - tool_auth — Do tools act as the user or as a shared account? [supported]: MCP Hub maps user hub tokens to downstream per-user OAuth tokens; secrets are injected server-side. Sources: unique-ai:unique-ai:hub. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins restrict origin/connector/tool exposure. Conduct can pause for approve/deny of configured sensitive actions; it is not a universal confirmation guarantee. Sources: unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:mcp, unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search has provider/strategy controls; separate Deep Research is experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No search/report fixture was run. Exact query/provider regions, contract enablement and current Deep Research production readiness remain unverified. - web_search — Is web search available? [supported]: Real-time web search/read is a Space tool, with stable V1/V2 modes and experimental V3. Sources: unique-ai:unique-ai:websearch. - admin_toggle — Can admins disable it per organisation or group? [supported]: Admins enable/disable tools per Space shared with groups. Deep Research tools are configured separately; disabling ordinary Web Search is not a universal external-search block. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch. - search_provider — Which search provider handles queries, and where? [partial]: Configured engines can include Google, Bing, Brave, Jina, Tavily, Firecrawl, Vertex or custom API; query context can leave the tenant. Exact provider region must be set per contract. Sources: unique-ai:unique-ai:websearch. - deep_research — Is multi-step research with a report available? [supported]: Experimental tool creates multi-source research and reports. Unique engine can use internal/web sources; OpenAI-native engine requires direct OpenAI-hosted models and lacks internal sources/hosting-location control. Sources: unique-ai:unique-ai:deepresearch. - web_citations — Are web sources cited? [supported]: Web answers include source references; Deep Research documents citation-linked reports. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:deepresearch. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Recurring Scheduled Tasks run with user permissions; current release notes label the feature experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - workflow_builder — Is there a workflow or chain builder? [unknown]: Is there a workflow or chain builder? Unknown. No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: User guide labels recurring Chat/Conduct tasks beta and off by default; release2026.42 instead labels Scheduled Tasks experimental, off by default, enabled on request, and describes scheduling/eligibility fixes. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:scheduled. - event_triggers — Can external events start a workflow? [partial]: SDK documents webhook-driven applications, which require developer-hosted modules; a packaged no-code external-event builder was not established. Sources: unique-ai:unique-ai:sdk. - builder_audience — Is building aimed at business users, IT or developers? [partial]: Business users author recurring tasks in the UI or Conduct; developers host webhook-driven SDK modules. Availability and scheduling behaviour depend on deployed release. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Contract-enabled Conduct plans and executes multi-step tasks with visible tools and stop controls. Sensitive actions can ask for approval; separately enabled Experimental Scheduled Tasks offer automatic approval. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Conduct; version=Conduct 2026.40+; scheduling status/flags per 2026.42; plan=Contracted Unique AI platform; Conduct; Scheduled Tasks separately enabled per contract and feature flag availability and deployment/provider configuration depend on the customer agreement; add_ons=Conduct; optional Scheduled Tasks feature flag; deployment_mode=not specified; region=Configured tenant/models/tools; scheduled actions run with the owner permissions and configured approval policy; os=not specified. Limitations: - No agent fixture was run. Interactive sensitive-action approval and separately enabled unattended automatic approval are different execution modes. - Actual tools, entitlement, approval policy and deployed release depend on the customer contract/configuration. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Plans and executes Python/Bash, files, internal search and configured MCP tools in an autonomous workspace. Sources: unique-ai:unique-ai:conduct. - visible_steps — Are steps and tool calls shown? [supported]: Shows checklist, progress, code/tool inputs and outputs, and waiting/working indicators. Sources: unique-ai:unique-ai:conduct. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Conduct shows approve/deny for actions configured as sensitive. The separate Scheduled Tasks guide offers Automatic or Manual approval for Chat/Conduct unattended runs. Release 2026.42 labels scheduling Experimental and feature-flagged. Mandatory human approval of every side effect is therefore not established for all configured runs. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42. - stop_control — Can the user stop a running task? [supported]: Stop ends the turn within seconds; completed steps/files remain and interrupted work can be resumed. Sources: unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public API/Python SDK and Knowledge Base MCP are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique API and Python SDK, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted APIs and KB MCP deployment; model tracking requires enablement; add_ons=KB MCP and usage-tracking enablement per contract; deployment_mode=not specified; region=Configured deployment and external client region; os=not specified. Limitations: - No API/SDK fixture was run; complete endpoint catalogue, rate limits, budget enforcement and all-services audit parity remain unverified. - chat_api — Is there an API for chat and assistants? [partial]: SDK exposes the Unique public API, personal/app keys and webhook signatures. Exact endpoint entitlements/rate limits require the contracted deployment. Sources: unique-ai:unique-ai:sdk. - knowledge_api — Can documents be loaded through an API? [partial]: Connector/operator docs describe ingestion and knowledge APIs; public SDK supports platform integrations. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Feature-flagged model-use tracking covers public API/SDK/agentic and Azure SDK calls with company/user/app metadata. Complete budget/model-rule enforcement across all internal services is not established. Sources: unique-ai:unique-ai:api-usage. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Knowledge Base MCP lets external assistants search/read the Unique KB with the user permissions and admin scope restrictions. The documentation-only MCP endpoint is distinct. Sources: unique-ai:unique-ai:mcpkb. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:api-usage, unique-ai:unique-ai:mcpkb ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A web workspace is documented; native-client and managed-deployment coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - web — Is a full web client available? [supported]: Public documentation describes browser chat, Space Management and administration. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent ### 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 #### Unique AI 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A beta Translator Space translates Office files and text with configurable glossaries. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No translated-contract fixture was run. Exact engine/model, formality/de-CH controls, supported glossary language pairs and layout fidelity need verification. - document_translation — Can whole documents be translated with formatting kept? [partial]: DOCX, XLSX and PPTX document translation is documented, with possible layout disruption. PDF input is explicitly excluded in this Translator mode. Sources: unique-ai:unique-ai:translation. - translation_engine — Which engine translates? [partial]: Translator V2 is a standalone AI module configured with a model; no dedicated DeepL engine was established. Sources: unique-ai:unique-ai:translation. - glossaries — Are company glossaries supported? [supported]: Admins can configure glossary pre/postprocessing. Sources: unique-ai:unique-ai:translation. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Postprocessing can change regional spelling, exemplified by US-to-UK English. Formality or de-CH-specific support was not verified. Sources: unique-ai:unique-ai:translation. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat generates and iterates on text; no distinct proofreading/rewriting tool scope was established. Sources: unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:translation, unique-ai:unique-ai:chat ### 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 #### Unique AI 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Voice dictation is documented with Azure Speech prerequisites; recording use is separately described in the DPA. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - dictation — Can users dictate prompts? [supported]: Microphone transcribes into the prompt field, with audio discarded after live transcription. Requires configured Azure AI Speech Services; EN/DE/FR/IT are listed. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - meeting_summaries — Are meetings transcribed and summarised? [partial]: DPA recording use case covers audio/transcripts, optional video and GPT summaries/follow-up emails. This is a contracted recording use case, not proof every Chat plan includes meeting capture. Sources: unique-ai:unique-ai:dpa. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user, unique-ai:unique-ai:dpa ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enabled Chat Code Execution and Conduct can analyse data and produce downloadable files. Selected KB documents can be preloaded into the code container; ordinary unrestricted KB retrieval is separate. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct; version=not specified; plan=Contracted Unique AI platform; Chat Code Execution or Conduct; model compatibility and flags configured separately availability and deployment/provider configuration depend on the customer agreement; add_ons=Code Execution / Conduct enablement per contract; deployment_mode=not specified; region=Documented Azure code container for the Azure route; LiteLLM execution region unverified; Conduct sandbox per contracted deployment; os=not specified. Limitations: - Selected admin-preloaded KB files are supported; this is not arbitrary sandbox retrieval of the whole Knowledge Base. - The page lists Azure and LiteLLM-compatible model IDs but describes Azure-specific container controls. Actual provider execution routing and entitlement require deployment configuration. - No generated-file quality/editability fixture was run. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: Chat Code Execution runs Python for CSV/XLSX analysis. The general limitation says KB files are not directly accessible, but admin configuration additionalUploadedDocuments preloads selected KB content_ids, for example templates, into the container. The documented Azure route has no outbound internet/runtime installs and a ten-file/100 MB per-file limit. The compatibility table also lists LiteLLM OpenAI models; that does not establish the same execution-region controls for every route. Conduct separately runs Python/Bash. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - charts — Can it produce charts? [supported]: The Code Execution guide documents matplotlib PNG/SVG and inline charts. Its described Azure container lacks kaleido, limiting Plotly static exports; no statement about every alternative runtime is inferred. Sources: unique-ai:unique-ai:review2-code. - office_file_output — Can it create Word, Excel or PowerPoint files? [partial]: The guide documents DOCX/XLSX generation and PPTX from supplied templates, with variable presentation quality. KB templates can be supplied by the admin preload setting. Generated files remain outside Conduct source-citation/hallucination checks. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: No dedicated canvas editor or editable spreadsheet-to-PowerPoint fixture result was established. Downloadable file generation does not establish in-product canvas editing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Chats is GA in release 2026.42, with company settings and a per-Space toggle. Simultaneous group conversation and recipient source-permission handling remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=2026.42 or later; plan=Contracted Unique AI platform; Shared Chats and Spaces; sharing settings and deployed release availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A shared conversation is not evidence of simultaneous group participation or recipient access to every source. - No cross-group shared-chat permission fixture was run. - share_chats — Can chats be shared inside the organisation? [supported]: Release 2026.42 makes whole-chat sharing GA and on by default for companies, while each Space still needs its Shared chat toggle. Explicit existing company preferences are preserved. Owners can search recipients and copy share links. Sources: unique-ai:unique-ai:review2-release42. - team_spaces — Are shared projects or workspaces available? [partial]: Admins publish shared Spaces with people/group Can chat and Can manage roles. These share agent configuration/knowledge, not necessarily a conversation. Sources: unique-ai:unique-ai:agent. - group_chat — Can several people chat together with the AI? [unknown]: Whole-chat sharing is documented. A simultaneous multi-person AI conversation, collaborative commenting or live co-editing mode was not established or tested. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Whole-chat sharing is documented, but whether a recipient can open every cited source or inherits source permissions was not established in the retrieved release/Space documentation. No cross-group fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:review2-release42 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current release notes document German, French and Swiss German UI language behaviour; completeness and accessibility remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Release notes describe locale fixes, not a full UI audit or conformance statement. No authenticated UI was reviewed. - ui_languages — Which UI languages are offered? [partial]: Release2026.42 describes German/French label translations and selected-language login/notices/errors/side-panels, including Swiss German spellings. A complete language matrix was not provided. Sources: unique-ai:unique-ai:release42. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:release42 ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Zitadel supports Entra OIDC, generic OIDC and SAML across documented deployment types. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Setup guides explicitly cover Entra ID OIDC, generic OIDC and SAML, including IdP metadata for closed networks. Sources: unique-ai:unique-ai:sso. - sso_plan — Which plan includes SSO? [partial]: Compliance matrix lists SSO for multi-tenant, single-tenant, client-hosted and on-premise modes. Numeric tariff prerequisites are not public. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - mfa — Can MFA be enforced? [partial]: Hosted compliance matrix lists enforced 2FA; SSO setup delegates authentication to the external IdP. Exact customer MFA policy controls need verification. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SCIM, group sync and SAML automatic user creation are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - scim — Is SCIM provisioning supported? [supported]: Unique supplies SCIM URL/key for IdP synchronisation, with an Entra guide. Sources: unique-ai:unique-ai:scim. - group_sync — Are identity-provider groups synced? [supported]: SCIM syncs users/groups; SSO group claims can also sync on login, requiring optional Graph group permission/admin consent. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso. - jit_provisioning — Are users created at first login? [supported]: SAML setup explicitly enables automatic creation/update and account creation. Sources: unique-ai:unique-ai:sso. - deprovisioning — What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - seat_assignment — Can admins assign and reclaim seats? [unknown]: Can admins assign and reclaim seats? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Four role/access layers separate identity, feature, Space and knowledge controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user disabled-feature test was run. Full cross-Space per-group controls and legal-entity separation require contracted setup. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: IAM owner/viewer/org-manager plus Unique application roles delegate administration; Space Can manage grants local configuration. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - groups — Can permissions be set per group? [supported]: Users/groups receive Space and ScopeAccess permissions. Sources: unique-ai:unique-ai:roles. - feature_toggles — Which features can be switched on or off per group? [partial]: Tools and upload settings are configured per Space, then Spaces shared to groups. A global group-feature matrix is not established. Sources: unique-ai:unique-ai:agent. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Compliance docs describe workspace isolation for departments/client engagements. Multi-subsidiary contractual/billing boundaries are not specified. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent, unique-ai:unique-ai:compliance ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Analytics exports cover adoption, assistants, models and tools with privacy controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact group breakdowns, every dashboard entitlement and suppression beyond exported identifiers need verification. - adoption_dashboard — Is there an adoption dashboard? [supported]: Reports cover daily/weekly/monthly active users, assistant interactions and document reference statistics. Sources: unique-ai:unique-ai:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Detailed exports include assistant/model, tool calls, skills, cost and tokens. Group and cost-centre breakdowns were not established. Sources: unique-ai:unique-ai:analytics. - export — Can usage data be exported? [supported]: Admins request and download reports with date/assistant filtering; model usage supports CSV. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Environment flags anonymise export emails, optionally with stable pseudonyms; detailed exports respect organisation settings. Sources: unique-ai:unique-ai:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Off-by-default beta cost management offers estimated spend and enforced daily caps. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No small-budget fixture was run. Estimates are configurable cost-sheet values, not a public billing tariff; cost-centre and full invoice reconciliation remain gaps. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Tracks estimated USD/input/output tokens by user, model, assistant/app; a billed invoice reconciliation or group cost view is not established. Sources: unique-ai:unique-ai:cost. - budgets — Can budgets be set per user or group? [supported]: Company fallback, group and user daily USD caps; user override first, highest applicable group limit next. Sources: unique-ai:unique-ai:cost. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Before the next call, accumulated daily spend at cap blocks the model call; resets at local midnight. Docs warn caps may break background-job SLAs. Sources: unique-ai:unique-ai:cost. - chargeback — Can costs be exported per cost centre? [partial]: CSV exports contain user/app/assistant/model/token/cost metadata, with privacy controls. Cost-centre attribution is not documented. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:cost ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial API audit events, detailed interaction exports and Single-Tenant security-event streaming are documented. A single authoritative retention period for the customer's audit records is not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Audit Logs, Analytics and Single-Tenant Security Events Export availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE for the contracted Single-Tenant deployment; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - API security-event records, detailed prompt/answer interaction exports, SEE replay and generic operational logging are separate sources/data flows. Their public retention figures are not substituted for each other. - No executed customer retention override or legal-hold/eDiscovery fixture was inspected. - admin_events — Are admin and security events logged? [supported]: Event logging covers privileged public/internal API interactions; many self-identity/chat operations are excluded. Basic mode is default; verbose content mode is opt-in. Sources: unique-ai:unique-ai:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Detailed chat interaction exports contain prompts/answers for authorised admins and respect configured privacy. Verbose event logging can include CID but is discouraged. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:audit. - siem_export — Can logs stream to a SIEM or be exported? [supported]: SEE offers Single-Tenant Azure Defender and Activity events via Event Hub to Sentinel/Splunk, seven-day replay. It excludes tenant-level Entra events and is not a prompt-content audit stream. Sources: unique-ai:unique-ai:security-export. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: No public legal-hold/eDiscovery workflow or complete event-log immutability design was established. - log_retention — How long are logs kept? [unknown]: Different sources describe different record scopes. The API event guide gives basic-mode MT events 90 days and ST events five years, including post-termination ST retention. DPA 3.15 says audit logs ten years without mapping its audit-log category to those API events. The generic hosted policy says logging up to one year after termination or longer if legally required. SEE has a separate seven-day Event Hub replay window, not the lifetime of all audit records. No customer agreement or authoritative record-class/precedence mapping was retrieved; the applicable audit retention period is unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-audit, unique-ai:unique-ai:analytics, unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-retention ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial DLP is primarily customer infrastructure and integration; it is not a verified default native redaction feature. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Documents customer HTTPS proxy/interceptor DLP and post-chat Analytics API scanning; Compliance Layer says pre-LLM calls can be implemented. Multi-Tenant matrix explicitly excludes DLP integration. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. - filter_location — Where does filtering run? [partial]: Proxy inspection runs in customer egress infrastructure; Analytics API supports customer post-chat inspection. A deployment-specific pre-LLM service may be implemented. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space instructions/banners and customer-specific login terms are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins set Space-level system instructions and persistent banners. A mandatory organisation-wide instruction hierarchy is not specified. Sources: unique-ai:unique-ai:agent. - usage_notice — Can users be required to accept a usage policy? [supported]: First login requires terms acceptance; custom terms/editing/deactivation depend on MSA eligibility and admin GraphQL role. Acceptance/version data can be exported. Sources: unique-ai:unique-ai:policy. - content_filters — Are content filters configurable? [partial]: Single-tenant Azure prompts pass through Azure content filters; Compliance matrix marks hosted modes with content filtering. Customer filter configuration and scope remain unspecified. Sources: unique-ai:unique-ai:single, unique-ai:unique-ai:compliance. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:policy, unique-ai:unique-ai:single, unique-ai:unique-ai:compliance ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Documentation offers CH North multitenant hosting and selectable single/customer-hosted regions, with model processing configured separately. The customer's binding residency schedule and full backup/log/support map remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted or customer-hosted platform; separately selected model/tool routes availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Documented options: CH North hosted MT; selected ST/customer region; provider/SKU/tool inference region separately configured; actual contracted boundaries unverified; os=not specified. Limitations: - Available architecture/region options are not a signed residency schedule. Storage, model inference, backups/logs, support access and external tools must be scoped separately. - DPA CH-storage and chosen-location statements are not reconciled by silently treating one as the current customer contract. - storage_region — Where are chats, files and indexes stored? [partial]: The deployment matrix documents Azure Switzerland North for hosted multitenant and chosen supported regions for Single Tenant. Tenant storage includes PostgreSQL, documents and vector data. These are configuration options; no customer-specific storage schedule was inspected. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-keys. - inference_region — Where do model calls run, per provider? [partial]: The model catalogue separates Azure regional/Data Zone/Global SKUs and external provider routes, with some Swiss deployments and some global-only services. Actual selected provider/SKU/tool routing must be configured for the contracted deployment. CH storage is not a verified CH inference guarantee. Sources: unique-ai:unique-ai:review2-models, unique-ai:unique-ai:deepresearch. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Single-tenant backup resources follow the configured landing-zone design and SEE sends events to a separately selected consumer region. An exhaustive physical replica/backup/log/telemetry country matrix was not retrieved. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - support_access_region — From where can vendor staff access data? [unknown]: The public DPA gives need-to-know access controls and customer-controlled on-premises support, but not an exhaustive physical country list for vendor/subprocessor support access. Office addresses are not used as support-access locations. - swiss_hosting — Is Swiss hosting available? [partial]: CH North is a documented hosted-MT option, and selected-region ST can be Swiss. This records available deployment options, not the customer's end-to-end storage/inference/support contract. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models. - residency_plan — Which plan or option provides residency? [unknown]: DPA 6.1 says storage stays in Switzerland, while its Appendix A allows a client-chosen Microsoft location and current platform docs offer selected jurisdictions. No current customer MSA, precedence clause or deployment schedule was inspected to resolve the binding scope. A contractual CH-wide residency commitment is not asserted. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:security-export, unique-ai:unique-ai:deepresearch ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current docs offer shared SaaS, dedicated instances, customer cloud and customer-operated on-premise/air-gapped modes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No deployed tenant was inspected. Seat/contract thresholds and an exhaustive offline feature-parity matrix remain unknown; docs establish an option, not universal entitlement. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Installation overview lists Multi Tenant on Unique cloud. Sources: unique-ai:unique-ai:install. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Unique-managed Single Tenant has its own Azure landing zone separated from other customers. Minimum seats/contract value are unpublished. Sources: unique-ai:unique-ai:single. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Operator guide documents deployment in customer cloud account with Unique software/support; cloud-specific rollout is contracted. Sources: unique-ai:unique-ai:operators. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Customer provisions/manages infrastructure on own premises, may run own models and can exclude Unique access. Minimum commitment not published. Sources: unique-ai:unique-ai:onpremsecurity. - air_gapped — Can it run without internet access? [partial]: IT-operator overview explicitly offers a full air-gapped on-premise deployment. Compatibility and feature limitations depend on customer setup. Sources: unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Compliance matrix separates SSO/content filter/DLP/PAM/key capabilities by mode. Azure Chat Code Execution/voice and external web/providers require those services and cannot be assumed in an isolated environment. Sources: unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:install, unique-ai:unique-ai:single, unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Azure documentation says no model training and disabled Microsoft prompt storage/human review; other provider routes require separate terms. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No signed Azure amendment was inspected. Retention and review conditions for Anthropic, Gemini, Together, xAI and direct OpenAI research remain unverified; do not generalise the Azure-only policy. - vendor_training — Does the vendor train on customer content? [supported]: Hosted retention policy says no customer data is used for AI/neural-network training. Public terms allow service development and anonymised metadata use; that is not a blanket prohibition of all secondary processing. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms. - provider_training — Do model providers train on it under this product's contracts? [partial]: Hosted Azure deployment is separate from public OpenAI and training is excluded. Other catalogue providers/direct OpenAI research need their applicable customer terms. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For hosted Azure OpenAI, documents/prompts/answers process in memory only, with logging/human-review opt-out. Ordinary application chats persist in Unique databases. Sources: unique-ai:unique-ai:retention. - zero_retention — Is zero data retention available, and on which plan? [partial]: Hosted Azure model calls use no provider content storage per opt-out; this is not zero retention of Unique application history, logs or other provider routes. Sources: unique-ai:unique-ai:retention. - human_review — Can provider staff review content? [partial]: Hosted Azure guide says Microsoft prompt/response human review is disabled. Vendor staff need-to-know access and alternate model-provider review conditions are separate. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:dpa ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat content clearing, chat uploads, KB documents, contract-end content deletion, recoverable files, backups and audit records have separate policies. No common purge deadline is established for all copies. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Chat, Knowledge Base and hosted retention configuration; customer-hosted policy separately controlled availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted storage/provider region; hosted-policy timings not extended to every customer-hosted system; os=not specified. Limitations: - Hosted content policy expressly permits contract-specific variation. Its timings do not define API/DPA audit-record retention. - No tenant configuration, customer MSA, final backup purge or external-provider deletion fixture was inspected. - default_retention — What is retained and for how long by default? [partial]: The chat-upload guide describes an admin-configured expiry, typically two weeks, for chat uploads. Hosted policy lists no minimum for KB/blob/vector/database content. Neither figure defines audit-event retention or proves a tenant's configured default. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:review2-retention. - admin_retention — Can admins set retention periods? [supported]: DATA_RETENTION_IN_DAYS drives the daily midnight chat-content clearing job; unset/zero disables it. This clears the content categories named by the redaction guide, not all uploads, KB, external tool records or audit events. Sources: unique-ai:unique-ai:redaction. - user_deletion — Can users delete their chats and files permanently? [partial]: The redaction guide says deleting a chat removes its Unique chat-content copy and marks the chat record deleted. Separate upload, KB, external-tool, soft-delete, backup and audit policies are not collapsed into that action. Sources: unique-ai:unique-ai:redaction. - contract_end_deletion — What is deleted at contract end, and when? [partial]: For Unique-hosted ordinary content, the published policy states a standard 30-day post-termination period unless the customer contract differs. It separately describes recoverable files for 30 days after deletion and database backups for two further weeks. DPA 6.1 requires return/deletion subject to legal record-keeping. Audit-log classes and their contractual lifetime remain unknown under ADM-06; this is not a deadline for deletion of every copy. Sources: unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:redaction, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The dated public DPA lists Microsoft, but a complete applicable current subprocessor/country schedule for all contracted model/tool routes was not retrieved. A technical provider catalogue is not substituted for that legal schedule. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; current platform infrastructure and enabled model/tool integrations availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Actual customer provider/country/transfer schedule unverified; os=not specified. Limitations: - The provider catalogue establishes technical choices, not each party's processor role or the legal schedule for a customer contract. - No sales contact, executed current MSA or nonpublic schedule was obtained. - subprocessor_list — Is a dated sub-processor list published? [unknown]: The July 2025 public DPA Appendix A lists Microsoft for infrastructure, Cognitive/Azure OpenAI and email. The current technical catalogue offers other provider/tool routes, which may have different contractual roles. No applicable complete current legal schedule or executed customer supplement was retrieved; the Microsoft-only list is not presented as complete. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: DPA Appendix A names CH or a client-chosen Microsoft location; technical model routes separately include regional and global processing. A complete current legal provider/country and support-access schedule for the chosen deployment was not retrieved. - change_notification — Are customers notified of sub-processor changes? [unknown]: No applicable current processor-change notification/objection clause for the customer's full provider schedule was retrieved from the DPA or current contract-access documentation. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The current contact page identifies Unique AI AG in Switzerland and regional entities. The public DPA uses Unique AG. Ultimate parent/beneficial-owner jurisdiction and a customer-specific contracting entity were not independently established. Sources: unique-ai:unique-ai:contact, unique-ai:unique-ai:review2-dpa. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: No complete customer-content transfer-instrument mapping per non-CH/EU provider was retrieved. The website visitor privacy policy is not substituted for customer-content terms. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: No current customer-content government-request/transparency policy was retrieved for the complete contracted provider chain. General banking/DPA assurances do not establish such a policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:contact ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public DPA and finance-specific compliance material are available; actual contractual amendments were not inspected. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - DPA negotiability and signed sector amendments, product-specific EU AI Act roles and exact sector assurance scope remain unverified. This records materials, not a compliance verdict. - dpa — Is a DPA available, and is it negotiable? [partial]: DPA accepts click-through/use or signature and defines Unique as processor for hosted MT/ST. Negotiability is not specified. Sources: unique-ai:unique-ai:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: DPA addresses GDPR, Swiss FDPIC oversight and MSA-defined laws; Compliance Layer identifies nFDAP/Swiss M329 amendment. Exact signed revDSG/GDPR scope requires MSA. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance. - governing_law — Which law and court govern the contract? [supported]: DPA 7 specifies Swiss substantive law and Zürich 1 courts unless mandatory GDPR/MSA otherwise. Public ToS similarly names Swiss law. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Trust centre describes per-use-case conformity assessments; ISO42001 and AI governance material are public. A complete provider/deployer AI Act technical file is not established. Sources: unique-ai:unique-ai:trust, unique-ai:unique-ai:compliance. - sector_materials — Are FINMA or other sector materials provided? [partial]: Compliance Layer names Microsoft M453 FINMA audit-rights amendment, M744 professional/banking secrecy and M329 CH-DPA for Unique-hosted deployments. Actual annexes and current signed scope are not public. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance, unique-ai:unique-ai:terms, unique-ai:unique-ai:trust ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial New public 2026 ATTESTA renewals establish ISO27001 and ISO9001 validity to 31 May 2029; the public TÜV SÜD ISO42001 certificate runs to 6 March 2028. SOC2 Type2 is vendor-documented, with full report evidence NDA-gated. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=ATTESTA 10 June 2026 renewals; TÜV SÜD 7 March 2025 certificate; plan=Contracted Unique AI platform; platform assurance; certificates cover the named legal entity and stated scopes, not every module/provider availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Certificates name Unique AG, Zurich, Switzerland; module/provider coverage depends on the stated audit scope; os=not specified. Limitations: - Current ISO27001/9001 evidence is the 2026 renewal plus matching register entries; the stale website-linked PDF is not used to deny current certification. - SOC chronology and access process are vendor-documented, not a reviewed independent SOC report. Certificate scopes are entity-specific and not a universal module/provider assurance. - iso_27001 — ISO 27001 with scope and validity? [supported]: Inspected the 2026 ATTESTA Schweizer Zertifizierungsgesellschaft AG ISO27001:2022 certificate for Unique AG, registration 223-06-018.I. It covers software development/operation/trading/distribution and IT services, is issued 10 June 2026 after 4 June surveillance and expires 31 May 2029. The certificate-linked public register matches the number and expiry. The marketing-linked 2025 PDF is an older artifact, not the current renewal. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs. - soc2 — SOC 2 type, period and covered service? [partial]: The dedicated SOC page documents Type1 in December 2023 followed by Type2 in January 2025. This explains the historical Type1 references rather than proving an ongoing Type1-only state. Current Type2 status is a vendor claim; the auditor, actual report period and service/control scope were not inspected because the full report is NDA-gated. Sources: unique-ai:unique-ai:review2-soc. - c5 — BSI C5 attestation? [unknown]: No public BSI C5 attestation was retrieved from the certification pages/trust centre or targeted first-party search. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: Inspected ATTESTA ISO9001:2015 renewal 223-06-017.Q for the same Unique AG software/IT scope, expiring 31 May 2029, matched in the public register. Separately inspected TÜV SÜD South Asia ISO42001:2023 certificate 99 420 00001, valid 7 March 2025 to 6 March 2028, for development/deployment of financial-services SaaS using foundation or client models. Current full ISAE/FINMA report scope was not inspected. Sources: unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:iso42001. - report_access — How can customers obtain reports? [supported]: The ISO documentation provides public certificate downloads. It says the ISO27001 Statement of Applicability requires a valid NDA. The dedicated SOC page likewise makes the audit report/certificate available on request after NDA. No NDA or sales request was made. Sources: unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:review2-soc. - pentest — Are independent penetration test summaries available? [partial]: The public DPA describes internal/external security testing and the trust page describes tests/bug bounty. An independent penetration-test report, current scope or summary was not inspected. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:iso42001, unique-ai:unique-ai:review2-soc, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment guides document encryption, isolated Single Tenant resources and optional IP filtering. Exact current MT PMK/CMK/HSM configuration and key sizes are not established across the conflicting pages. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted MT/ST encryption and optional customer-controlled self-hosting availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted Azure tenant/storage/backup region; actual key-vault/HSM location unverified; os=not specified. Limitations: - No exact RSA/HSM key size or actual MT PMK/CMK design is asserted. A customer-specific deployment/key diagram and key-vault region were not inspected. - Customer-generated imported keys held by Unique do not establish customer-exclusive key custody; full control is a separate self-hosting option. - encryption_at_rest — Is data encrypted at rest? [partial]: The compliance matrix documents encryption at rest and in transit across deployment options, with AES256/TLS1.2+ in its controls text. No exact current RSA key size is asserted: the ST architecture says 2048-bit RSA-HSM while the hosted retention page says 4096-bit. An implementation-specific key design was not retrieved. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: The infrastructure key guide allows a customer-generated key to be imported for a Unique-hosted Single Tenant, with Unique holding/managing it. It directs clients needing exclusive control of all storage keys to customer self-hosting. This is not HYOK or exclusive customer custody in Unique hosting. Actual MT PMK/CMK/HSM configuration is unknown because the key guide and hosted retention matrix disagree. Sources: unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-retention. - private_networking — Is private connectivity or IP restriction available? [partial]: The Single-Tenant WAF supports optional IP blocking. The separate SEE consumer endpoint is public TLS with optional allow-list and no standard private endpoint/peering. These are distinct scopes; other private-link options for the customer deployment were not verified. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - tenant_isolation — How are customers separated in shared SaaS? [supported]: The Single-Tenant architecture describes a separate customer landing zone under Unique's subscription, isolating its storage/processing from other customers. This documents that ST architecture, not the isolation configuration of every hosted or customer-managed instance. Sources: unique-ai:unique-ai:review2-single. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:security-export ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents general staff/external-party access controls and customer-controlled on-premises access. A professional-secrecy undertaking under § 203 StGB or Art. 321 StGB, its subprocessor flow-down and qualifying plan/add-on remain unverified. Financial-sector banking-secrecy amendments are recorded separately under DATA-06. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI; profession-specific eligibility and fees unpublished; add_ons=none stated; deployment_mode=not specified; region=Contracted hosting jurisdiction; customer-controlled on-premises access described separately from Unique-hosted access; os=not specified. Limitations: - No executed professional-secrecy undertaking or § 203 / Art. 321 contract was inspected. General DPA confidentiality is not treated as such an undertaking. - The M744 professional-secrecy wording appears in a banking-secrecy/financial-services framework; no inference is made to lawyers, doctors, auditors or tax advisers. - Customer-controlled on-premises access does not establish the same access conditions for Unique-hosted deployments or all model-provider routes. Full plaintext-access mapping remains unknown. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public Unique AI-specific § 203 StGB or Art. 321 StGB secrecy undertaking covering staff was located in the DPA, compliance documentation or targeted first-party search on 21 October 2026. The DPA confidentiality commitment alone does not establish a professional-secrecy undertaking. No executed or negotiated customer agreement was inspected. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The DPA says employees, contractual subprocessors and other service providers are bound to confidentiality of sensitive information. A professional-secrecy-specific obligation extending through the subprocessor/model-provider chain was not verified. The Microsoft M744 banking-secrecy amendment mentioned in the financial-services framework is not counted as evidence of § 203 / Art. 321 coverage for professional secrecy holders. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No qualifying professional-secrecy plan, dedicated offering, add-on tariff or named eligibility rule was located. The documented financial-services amendments and general deployment choices do not establish a separate § 203 / Art. 321 offering. Contract-specific terms and fees remain unknown. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: DPA Appendix B permits employees or external parties access to personal/confidential information on a need-to-know basis. For on-premises support, customers control remote connections and Unique staff cannot access a customer system without customer knowledge or full active participation. The on-premises architecture also allows operation without any Unique access under customer control. These sources do not exhaustively identify plaintext access at each hosted subprocessor/model provider or profession-specific access conditions. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA and on-premises architecture describe confidentiality and access controls, but no profession-specific secrecy template or professional-body guidance was located. The compliance page describes Microsoft M453/M744/M329 in a financial-services context; those banking/FINMA disclosures belong to DATA-06 and do not establish the missing professional-secrecy contract. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance ## 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Applicable current platform pricing unit, list tariff, included usage and overages remain unknown. A separately documented Single-Tenant SEE consumption/engineering charge is retained; legacy sales-conversation terms are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform subscription and separately enabled Single-Tenant SEE availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE scope only where contracted; deployment_mode=not specified; region=Vendor currency and applicable invoicing terms not established for the platform; SEE guide separately quotes indicative CHF consumption; os=not specified. Limitations: - The SEE cost finding is scoped only to that Single-Tenant integration. It does not price the platform subscription or all modules. - The 2023 sales-conversation ToS is excluded as evidence of current Unique AI commercial terms; no sales quote or private contract was requested. - pricing_unit — What is the pricing unit? [unknown]: No applicable current platform MSA/order form or tariff establishing seat, active-user, platform or usage pricing units was retrieved. The public 18 October 2023 ToS defines a sales-conversation intelligence service, so its subscription/Order Form clauses are not applied to current Unique AI. - list_prices — What are list prices per plan, with date and currency? [unknown]: No applicable current platform list tariff, tier names or primary invoicing currency was retrieved from platform/contract documentation or targeted first-party search. - included_usage — What usage is included? [unknown]: No applicable current platform agreement specifying included model tokens, storage or module allowances was publicly retrieved. - add_ons — Which features cost extra? [partial]: Single-Tenant SEE passes through Azure consumption without markup; guide observes CHF20-50/month/environment, not a fixed quote, with initial engineering at agreed rates. Other module charges are unpublished. Sources: unique-ai:unique-ai:security-export. - overage — What do usage beyond limits and premium models cost? [unknown]: No applicable current platform overage or premium-model sales tariff was retrieved. Cost-management model estimates are not substituted for a customer sales tariff. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. Public enterprise pricing is insufficient for the required 200/1,000/5,000-user annual totals. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - variable_share — Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - unknown_parts — Which costs could not be priced? [supported]: Subscription/order pricing, usage billing, provider contracts, deployment operation, connectors, execution, training and support charges are not publicly priced. SEE consumption example alone cannot price the platform. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export, unique-ai:unique-ai:ecb-fx ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public route is demo/evaluation by arrangement; self-service trial conditions were not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Current platform CTA requests a demo; public baseline ToS says Unique may offer evaluation at its discretion. This does not prove every meaningful evaluation is sales-gated. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai: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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current platform minimums, term, cancellation and local invoicing remain unknown because the applicable agreement was not publicly retrieved. Current documentation makes legal contracts available on request; legacy sales-conversation renewal clauses are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform commercial agreement; actual agreement not inspected availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CHF/EUR invoicing and legal entity for a specific platform contract unverified; os=not specified. Limitations: - No current customer agreement or sales quote was requested. Contract availability on request does not establish price, term or cancellation conditions. - minimum_commitment — What seat or spend minimum applies? [unknown]: No current platform seat/spend minimum was established from the public contract-access and platform pages. - contract_length — What contract lengths are offered? [unknown]: No applicable current Unique AI agreement establishing subscription duration, renewal term or notice period was retrieved. The 2023 sales-conversation service term is not applied. - cancellation — How can the contract be cancelled or reduced? [unknown]: Current Unique AI cancellation, refund, seat-reduction and nonrenewal rules were not retrieved. The 30-day renewal notice and quantity restrictions from the sales-conversation ToS are excluded. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: CHF/EUR invoice currency, billing entity and local invoicing eligibility for a current platform contract were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: The current governance framework says legal contracts and end-user T&Cs are available on request. No applicable public platform list tariff or complete commercial agreement was retrieved. This records an access/transparency gap, not a price or a customer-specific commitment. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public reference repository uses restricted Unique License v1, while the Python SDK has an explicit MIT exception. Hosted platform component terms and enterprise-edition boundaries remain unverified. Availability: source-only Delivery: native Scope: surfaces=Unique API and Python SDK, Unique AI Chat and administration; version=Unique-AG/ai commit afa596c9b4b0231895ff70f44029a9a525f746e9; plan=Public reference-code and Python SDK licences; current contracted Unique AI client/server/connector agreement remains unavailable; add_ons=none stated; deployment_mode=not specified; region=Public Unique License v1 specifies Swiss law and Zurich venue; this is not a hosted-service residency claim; os=not specified. Limitations: - The MIT exception applies to unique_sdk, not every directory or the hosted platform. - Root reference-code terms are not substituted for customer platform branding, seat or enterprise-edition conditions. - The 2023 sales-conversation service ToS remains excluded. - licence_type — Which licence applies to each component? [partial]: The public Unique-AG/ai repository at afa596c9b4b0231895ff70f44029a9a525f746e9 defaults to Unique License v1, which restricts commercial use, distribution and modification without written approval. The unique_sdk directory is an explicit MIT exception, confirmed by LICENSE and package metadata. This is a component-level source-available/MIT distinction; current hosted client/server/connector customer terms and a full dependency inventory remain unknown. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Unique License v1 requires written approval to modify or redistribute covered reference code; the MIT SDK exception requires retention of copyright/licence notices. A current hosted-platform white-label/logo-removal obligation or a numerical user cap is not established by these public component licences. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Current closed/open enterprise-edition boundaries were not established from an applicable component licence inventory. Public SDK/repository availability is not proof of the whole platform licence. Rechecked 2026-10-26 in Unique AI governance framework: contract access, Terms and Conditions Administration. No current customer MSA, quote, private schedule or gated contract was requested. The differently scoped 2023 sales-conversation ToS remains excluded. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin, unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026, unique-ai:unique-ai:review2-governance-20261026, unique-ai:unique-ai:review2-terms-admin-20261026 ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorised content/report export exists, but full assistant/knowledge portability is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - chat_export — Can admins export all chats? [partial]: Detailed interaction export includes user prompts/answers over a chosen period with privacy settings. Completeness across files, agent state and all historical chats was not tested. Sources: unique-ai:unique-ai:analytics. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - export_format — Are formats documented and machine-readable? [partial]: Model usage CSV and detailed analytics exports are documented. DPA promises return in existing format, not a universal reusable assistant/knowledge format. Sources: unique-ai:unique-ai:cost, unique-ai:unique-ai:analytics, unique-ai:unique-ai:dpa. - post_termination_window — How long can data be retrieved after termination? [partial]: Baseline ToS 11.4 offers recorded-call download/export on written request within 30 days; that does not establish a chat/assistant/KB exit window. DPA return is within reasonable time. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost, unique-ai:unique-ai:dpa, unique-ai:unique-ai: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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise support and a public multitenant status page are available; response times are contracted. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - support_channels — Which support channels are available on each plan? [supported]: Enterprise email and three-layer dedicated support escalation through customer team, CS and engineering. Hours/responses depend on SLA; extended-hours contract is extra. Sources: unique-ai:unique-ai:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Unique AI AG lists Zürich, Unique Germany GmbH Berlin, plus UK/US/Singapore entities. Sources: unique-ai:unique-ai:contact. - uptime_sla — Is there an uptime SLA with credits? [partial]: Support docs defer hours and response times to SLA contract; no public uptime/credit schedule was obtained. Baseline terms only promise commercially reasonable availability efforts. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:terms. - status_page — Is there a public status page with history? [supported]: status.prod.unique.app publicly shows component/uptime history. Support docs scope it to multitenant accounts, not every dedicated environment. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:contact, unique-ai:unique-ai:terms, unique-ai:unique-ai:status ### 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 #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor markets forward-deployed delivery and structured training; inclusion and cost remain unpriced. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - onboarding_service — Is guided onboarding included? [partial]: Homepage markets embedded forward-deployed experts helping business/IT ship use cases; exact licence-included rollout scope is contracted. Sources: unique-ai:unique-ai:homepage. - user_training — Is end-user training offered, in which languages? [partial]: Vendor homepage describes structured programmes teaching users to use/build/scale; current languages and course entitlement are not specified. Sources: unique-ai:unique-ai:homepage. - use_case_library — Are role-based use cases and templates provided? [supported]: Public documentation has finance-role workflows, Chat/Conduct guidance, configurable Suggested Prompts and agent examples. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:homepage, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct ## 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 ### unique-ai:unique-ai:models Unique LLM availability overview. Lists contract-dependent provider/model availability, region SKUs, dated additions and retirements; CH Phoeniqs remains QA-only. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Per-client availability; Azure/LiteLLM/Phoeniqs matrices; Recent changes - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:agent Unique AI space configuration. Documents admin instructions, configured model/tools, knowledge binding, prompts and people/group Can chat/Can manage access. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/unique-ai-space - Locator: Models; sources/tools; sharing; publishing - Evidence kind: documented - Source date: 2026-06-18 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:conduct Unique AI Conduct. Documents autonomous Python/Bash work, visible steps, approvals and stop, with per-chat files and restricted egress. - URL: https://docs.unique.ai/users/spaces/unique-ai-conduct - Locator: GA release 2026.40; execution UI; limitations - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:release42 Unique release 2026.42. Hosted release 14 October 2026 makes chat sharing and Context Memory GA, labels Scheduled Tasks experimental, changes protected-file ingestion and documents current model additions/migrations. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Release Overview; Chat Platform; RAG; Unique AI; Language Model - Evidence kind: documented - Source date: 2026-10-14 - 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 ### unique-ai:unique-ai:customllm Custom LXM connection. Documents operator-created external model endpoints, API/OAuth credentials and model groups. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/connect-custom-lxm-llm-with-unique-ai - Locator: Technical insight; Create and Connect; Security - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:code Code Execution. Documents Azure Responses API Python execution, downloadable outputs, no outbound internet and model/file restrictions. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Compatibility; output; limitations; governance - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:compliance Compliance Layer 3.0. Describes FINMA/bank-secrecy/CH-DPA Microsoft amendments and deployment-specific assurance limitations. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Legal framework; FSI amendments; deployment feature matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:embeddings Custom embedding models. Documents custom embedding endpoints, one model per organisation and mandatory re-embedding after model/dimension changes. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/usage-or-change-of-custom-embedding-model - Locator: Setup; configuration; re-embedding - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:onpremsecurity On-premises security architecture. Documents full customer control and possible operation without Unique access, with customer models/infrastructure. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/on-premise-tenant/security-architecture-on-premises - Locator: Overview; custom setup - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:operators IT operator documentation overview. Describes dedicated Unique-managed, customer-cloud and full air-gapped on-premise modes. - URL: https://docs.unique.ai/it-operators - Locator: Supported deployment models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-code Code Execution. The page allows selected Knowledge Base files to be preloaded with additionalUploadedDocuments. Its compatibility list includes Azure and LiteLLM OpenAI Responses-capable IDs despite Azure-only introduction/limitations. Azure sandbox controls are not proof of the LiteLLM execution region. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Functionality; Limitations; All available models; Security & Governance; additionalUploadedDocuments - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-models Unique LLM availability overview. The model catalogue separates provider routes, region/SKU choices and QA-only Swiss Phoeniqs. It is a technical availability inventory, not a complete legal subprocessor schedule. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Provider and region matrices; Phoeniqs Model Service; recent changes - Evidence kind: documented - Source date: 2026-10-12 - 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 ### unique-ai:unique-ai:cost Model usage and cost management. Documents off-by-default estimated usage dashboards and enforced daily company/group/user model-call limits. - URL: https://docs.unique.ai/administrators/models-llm-management/model-usage-and-cost-management - Locator: Beta flags; daily limits; cost calculation; CSV - Evidence kind: documented - Source date: 2026-07-21 - 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 ### unique-ai:unique-ai:files Upload and Chat limits. Specifies 512 MB/file, 30 files/batch, default forced retrieval for selected uploads and configurable expiry. - URL: https://docs.unique.ai/users/upload-chat-file-limits-how-large-documents-are-handled - Locator: Production limits; retrieval; expiry - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:filetypes Supported file types. Lists common Office/PDF/text formats and general ingestion limitations that differ from the newer chat-specific limits. - URL: https://docs.unique.ai/users/supported-file-types - Locator: Types; exceptions; ingestion quality - Evidence kind: documented - Source date: 2026-05-09 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:file-ingestion-20261026 Unique file ingestion administration. Base ingestion lacks scanned-PDF OCR. MDI supports image-based PDFs; Docling has partial support. MDI must be provisioned and enabled per folder or chat Space, and the guide distinguishes experimental image-content extraction and deprecated agentic ingestion. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/file-ingestion - Locator: Ingestion overview capability table; Enable MDI; Enable MDI for Upload in Chat - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### unique-ai:unique-ai:kbpermissions Knowledge scope permissions. Describes query filtering by user/group scopes, but older SharePoint permission statements differ from the newer connector guide. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/folder-scope-access-permissions - Locator: Scopes; source integration limits - Evidence kind: documented - Source date: 2026-05-07 - 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 ### unique-ai:unique-ai:sharepoint SharePoint connector. Documents periodic indexed sync, optional content-and-permissions mode, site selection and absent label-level detection. - URL: https://docs.unique.ai/it-operators/integrations-connectors/sharepoint-connector - Locator: Modes; permission sync; limitations - Evidence kind: documented - Source date: 2026-07-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:confluence Confluence connector. Documents Cloud/Data Center content sync without source-permission synchronisation. - URL: https://docs.unique.ai/it-operators/integrations-connectors/confluence-connector - Locator: Requirements; sync; limitations - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:platform-overview-20261026 Unique platform overview. The platform architecture names Google Drive and Salesforce among knowledge sources, alongside SharePoint/OneDrive, Confluence and Teams/Outlook. It does not provide per-connector consent, rollout or price entitlements. - URL: https://docs.unique.ai/administrators/platform-overview - Locator: Connectors and Knowledge Sources diagram - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:release40-20261026 Unique release 2026.40. GA HTML dashboards can list, enable and sign in to MCP connectors, with Salesforce and Yahoo Finance named examples. Contract/module enablement and personal connection state still apply. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-40 - Locator: Hosted September 30 2026; Chat Experience, GA HTML connector dashboards - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-26 ### 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 ### unique-ai:unique-ai:permissioncache Permission cache timing. Describes usual subsecond internal permission propagation without a hard upper bound, and stale rules after a missed broadcast. - URL: https://docs.unique.ai/administrators/access-management-for-admins/cache-permission-sla - Locator: Expected timing; degraded scenarios - Evidence kind: documented - Source date: 2026-09-22 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:keys Single-tenant key management. Explains why client-held keys are unavailable across all Single Tenant data stores and directs full key control to self-hosting. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Big picture; BYOK/CYOK/HYOK; storage locations - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:retention Retention and deletion at Unique. Documents no training, Azure abuse-monitoring opt-out, post-termination retention and backup exceptions. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Hosted-only scope; Azure provider retention; deletion; encryption - Evidence kind: documented - Source date: 2026-05-04 - 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 ### unique-ai:unique-ai:memory Context Memory in Unique AI Chat. Documents private per-user cross-chat memory, edit/disable controls and an explicit warning that disabling does not delete the stored profile. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat/context-memory-in-unique-ai-chat - Locator: Private profile; edit and disable; web-search restriction - Evidence kind: documented - Source date: 2026-09-15 - 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 ### unique-ai:unique-ai:chat Unique AI Chat. Describes the user chat workspace and configurable tools. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat - Locator: Features and access - Evidence kind: documented - Source date: 2026-09-03 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:roles Access role concept. Defines identity, application, space and knowledge-scope permissions, including delegated management roles. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/access-role-concept - Locator: Four access layers - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:mcp MCP tools for spaces. Describes feature-flagged beta MCP clients with organisation and per-space connector/tool controls. - URL: https://docs.unique.ai/administrators/space-management/tools/mcp-tools - Locator: Beta warning; flags; selective tool enablement - Evidence kind: documented - Source date: 2026-05-21 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:hub MCP Hub security governance. Documents per-user token routing, approved origin restrictions and tool-call correlation; some DLP/elicitation pipeline measures are planned. - URL: https://docs.unique.ai/administrators/mcp/the-mcp-hub/govern/security-governance - Locator: Authentication; governance; planned request pipeline - Evidence kind: documented - Source date: 2026-08-26 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:deepresearch Deep Research tool. Documents experimental research/report engine, with separate external OpenAI-engine data flows and limited current tools. - URL: https://docs.unique.ai/administrators/space-management/tools/deep-research - Locator: Experimental warning; engines; user flow - Evidence kind: documented - Source date: 2026-05-09 - 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 ### unique-ai:unique-ai:websearch Web Search tool. Documents multiple search engines, source citations and experimental query review/screening; conversation context may leave through queries. - URL: https://docs.unique.ai/administrators/space-management/tools/web-search - Locator: Modes; engines; external-query warning - Evidence kind: documented - Source date: 2026-05-20 - 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 ### unique-ai:unique-ai:sdk Python SDK documentation. Documents SDK/public API access and customer-operated modules with event-driven webhook integration. - URL: https://docs.unique.ai/developers/software-development-kit-sdk - Locator: Public API; webhook verification; personal/app keys - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scheduled Scheduled Tasks. Documents off-by-default recurring tasks running with user permissions; unattended approvals/questions can stop a run. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: Beta warning; task settings; runs and limits - Evidence kind: documented - Source date: 2026-10-12 - 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 ### unique-ai:unique-ai:review2-scheduled Scheduled Tasks. Scheduled Chat/Conduct tasks offer Automatic or Manual approval. The newer release labels scheduling Experimental and feature-flagged; unattended automatic approval is not mandatory human confirmation. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: At a glance; task Approval setting; unattended runs - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-release42 Unique release 2026.42. Release 2026.42 makes Shared Chats GA, on by default per company with a per-Space toggle and preservation of explicit settings. Scheduled Tasks remain Experimental and feature-flagged. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Highlights; Chat Platform; Conduct scheduling flag - Evidence kind: documented - Source date: 2026-10-14 - 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 ### unique-ai:unique-ai:mcpkb Knowledge Base MCP user guide. Documents external-assistant search/read with user permissions, citations and optional KB scope restrictions. - URL: https://docs.unique.ai/it-operators/integrations-connectors/knowledge-base-mcp/knowledge-base-mcp-user-guide - Locator: Connecting; access; limitations - Evidence kind: documented - Source date: 2026-10-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:api-usage API model usage tracking. Documents public API/SDK model-call usage tracking; some other internal-service calls are outside scope and REST usage retrieval is planned. - URL: https://docs.unique.ai/it-operators/operations/api-model-usage-tracking - Locator: Coverage; flags; limitations - 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 ### 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 ### unique-ai:unique-ai:translation Translator space. Documents beta Office-file/text translation with glossary pre/postprocessing and potential layout disruption. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/translator-space - Locator: Beta; glossary; document types; limitations - Evidence kind: documented - Source date: 2026-05-06 - Retrieved: 2026-10-21 ### 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 ### unique-ai:unique-ai:voice Voice administration. Requires Azure AI Speech Services and describes potential public/backbone audio routing. - URL: https://docs.unique.ai/administrators/space-management/voice-administration - Locator: Dependencies; networking; limitations - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:dpa Unique data processing addendum. Public DPA covers hosted chat/recordings, lists Microsoft, Swiss storage, return/deletion, confidentiality and ten-year audit-log retention. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 2-3, 6-7; Appendices A-B; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:voice-user Using Voice. Documents prompt dictation with EN/DE/FR/IT, immediate audio discard and dialect/recognition limitations. - URL: https://docs.unique.ai/users/spaces/using-voice - Locator: Prompt dictation; privacy note; supported languages - 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 ### unique-ai:unique-ai:sso Single sign-on setup. Documents Zitadel SSO across deployment types, group claims and automatic SAML account creation/update. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/how-to-setup-single-sign-on-sso - Locator: Entra ID OIDC; SAML; managed-tenant setup - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scim SCIM provisioning. Documents Unique SCIM endpoint/key for IdP user/group synchronisation. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/user-and-group-provisioning/scim-system-for-cross-domain-identity-management - Locator: Prerequisites and Entra setup - Evidence kind: documented - Source date: 2026-05-07 - 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 ### unique-ai:unique-ai:analytics Analytics interface. Documents adoption reports, detailed chat/model/tool exports and randomised or stable pseudonymous identifiers. - URL: https://docs.unique.ai/administrators/insights-measurement/analytics-interface/analytics - Locator: Reports; anonymisation; detailed interactions - Evidence kind: documented - Source date: 2026-09-03 - 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 ### unique-ai:unique-ai:audit Audit logs. Defines privileged API event logging with self-service exclusions, deployment-specific retention and request-based export. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: Scope; exclusions; default basic mode; retention and export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:security-export Security Events Export. Documents Single-Tenant-only Azure Activity/Defender Event Hub export with seven-day replay, client-region selection and consumption cost. - URL: https://docs.unique.ai/it-operators/integrations-connectors/security-events-export-see - Locator: Availability; delivered events; retention; cost - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-audit Audit logs. API audit-event guide specifies basic/verbose modes and MT 90-day/ST five-year operational retention. It does not reconcile those event classes to DPA audit logs or a customer-specific contractual override. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: About audit logs; modes; Single and Multi Tenant Clients - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-dpa Unique data processing addendum. The public July 2025 DPA specifies ten-year audit logs and CH storage, while Appendix A lists Microsoft and a client-chosen location. No signed current provider schedule, retention override or contract-precedence mapping was inspected. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 3.15 and 6.1; Appendix A; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-retention Retention and deletion at Unique. Hosted-only policy separates ordinary post-termination content retention, recoverable files and backups and permits contract customisation. Its log/key statements are not reconciled to audit-event/DPA/key-management scopes. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Purpose; Data retention; Deletion after termination; Backups; Encryption in Place - Evidence kind: documented - Source date: 2026-05-04 - 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 ### unique-ai:unique-ai:dlp Data leakage prevention integration. Describes customer-operated HTTPS/DLP proxy and post-chat analytics scanning rather than a default native PII-redaction feature. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-leakage-prevention-dlp - Locator: Proxy; analytics API; compatibility - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:single Single-tenant security architecture. Documents separate Azure landing zone, network restrictions, retention and Unique-managed infrastructure keys. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Azure resources; SSO; encryption; monitoring - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:policy Terms and conditions administration. Documents first-login acceptance, custom terms under an MSA and version/agreement export through GraphQL. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: First-login acceptance; MSA condition; API export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### 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 ### unique-ai:unique-ai:review2-keys Single-tenant key management. May 2026 key guide distinguishes imported customer-generated keys held by Unique from customer-exclusive key control via self-hosting. Its MT/ST CMK statement differs from the hosted retention page; actual MT configuration is unverified. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Infrastructure-only scope; PMK; BYOK/CYOK/HYOK; Summary - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-single Single-tenant security architecture. Single-tenant guide documents separate landing zone, WAF/IP controls and Unique-managed encryption. Its 2048-bit RSA-HSM description differs from the hosted retention page; this does not establish an exact current key design. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Overview; Encryption; Data classification - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-compliance Compliance Layer 3.0. The deployment matrix documents CH North multitenant hosting and selectable single/client-hosted regions, with deployment-specific controls. These are options, not proof of a particular customer contract or current key configuration. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Digital Sovereignty; Feature overview matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:install Unique installation models. Enumerates multi-tenant, single-tenant, customer-managed and on-premise deployments. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique - Locator: Overview - Evidence kind: documented - Source date: 2025-08-06 - 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 ### unique-ai:unique-ai:terms Unique terms of service. Describes a sales-conversation service with Order Form subscription fees, nonrenewal notice, recording export and proprietary rights; applicability to the current AI MSA needs confirmation. - URL: https://www.unique.ai/terms-of-service - Locator: Sections 1-2, 4-6, 11, 17-18 - Evidence kind: documented - 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 ### unique-ai:unique-ai:redaction Chat data redaction and retention. Documents scheduled clearing of chat content and workspace records, with separate upload/KB retention rules. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-redaction - Locator: What is cleared; exclusions; administrator settings - Evidence kind: documented - Source date: 2026-10-18 - 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 ### unique-ai:unique-ai:contact Unique AI contact. Lists Unique AI AG in Zürich, Unique Germany GmbH in Berlin and other regional entities. - URL: https://www.unique.ai/contact-us - Locator: Office addresses - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:trust Unique AI trust centre. Describes CH Azure storage separately from globally routed inference and claims ISO/SOC assurances, with differing SOC types in the FAQ. - URL: https://www.unique.ai/trust-center - Locator: Enterprise security; compliance standards; FAQ - Evidence kind: vendor-claimed - Source date: Not stated - 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 ### unique-ai:unique-ai:iso42001 Unique ISO/IEC 42001 certificate. TÜV SÜD certificate covers development/deployment SaaS for financial services using pretrained foundation models or client-provided models, valid to 6 March 2028. - URL: https://www.unique.ai/hubfs/ISO%2042001_Unique_EN_2025.pdf - Locator: One page; registration 99 420 00001; scope and dates - Evidence kind: certificate-verified - Source date: 2025-03-07 - Retrieved: 2026-10-21 - Issuer: TÜV SÜD South Asia Private Limited - Certificate scope: Unique AG, Stockerstr.34, Zurich. Development and deployment of SaaS for financial-services clients based on pretrained AI foundation models using Azure OpenAI or client-provided models, including client on-premise models. - Valid: 2025-03-07 to 2028-03-06 ### unique-ai:unique-ai:review2-iso-docs ISO Certifications and current downloads. The ISO documentation links 2026 English/German ATTESTA ISO27001 and ISO9001 renewals, plus the 2025 ISO42001 certificate; ISO27001 SoA requires an NDA. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/iso-certifications - Locator: Certificate ISO27001; ISO9001; ISO42001; Statement of Applicability - Evidence kind: documented - Source date: 2026-08-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-iso27001 Unique AG ISO27001 ATTESTA 2026 renewal. Inspected ATTESTA ISO27001:2022 renewal for Unique AG, registration 223-06-018.I, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750716/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO27001:2022 information security management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso9001 Unique AG ISO9001 ATTESTA 2026 renewal. Inspected ATTESTA ISO9001:2015 renewal for Unique AG, registration 223-06-017.Q, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750710/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO9001:2015 quality management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso-register Certificate-linked public register: Unique AG. Public certificate-linked register lookup for Unique AG lists registrations 223-06-018.I and 223-06-017.Q, Zurich, software/IT scope and expiry 31 May 2029. Standard/status text fields are blank; certificate PDFs supply the standards. - URL: https://www.ic-register.com/?qry=Unique&handler=Process - Locator: Unique AG result rows; registration, scope, expiry - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-soc SOC2 Type2: chronology and report access. The dedicated SOC page explains Type1 in December 2023 followed by Type2 in January 2025; audit report and certificate are available only on request after NDA. Auditor, service scope and actual reporting period were not publicly inspected. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/soc-2-type-2 - Locator: SOC2 Type2 timeline; Certificates/report access - Evidence kind: vendor-claimed - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### 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 ### unique-ai:unique-ai:review2-terms-admin Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - 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 ### unique-ai:unique-ai:platform Unique AI platform. Markets a modular finance platform with governed connectors, frontend, financial agents and APIs. - URL: https://www.unique.ai/en/platform - Locator: Frontend, financial agents, MCP Hub; deployment section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:ecb-fx ECB euro foreign exchange reference rates, 20 October 2026. ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time="2026-10-20": USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance-20261026 Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:reference-licence-20261026 Unique public reference repository licence. The public repository defaults to Unique License v1 unless an explicit licence says otherwise; commercial use, distribution and modifications require prior approval. The default is restricted source-available, not an OSI open-source licence. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/LICENSE - Locator: LICENSE, repository-wide disclaimer and exceptions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:unique-licence-v1-20261026 Unique License v1. The published full licence permits personal noncommercial use and requires prior written approval for commercial use, distribution and modification, with separate component-licence exceptions. Swiss law and Zurich venue are specified. - URL: https://github.com/Unique-AG/license/releases/tag/unique-license.v1 - Locator: Grant, Restrictions, Open Source Components, Governing Law - Evidence kind: documented - Source date: 2024-09-24 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-licence-20261026 Unique Python SDK MIT licence. The Python SDK directory has an explicit MIT licence permitting commercial use and modification subject to notice requirements; this exception does not license the hosted platform. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/LICENSE - Locator: unique_sdk/LICENSE, explicit component exception - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-package-20261026 Unique SDK package metadata. At the pinned October 23 repository commit, unique_sdk package metadata declares MIT, consistent with its component licence. Repository/package version is not treated as the hosted release date. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/pyproject.toml - Locator: project name/version and licence - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:review2-terms-admin-20261026 Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-26 ### 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 ### unique-ai:unique-ai:support Enterprise support. Provides public multitenant status link, enterprise email and a contract-specific dedicated support model. - URL: https://docs.unique.ai/enterprise-support - Locator: Contact; dedicated support model; hours - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:status Unique public system status. Public status page displays service/API/collector components and historical uptime panels; dedicated environments are outside the documented status scope. - URL: https://status.prod.unique.app/ - Locator: Component and 90-day uptime panels - 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 ### unique-ai:unique-ai:homepage Unique AI finance platform. Markets embedded experts and structured training programmes for finance users and IT. - URL: https://www.unique.ai/ - Locator: Forward-Deployed Engineers and training section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21