Connect Copilot Cowork to the systems your business runs on

Copilot Cowork plans and carries out multi-step tasks across Outlook, Teams, Word, Excel and SharePoint, and asks before it sends, posts or changes anything. We build the plugins that connect it to your CRM, ERP and internal APIs, set the spending limits and approvals, and roll it out one team at a time.

A senior partner runs the call and tells you which of your workflows suit Copilot Cowork, and which need a custom build, before anything is scoped.

Copilot CoworkWorkplace AI
What it is
Microsoft 365's agent for multi-step workIt plans a task, works through it step by step and asks before it sends, posts or changes files.
Licence
Copilot licence plus usageTasks bill in Copilot Credits, $0.01 each pay-as-you-go or discounted through P3.
Plugins
Skills and MCP connectorsPackaged as Microsoft 365 apps. Claude plugin packages convert on upload.
Admin
Off until an admin turns it onAccess through spending policies, with limits per tenant, group and user.
Models
Anthropic Claude for most workGPT and other models are selectable. EU Data Boundary tenants get GPT models only.

From Microsoft's announcement of 16 June 2026 and Microsoft Learn, checked 12 November 2026.

Clients include

AudinatePinkcubeBizIQCourserAllClear Travel Insurance
Why teams call us

Why Copilot licences stall at email and meeting notes

Your teams use Copilot to tidy emails and recap meetings, then go back to their old tools within weeks. Cowork can take on whole tasks once it reaches your systems, follows your rules and runs within a budget.

No connection to your own systems

Cowork reaches Microsoft 365 out of the box. Your ERP, internal APIs and line-of-business databases need a connector before it can read or update them.

Skills nobody reviews

Each person can write up to 50 custom skills, and Microsoft does not validate them. Without shared plugins, every team writes its own instructions for the same task.

Spend nobody planned

Every task bills in Copilot Credits on top of the Copilot licence. Without spending policies per group, nobody sees the cost until the first invoice arrives.

Adoption left to chance

Licences go unused when nobody shows each team which tasks to hand to Cowork and what it asks before it acts.

What we build on Copilot Cowork

Four builds that take Cowork past the chat window, each with a person approving what it sends or changes.

Connectors

Connectors to your CRM, ERP and internal APIs

Remote MCP servers secured with OAuth, so Cowork reads records and proposes updates in the systems your teams run. We configure partner connectors where they exist and build yours where they do not.

See the context layer
Skills

Plugins that follow your way of working

Your templates, policies and process steps written as skills, packaged with the connectors into one plugin per team, and deployed by your admin to the groups that need it.

Meetings

Meeting follow-up without the chasing

From your meeting notes, Cowork drafts the action items, adds them to Planner and books the follow-up, then waits for approval before anything goes out.

Operations

Tasks that start when your systems change

Event-driven tasks that start when a case lands in your CRM, prepare the reply or the record update, and hold it for a person to approve.

One task, from request to approved action

This is the path a Cowork task takes, and what it can reach along the way depends on the plugins we build.

Copilot Cowork task
  1. RequestA task in plain languageTyped in Copilot, run on a schedule or started by an event in your CRM
  2. PlanSteps, one by oneReads mail, files and Teams with the user's own permissions
  3. PluginsYour skills and connectorsApply your templates and rules, and read or update your own systems
  4. ApproveApproval promptSending, posting, booking and file changes wait for a person
Files land in OneDrive or SharePoint, and prompts, responses and files fall under your Microsoft 365 audit log and sensitivity labels

Illustrative task. Approval and permission behaviour from Microsoft Learn, checked 12 November 2026. Your plugins and approvers are set during scoping.

Where Copilot Cowork fits, and where we would build on something else

Cowork is built for multi-step work that a person starts and approves. Microsoft does not intend it for work that needs guaranteed accuracy without human review.

  1. Multi-step work across mail, files and Teams

    Research a supplier, draft the summary in Word, book the review and send the invite.

    Strong fit

    Cowork plans the steps itself and works inside the Microsoft 365 apps your people already use.

  2. Work that needs your CRM or ERP

    Prepare an account review from CRM history, open orders and last quarter's emails.

    Good fit

    Strong once a connector reaches the system. We configure a partner connector or build an MCP server for yours.

  3. Quick questions and single drafts

    Rewrite a paragraph, or find last week's pricing email.

    Copilot Chat is enough

    Copilot Chat answers inside the conversation, so these need no Cowork task.

  4. High-volume processing with nobody watching

    Read every inbound invoice and post it to the ledger.

    Pick something else

    Cowork waits for a person before it sends or changes anything. We build this on n8n or Microsoft Foundry, where every item runs the same tested steps and only exceptions reach a person.

Systems we connect Cowork to

Cowork reaches beyond Microsoft 365 through plugins, and we add them without replacing the systems your teams run.

  • Dynamics 365 and FabricMicrosoft's own plugins, generally available since June 2026, deployed to the groups that need them.
  • Salesforce, ServiceNow, SAP and JiraPartner connectors from the Microsoft 365 App Store, set up with OAuth and access per group.
  • Odoo, internal APIs and databasesRemote MCP servers we build and secure with OAuth, packaged as a plugin your admin deploys.
  • Planner, OneNote and SharePointPlans, notes and files Cowork reads and updates, each change approved by the person who started the task.
In production today

An agent layer on top of an ERP, running every week

For a dental care group, a Dutch Odoo implementation partner spent a year trying to build scheduling natively. We built an agent layer on n8n over Odoo instead. It is not a Copilot Cowork build, and it follows the pattern a Cowork connector does: the AI drafts and routes, the ERP stays the system of record, and people handle the exceptions.

