Eric Brown, a Solution Engineer at Microsoft focused on Copilot and agents, joined Chris and Sash to walk through Copilot Cowork the way he demos it for enterprise customers. The framing up front: the bottleneck in most organizations was never a lack of knowledge, it is coordination across email, meetings, chat, and scattered documents - and Cowork is built to act as an agentic teammate inside that mess rather than another place to search.

Eric ran a live screen share showing the difference between Copilot Chat (single question, single response) and Cowork (connects to tools and data, reasons, and executes multi-step work). A big piece of what makes that possible inside Microsoft 365 is Work IQ - the graph layer that already knows a user's files, meetings, emails, and chats, now paired with an LLM that can reason over it. Eric was clear that Cowork's access is bounded by the same permissions the user already has in Exchange, SharePoint, and OneDrive - "your digital assistant only has access to the items that you have access to" - and described the governance posture as wanting to build "a casino, not a prison," enabling exploration inside real guardrails rather than locking things down entirely.

The back half moved into automations: Eric used voice to ask Copilot to pull meeting transcripts off his calendar and generate a recurring daily digest, live, showing the step-by-step planning Cowork does before it commits to a scheduled task. Chris connected it to his own "orchestrator method" - define the end state with clarity first, then let the agent work backward into steps - and the conversation was headed into how Microsoft 365's credit system prices this kind of agentic work when the recording cut short.

Key takeaways:

• Copilot Cowork's real differentiator over Copilot Chat is that it acts on tasks (connects to tools, plans, executes) rather than just answering a single question - if you are still only using it for one-off Q&A, you're leaving the agentic half on the table.
• Enterprise Copilot's data access is bounded by the user's own existing permissions (Exchange/SharePoint/OneDrive) - it doesn't grant new access, so oversharing risk is closer to "existing permission hygiene" than "AI-specific risk."
• Voice input plus Cowork's task/automation builder can turn a recurring manual chore (pulling meeting transcripts into a summary) into a standing background job with a few spoken sentences - worth trying on your own most-repeated weekly task first.
• Start with "auto" model selection in Copilot if you're not sure which underlying model fits your task; Copilot will route it for you.
• Define the end state before you prompt for the task - Chris's orchestrator framing (clarity on the output shape first, then the steps) mapped directly onto how Eric was structuring his own Cowork requests.

Watch the video version on YouTube · Full show notes, transcript + takeaways