Copilot Cowork for AEC teams: what Microsoft's agent changes

Copilot Cowork is Microsoft's agent layer for Microsoft 365 Copilot. Instead of asking Copilot questions turn by turn, work is delegated as a task and the result is reviewed. For construction and engineering teams the fit is recurring assembly work that draws on material already sitting in the tenant: progress reports, RFI register summaries, meeting consolidation and correspondence packs.

There is a second, less discussed consequence. Because the agent reaches across SharePoint, Teams and Outlook using each user's existing permissions, whatever oversharing already exists in your tenant stops being theoretical. Most firms discover this in the first fortnight.

^{What is Copilot Cowork, and how does it differ from Copilot Chat?}

Copilot Chat answers a question using the material it can reach. Cowork takes a scoped task and works through it, producing something you then review. Microsoft's own Microsoft 365 Copilot documentation is the authoritative reference for current behaviour, and worth checking directly because the product changes frequently.

For a delivery team the practical difference:

• Unit of work. Chat takes a question. Copilot Cowork takes a task.
• Where the effort goes. Chat rewards asking well. Copilot Cowork rewards briefing well, then reviewing what comes back.
• Typical AEC use. Chat finds a clause or drafts a paragraph. Copilot Cowork assembles a monthly report or consolidates a register.
• Data reach. Neither sees anything you could not already open. Copilot Cowork simply reaches across more of it.
• Failure mode. Chat gives an answer you can judge. Copilot Cowork gives a finished-looking output you did not watch being assembled.

The last point is the one that matters operationally. A finished-looking progress report is harder to check than a paragraph, because it looks complete.

^{Which AEC tasks suit Copilot Cowork?}

Recurring, information heavy, and drawn from material the tenant already holds.

^{Reporting tasks for Copilot Cowork}

• Monthly and weekly progress reports. Pulling together site notes, programme updates, photographs and subcontractor returns into the client's format. This is the single most common starting point and usually the largest recurring saving.
• Meeting consolidation. Turning a series of minutes into a position paper on a live issue.

^{Registers and tracking with Copilot Cowork}

• RFI and submittal register summaries. Status, ageing, and what needs chasing, drafted for the project manager to approve.
• Action log follow up. Preparing chase correspondence from an action log.

^{Correspondence packs and Copilot Cowork}

• Correspondence packs assembled around a single issue for a commercial or legal review.
• Handover and O&M index drafting from a document store.

^{What does not suit Copilot Cowork}

Anything requiring a decision, anything issued externally without review, and anything drawing on a document store where the current revision is not reliably identifiable. Delegation multiplies the effect of poor document hygiene, because nobody watches the intermediate steps.

^{The permissions problem Copilot Cowork exposes}

This is the part worth reading twice before switching anything on.

Microsoft 365 Copilot respects existing permissions. It does not grant access to anything a user could not already open. That sounds reassuring, and it is exactly the problem: in most established tenants, people can already open far more than anyone realises. Folders shared with the whole organisation years ago, project sites never locked down after handover, HR or commercial material sitting in a general SharePoint library.

In Chat, that latent oversharing rarely surfaces, because nobody thinks to ask. An agent working through a task across the tenant surfaces it as a matter of routine.

Three things to do before a rollout:

1. Audit sharing on the sites the agent will reach. Particularly older project sites and anything created before your current governance standard.
2. Check where commercially sensitive material actually lives. Tender pricing, subcontract terms, staff information.
3. Use the tooling. Microsoft's Purview capabilities for AI exist for exactly this, covering sensitivity labelling and oversight of how AI interacts with organisational data.

Firms that do this first find a rollout uneventful. Firms that skip it tend to pause the rollout in week two, which costs more than the audit would have.

^{What controls should govern Copilot Cowork?}

Four, and none of them technical.

A boundary. Which systems the agent may read and write to, and what it may never do without approval. Anything issued externally sits outside the boundary by default.

