Back to Blog

    Microsoft Copilot

    Work IQ: how Copilot draws context from Microsoft 365

    What Work IQ is, which Microsoft 365 data Copilot uses through it, what is available, how the API is billed and how to test access.

    March 10, 20265 min read
    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    marcel.haas@cnext.ch
    CNEXT AI Agent
    In this article

    Work IQ is Microsoft's context layer behind Microsoft 365 Copilot and agents. It brings together emails, meetings, files, Teams messages, people and other signals that the person asking has access to; existing permissions, sensitivity labels and DLP policies continue to apply, and Work IQ is not an additional database. Our position: the value comes from the interplay of data, context, skills and governance in your tenant, not from the choice of a model.

    Which data and context flow in

    Microsoft describes the context layer and its governance on Microsoft Learn. In practice, three areas can be distinguished.

    Data

    • Microsoft 365 content: SharePoint, OneDrive, Word, Excel, PowerPoint, Outlook and Teams, always based on permissions and in line with existing sensitivity labels and DLP policies.
    • Copilot connectors: prebuilt and custom connectors that bring in content from third-party systems.
    • Dataverse and Dynamics 365: structured business data as an additional knowledge source. Microsoft has announced further integrations; availability per product and region may change.

    Context and memory

    • Memory: In Microsoft 365 Copilot Chat, users explicitly set custom instructions, such as “Always write in the active voice”, and saved memories. Implicitly, Copilot derives recurring preferences from the chat history; Microsoft is communicating step by step which signals feed into this.
    • Semantic index: meaning-based retrieval across tenant content rather than pure keyword matching. Content from Copilot connectors is indexed as well, and existing permissions remain binding.
    • Your organisation's terms: How well Copilot places organisation-specific terms depends on how consistently a tenant maintains SharePoint structures, term stores and sensitivity labels.

    Skills and tools

    Skills are specialised instructions for recurring tasks, such as planning a meeting, summarising a briefing or interpreting a dashboard. Microsoft builds them into its own Copilot experiences and into Copilot Studio, where organisations build their own agents.

    Two ways to use it

    In Microsoft 365 Copilot: An eligible person asks a question in the familiar Copilot experience. Work IQ supplies context under the existing Microsoft 365 permissions. Which features are available depends on the product and licence.

    Through the Work IQ API: A custom application or agent can call Work IQ through documented protocols. Microsoft lists A2A, MCP and REST. According to Microsoft's API overview, the API can be used independently of a Microsoft 365 Copilot licence and is billed by usage through Copilot Credits. Depending on the protocol, feature and tenant, further setup may be needed.

    What is available today

    AreaStatus
    Microsoft 365 Copilot in Word, Excel, PowerPoint, Outlook and TeamsGenerally available (GA)
    Semantic index across tenant contentGA
    Memory in Copilot Chat (custom instructions, saved memories)GA or in broad rollout
    Activity signals from Office apps in memoryRolling out, varies by tenant
    Model choice in selected experiencesRolling out, depending on licence and region
    Copilot CoworkGA for work and school accounts; individual features may be in preview
    Work IQ API (A2A, MCP, REST)Documented, billed by usage through Copilot Credits

    The table is a rough guide. Before production planning, the relevant entry in Microsoft Learn or the Microsoft 365 roadmap is authoritative.

    Model choice is not a reason to buy

    Microsoft 365 Copilot uses various foundation models in the background. Microsoft communicates partnerships with, among others, OpenAI and Anthropic. Direct model choice by end users is not available in every Copilot experience: it arrives first in certain experiences such as Copilot Chat or Researcher; in Word, Excel, Outlook or Teams there is usually no model picker at the prompt.

    We therefore recommend not justifying Copilot investments with multi-model arguments. The value lies in the interplay of data, context, skills and governance, not in a model name.

    Permissions and compliance

    Work IQ uses the existing permission model. Copilot only sees content that the person asking has access to; sensitivity labels are inherited and DLP policies stay active. API requests run with a delegated Microsoft Entra identity in the context of the signed-in person. According to Microsoft, app-only authentication is not currently supported. On data residency, Microsoft describes the EU Data Boundary and its exceptions.

    For Swiss companies with requirements under the FADP, FINMA or industry-specific rules, this means the governance tasks stay the same as without Copilot: permissions, sensitivity labels, DLP and external access. Organisations that already maintain these benefit most.

    A test with two accounts

    Choose a question with a clear source, such as “Which open project decisions are in the latest meeting notes?” Test it with two accounts that have different read permissions. Compare the answer and sources with the original documents, and also test a question without a sufficient source. What matters is not only whether an answer is technically possible, but whether the person asking may see the sources. Only once this works is it worth integrating Work IQ into a business process.

    What we recommend

    1. 1Tenant hygiene first: update SharePoint permissions, external access, sensitivity labels and DLP policies. This is the lever with the greatest effect.
    2. 2A few well-defined use cases: measure three use cases properly in one pilot group rather than rolling out ten in parallel.
    3. 3Use memory deliberately: agree custom instructions centrally rather than having everyone maintain their own saved memories.
    4. 4Measure before and after: with concrete tasks, not only generic adoption KPIs.
    5. 5Follow the roadmap: read the Microsoft 365 roadmap and Microsoft Learn regularly rather than relying on marketing slides.

    We support rollouts with a readiness assessment of permissions, labels and DLP, a use-case workshop for your industry and your data, pilot support with clearly defined success criteria, and training for end users, power users and IT admins based on what is actually available.

    What to bear in mind

    Features and status change frequently; the current entry in Microsoft Learn is authoritative. Work IQ only makes accessible what permissions allow: overly broad sharing therefore remains a risk and should be cleaned up before the pilot.

    Sources

    Microsoft 365Microsoft CopilotAgentic AIDataverse
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Marcel Haas

    Marcel Haas

    Solution Architect, CEO

    6x Microsoft Applied Skills

    Plan a Work IQ test

    We review with you what Microsoft 365 Copilot delivers in your tenant today and test Work IQ with two accounts and clear sources.