Microsoft just launched Copilot Cowork a feature that lets Copilot execute multi-step tasks across your entire M365 environment. I tested it this week. Here’s what I learned about the shift from prompting to delegating.

The prompting era is evolving

For the past two years, the AI conversation in most organizations has been about prompting. How to write better prompts. Prompt libraries. Prompt engineering workshops. And yes all of that was valuable. But this week, something shifted.

Microsoft launched Copilot Cowork as part of the Frontier program. And it changes the game fundamentally. Instead of asking Copilot to do one thing at a time, you can now describe an entire workflow and Cowork executes it across Outlook, Teams, Word, Excel, and more.

We went from “write me an email” to “research this client in my emails, draft a proposal in Word, and schedule a follow up in Teams.” The skill is no longer just prompting. It’s delegating.

What is Copilot Cowork, exactly?

Copilot Cowork is a new experience inside Microsoft 365 Copilot that can carry out multi-step tasks on your behalf. You describe what you need in natural language, and Cowork breaks it down into steps, works through them across your M365 apps, and asks for your approval before taking key actions like sending emails or scheduling meetings.

Think of it as going from a chat assistant to a capable colleague who can actually do things in your environment. It sends emails, schedules meetings, creates documents, posts in Teams, and searches across your organization.

It’s currently available through the Frontier preview program. Microsoft’s early access track for the latest Copilot innovations.

4 lessons from my first week with Cowork

LESSON 1

Think in workflows, not prompts

The biggest mindset shift: stop asking for one thing. Instead, describe the outcome you need across multiple steps. That’s where Cowork truly shines.

Before:  Write an email to the project team with a status update.

After:  Check my last 3 Teams conversations about Project Alpha, summarize the status, draft an email to the project team, and add a follow-up meeting to my calendar for Friday.

The second prompt triggers a chain of actions across Teams, Outlook, and Calendar. One instruction, four apps, zero switching.

LESSON 2

Give context like you’d brief a colleague

Cowork performs dramatically better when you provide role, goal, constraints, and sources just like you would when briefing a real colleague.

Before:  Prepare for my meeting tomorrow.

After:  I have a quarterly review with the marketing team tomorrow at 10 AM. Find the latest campaign performance data from our shared Excel files, check any relevant Teams threads from the past week, and create a one page briefing document in Word.

Context is everything. The more specific you are about what you need and where to find it, the better the result.

LESSON 3

Point to your files

Copilot works best when you reference specific documents, emails, or chats. Vague references lead to vague results.

Before:  Based on recent info, update the project plan.

After:  Based on last Tuesday’s project update in the Teams channel ‘Project Alpha’ and the budget spreadsheet in our SharePoint folder, update the project timeline in Word.

Specific references let Cowork pull the right data from the right places. Think of it as giving someone directions instead of saying “you know where it is.”

LESSON 4

Iterate out loud. Cowork is conversational. If the first result isn’t right, don’t start over refine.

“Make the summary shorter.”

“Add the Q1 revenue numbers.”

“Change the tone to be more formal.”

“Now send it to the team.”

Each follow up builds on the previous result. It’s a conversation, not a one-shot prompt. The people getting the most value from Copilot aren’t better prompters they’re better delegators.

What this means for AI adoption

If you’re leading AI adoption in your organization, Copilot Cowork changes the training conversation. The focus needs to shift from “how to write a good prompt” to “how to delegate effectively to AI.” That’s a fundamentally different skill. It requires thinking about workflows end-to-end, being specific about context and sources, and being comfortable iterating in a conversational way.

The good news? Most professionals are already great delegators when it comes to working with human colleagues. The same principles apply here. Brief clearly, point to the right resources, and refine as you go.

Getting started

Copilot Cowork is available through the Frontier program for Microsoft 365 Copilot users. If your organization has Copilot licenses, your IT admin can enable Frontier in the Microsoft 365 admin center. Individual users with Microsoft 365 Premium, Personal, or Family subscriptions can opt in directly via Copilot Settings.

Once enabled, you’ll find Cowork in the Agent Store inside the Microsoft 365 Copilot app. Pin it to your left rail, and you’re ready to go.

A note on data residency for EU organizations

If you’re working in the EU, there’s one important thing to be aware of. Microsoft 365 Copilot is an EU Data Boundary service your data stays within the EU. However, Copilot Cowork uses Anthropic’s Claude model under the hood, and Anthropic is currently out of scope for the EU Data Boundary and in country LLM processing commitments.

In practice, this means that prompts processed by the Anthropic model may leave the EU Data Boundary. For EU, EFTA, and UK tenants, the Anthropic subprocessor is disabled by default your IT admin needs to explicitly enable it in the Microsoft 365 admin center before Cowork becomes available.

This doesn’t mean you shouldn’t use it. But it does mean you should have the conversation with your compliance and security teams before rolling it out. Anthropic models are covered under the Microsoft Product Terms and Data Protection Addendum, and Microsoft’s existing privacy, security, and GDPR commitments still apply. Just make sure everyone is aligned on the data residency implications.

Bottom line: your data is still protected under Microsoft’s terms, but for EU organizations, Copilot Cowork requires an active, informed decision to enable the Anthropic subprocessor.