A named owner per automated process. One person accountable, reviewing output on a defined cycle rather than assuming it is fine. Firms that automated fifteen processes in six months generally cannot say who owns any of them.

A log. What ran, when, what it produced, kept where the project record is kept. Material generated during a project may be disclosable in a dispute.

Trained reviewers. The person checking a delegated output needs to understand how it was assembled. For firms operating in Ireland or working into the EU, the AI literacy duty in Article 4 of the EU AI Act has applied since February 2025 and requires organisations to ensure staff working with AI systems have an adequate level of understanding of them.

For building bespoke agents rather than using the Microsoft layer, see building Microsoft Copilot agents.

^{What licence does Copilot Cowork need?}

Copilot Cowork sits within the Microsoft 365 Copilot offering, which requires a paid Copilot licence on top of a qualifying Microsoft 365 plan. Licensing and feature availability change regularly and differ between business and enterprise plans, so confirm the current position through Microsoft support rather than relying on any third party summary, including this one.

The practical point for AEC firms: a Copilot licence is a per user cost, and the return depends entirely on whether those users change how they work. Licences issued without training reliably produce low adoption, which is an expensive way to discover that adoption is a behaviour change problem rather than a technical one.

^{How should an AEC team start with Copilot Cowork?}

Pick the monthly progress report. It is recurring, it draws on sources that already exist, and everyone who produces one knows exactly what it costs in hours.

1. Audit permissions on the sites involved.
2. Measure the current process for two cycles.
3. Write the brief and the review standard before anyone runs anything.
4. Run one cycle, with the same quality bar.
5. Measure again, including review time. Time saved assembling and lost checking is the number that decides whether to extend.

Only once that is stable is it worth adding registers and chasing work. An agent built on an unclear process automates the unclearness.

^{What good Copilot Cowork adoption looks like after a quarter}

Delivery teams that get value from Copilot Cowork tend to look similar three months in, and the pattern is less dramatic than most firms expect.

Two or three processes are delegated, not fifteen. Each has a named owner and a log. Firms that automated everything in a quarter generally cannot say who owns any of it, which is the state that produces an incident.

The reporting standard did not drop. The monthly report goes out in the same format to the same quality. What changed is where the project manager's attention sits, moved from assembly to the commentary that actually informs a client.

Permissions were fixed first. The teams that had an uneventful rollout audited sharing before switching anything on. The ones that skipped it spent week two explaining to a director why a delegated summary quoted a document nobody expected it to reach.

Reviewing is routine. People check output because it is the process, not because they distrust it. That habit is what separates a team that can extend this from one that cannot.

Nobody talks about it any more. The strongest signal of successful adoption is that it stopped being a project and became how the monthly report gets written.

^{Copilot Cowork: frequently asked questions}

What is Copilot Cowork? Microsoft's agent layer for Microsoft 365 Copilot, where work is delegated as a scoped task and the result reviewed, rather than requested turn by turn in chat.

How is it different from building a Copilot agent? Cowork is Microsoft's own delegated working mode within Copilot. Building a custom agent means configuring a specific tool for a specific process. They solve different problems and are often used together.

Which AEC tasks suit it? Recurring assembly work drawn from material already in the tenant: progress reports, RFI and submittal register summaries, meeting consolidation and correspondence packs.

Does it create a data risk? It does not grant new access, but it surfaces existing oversharing quickly because it works across the tenant. Audit sharing on the relevant sites before rollout.

What licence is required? A Microsoft 365 Copilot licence on a qualifying plan. Confirm current requirements with Microsoft directly, as availability differs between business and enterprise plans.

Next steps: Copilot Cowork training for AEC teams

AI Institute runs Copilot for AEC Teams, a live online course for project managers, site managers and quantity surveyors, which now covers Copilot Cowork and is updated as Microsoft ships new capability. It is EUR 600 per person and requires a Microsoft 365 Copilot licence.

For the commercial work Copilot Cowork is most often pointed at first, see AI for Excel in AEC commercial workflows.