See all case studies
Dental care groupOdoo and n8n, scheduling
1,500
Appointments scheduled a week
200practitioners
25,000residents served
5sync workflows

How a Copilot Cowork rollout runs

Scoping sets the timeline for your workflow, and every build is tested in staging before it goes live. See how we work

AI pilot
2 to 6 weeks
AI Audit
4 to 8 weeks
Full build
Set in scoping
  1. Solution architecture

    Workflow mapping and architecture

    We map the work your teams do in Microsoft 365 and the systems around it, pick the tasks Cowork takes on first, and set what it may read, draft and change.

    • The tasks Cowork takes on first
    • Spending policies agreed per group
  2. Engineering

    Connector build and data layer

    We build the MCP connectors to your CRM, ERP and internal data, with the context layer behind them where records need cleaning or joining first.

    • OAuth on every connector
    • Staging first, on test data
  3. Engineering

    Plugin build and approval calibration

    We write your templates, rules and process steps as skills, package them with the connectors, and test which actions wait for approval.

    • Approvals tested on real cases
    • Plugins reviewed by your IT team
  4. Integration

    Group rollout and launch

    Your admin deploys the plugins group by group, we show each team the tasks built for it, and we keep improving them in weekly sprints.

    • Every team shown its tasks
    • Weekly sprints that you direct

What teams ask before rolling out Copilot Cowork

Ask us something else

What is Copilot Cowork?

Copilot Cowork is the agent in Microsoft 365 Copilot that carries out multi-step tasks for you. It drafts and sends email, schedules meetings, posts in Teams and creates or edits Word, Excel and PowerPoint files, and it asks for approval before sensitive actions such as sending an email or posting in Teams. Microsoft made it generally available worldwide on 16 June 2026.

How do we get access to Copilot Cowork?

Each user needs a Microsoft 365 Copilot licence, and an admin has to turn Cowork on, because it is off by default. Access is granted through a spending policy that selects Cowork for a group in the Microsoft 365 admin center. Once it is on, people open it in the browser, in the Copilot desktop and mobile apps, and in Outlook and Teams.

What does Copilot Cowork cost?

Cowork is billed on top of the Copilot licence. Each task uses Copilot Credits, at $0.01 a credit pay-as-you-go or at a discount when you commit to a volume in advance through P3 (Microsoft, 16 June 2026). Admins set spending limits per tenant, group and user, and we agree those limits with your finance team before rollout.

Is Copilot Cowork the same as Claude Cowork?

They are separate products. Copilot Cowork is Microsoft's product. It runs inside Microsoft 365 under your tenant's permissions, sensitivity labels and audit log, bills in Copilot Credits, and uses Anthropic's Claude models for most of its work. Claude Cowork is Anthropic's own agent, on a Claude plan. Both use the Agent Skills format, and Copilot Cowork converts a Claude plugin package on upload, so the skills and connectors in it carry across.

How is Cowork different from Copilot Chat?

Copilot Chat answers inside the conversation. Cowork takes a task, breaks it into steps and works through it over minutes to hours, using your mail, calendar, Teams and files, and comes back for approval before it acts. Questions and single drafts belong in Chat, and work with several steps and a finished result belongs in Cowork.

Can Copilot Cowork connect to our CRM or ERP?

Yes, through plugins. Microsoft lists partner connectors for Salesforce, ServiceNow, SAP ERP, Workday and Jira, and its Dynamics 365 plugins are generally available. For a system without one, we build a remote MCP server secured with OAuth and package it as a plugin your admin deploys.

Where should we start?

With one team and one task it runs by hand every week. Book a discovery call and we scope it with you. If you have several candidates, the AI Audit ranks them over 4 to 8 weeks and ends in a 90-day roadmap.

Other platforms we build on

We pick the platform after we understand the workflow, so the same team can build on whichever of these fits it. Compare them all

Workflow automation

n8n

Trigger-and-steps workflows with AI inside them, billed per run and self-hostable in your own cloud.

See n8n
Enterprise AI platforms

Microsoft Foundry

Agents built in your Azure tenant under Entra ID, billed on the Azure account you already have.

See Microsoft Foundry
Agent builders

Sim AI

Open-source AI agent workflows, built on a canvas and run on Sim Cloud or your own infrastructure.

See Sim AI
Workflow automation

Kestra

Open-source orchestration for data and AI pipelines, defined as code and run on your infrastructure.

See Kestra
Workplace AI

Claude Cowork

Anthropic's agent for knowledge work, set up with the plugins, connectors and approval steps your teams need.

See Claude Cowork
SAP

SAP Joule Studio

Custom Joule skills and agents on SAP BTP, connected to the SAP and non-SAP systems your teams query.

See SAP Joule Studio

Guides for teams connecting Cowork

What an MCP connector is, how to run one safely, and what changes when an agent reads your data with a person's permissions.

Explainer

What Is an MCP Server? The Model Context Protocol, Explained

An MCP server gives AI apps tools, data and prompts through one open protocol. How MCP works, how it differs from an API, and a worked example.

Read the guide
Guide

MCP Security: How to Run MCP Servers Safely in the Enterprise

Six public incidents show where MCP deployments break, the controls that stop each one, and how MCP authorization works with OAuth 2.1.

Read the guide
Guide

Data Governance for AI: What Changes When Agents Read Your Data

Whose permissions an agent uses, where access is checked, what to log per answer, and a launch checklist.

Read the guide

Take Copilot past the chat window

Tell us which team goes first and which systems its work touches, and a senior partner scopes the connectors, plugins and spending limits with you.