Fellow for Microsoft Copilot Cowork: How to Turn Meeting Intelligence Into Deliverables

Your team's most important decisions happen in meetings, but the work that follows happens in Microsoft 365. Account briefs get drafted in Word. Status updates land in Teams. Project plans live in PowerPoint. The problem is that the context behind those deliverables (what was actually said, decided, and committed to) stays locked in a separate meeting tool, forcing people to toggle between apps, search recordings manually, or reconstruct conversations from memory.

Fellow for Copilot solves this by bringing your full AI meeting assistant history directly into Microsoft 365 Copilot Cowork. Instead of switching to Fellow to find what happened in a meeting and then switching back to write it up, you describe the deliverable you need and Copilot produces it, grounded in real meeting data. This post covers what Fellow for Copilot is, what it can access, practical prompts for every role, and how your admin controls keep meeting data secure.

What is Fellow for Copilot?

Fellow for Copilot is a plugin for Microsoft 365 Copilot Cowork that connects your Fellow meeting data (notes, transcripts, action items, recaps, and agendas) to Microsoft's agentic AI system. Copilot Cowork is the execution layer of Microsoft 365 Copilot: instead of answering questions in a chat window, Cowork plans multi-step tasks, pulls context from connected systems, and returns finished deliverables like Word documents, PowerPoint decks, and Excel sheets.

With Fellow for Copilot installed, Cowork treats your meeting history as another source of truth alongside Outlook, Teams, and SharePoint. That means a single prompt can combine what was said in a meeting (Fellow) with what was written in an email thread (Outlook) or shared in a channel (Teams) to produce a document that reflects the full picture.

Critically, Fellow for Copilot covers every meeting Fellow captures, not just Microsoft Teams calls. Zoom recordings, Google Meet calls, in-person meetings captured via botless recording, and Slack huddle transcripts all flow into Copilot through this plugin. If Microsoft 365 Copilot could previously only reference the meetings Microsoft recorded natively, Fellow for Copilot fills in everything else.

How does Fellow for Copilot work?

Setup takes minutes and requires no server configuration or custom development.

1. A Fellow workspace admin enables MCP connections under Workspace Settings, which is a one-time toggle

2. Users find Fellow in the Copilot Cowork plugin directory or add it from the Microsoft Marketplace

3. On first use, each user signs in to their own Fellow account inside Cowork and approves the connection

4. From that point forward, Copilot can read Fellow data whenever it helps complete a task

The connection is read-only: Copilot can retrieve meeting data from Fellow but cannot modify anything. Write access (for example, updating meeting agendas from Copilot) is planned for a future release.

What can Copilot access through Fellow?

Once a user connects Fellow in Cowork, Copilot can pull from six categories of meeting data. Each user sees only the meetings, notes, and channels they already have access to in Fellow, so existing privacy controls apply automatically.

1. Meetings. Search past meetings by topic, attendee, company, date, or channel, including full transcript content. This covers meetings across Zoom, Microsoft Teams, Google Meet, in-person, and botless recordings.

2. Recaps and transcripts. AI-generated meeting summaries (including decisions and suggested action items) plus full speaker-attributed transcripts with timestamps.

3. Participants. Who attended a given meeting, useful for account intelligence, relationship mapping, and verifying who was in the room when a commitment was made.

4. Action items. A user's action items across all meetings, filterable by assignee, status, date, or topic. Copilot can pull open items into a status update or flag overdue commitments in a report.

5. Channels. Fellow channels and their details (on plans that include Channels), so Copilot can scope queries to a specific team, project, or client.

6. Agendas and templates. Meeting agendas and the workspace's agenda templates, giving Copilot context on what was planned for a meeting alongside what actually happened.

What are the best use cases for Fellow for Copilot?

The real value of Fellow for Copilot is that Cowork produces finished deliverables, not just answers. Each prompt below combines meeting intelligence from Fellow with other Microsoft 365 data to create something you would otherwise build manually.

Financial services and compliance teams

Analysts, portfolio managers, and compliance officers in investment banking, private equity, and hedge fund firms handle conversations involving MNPI, client commitments, and regulatory obligations. Fellow for Copilot lets these teams turn meeting records into structured compliance documentation without manually reviewing recordings.

Example prompt: "Pull the decisions and client commitments from this week's Investment Committee meetings and draft a Word memo for the compliance review file."

Cowork retrieves Fellow recaps from the relevant meetings, extracts decisions and commitments, and produces a formatted memo. Because Fellow's compliance portal provides workspace-wide oversight with AI trackers that flag MNPI and PII concerns, the underlying meeting data is already governed before it reaches Copilot.

Legal teams

Legal teams conducting depositions, client intake calls, and case strategy meetings need precise documentation of what was discussed and decided. Fellow for Copilot bridges the gap between verbal discussions and the formal records legal workflows require.

Example prompt: "Summarize all meetings tagged 'Project Atlas' from the last 30 days into a Word briefing document organized by date, with participant names and key decisions."

Cowork searches Fellow for all matching meetings, organizes the recaps chronologically with participant attribution, and delivers a document ready for a case file or client update. Fellow's transcript redaction and pause/resume recording controls ensure sensitive portions of conversations are handled before data flows downstream.

Healthcare and healthtech teams

Clinical operations leaders, product teams at healthtech companies, and hospital administrators discuss patient workflows, regulatory requirements, and product roadmaps in meetings that often contain protected health information. Fellow's HIPAA compliance and zero-day retention option mean these conversations are captured under the same data governance standards the organization already follows.

Example prompt: "Create an Excel table of every feature request mentioned in customer meetings with hospital systems this quarter, with the requesting organization and date."

Cowork searches Fellow transcripts across all customer meetings involving hospital system contacts, extracts feature requests, and outputs a structured spreadsheet the product team can prioritize. Fellow's configurable retention policies ensure raw transcripts can be deleted on schedule while AI-generated summaries persist as institutional knowledge.

Sales and account teams

Sales reps spend hours compiling notes from multiple client calls into account briefs, QBR prep docs, and deal summaries. Fellow for Copilot collapses that work into a single prompt.

Example prompt: "Summarize every call we've had with Acme this quarter and draft a Word account brief with open risks and next steps."

Cowork searches Fellow for all meetings with Acme attendees, pulls the recaps and action items, cross-references any related Outlook email threads, and produces a formatted Word document with the account history, outstanding commitments, and flagged risks.

Leadership and executives

Leaders who sit in back-to-back meetings rarely have time to synthesize what they heard into the decks and updates their teams need.

Example prompt: "Create a PowerPoint recapping the key decisions from last week's leadership meetings."

Cowork pulls Fellow recaps from every leadership meeting in the past week, extracts the decisions, and builds a slide deck you can present or distribute, with each decision attributed to the meeting where it was made.

Managers

Managers need to track commitments across 1:1s, team syncs, and cross-functional meetings without maintaining a separate spreadsheet or spending time reviewing recordings.

Example prompt: "What did I commit to in my 1:1s with Jordan this month, and what's still open?"

Cowork searches Fellow for all 1:1 meetings with Jordan, extracts the action items assigned to you, checks their completion status, and returns a list of what you still owe. You can also combine this with calendar data: "Pull my open action items from this week's meetings and block 30 minutes on Friday to clear them."

Individual contributors

ICs often leave meetings with a vague sense of what they owe without a concrete list. Fellow for Copilot turns that into a specific, filterable inventory.

Example prompt: "What action items do I still owe from this week's meetings?"

Cowork queries Fellow for all action items assigned to you from the current week, filters to incomplete items, and returns them organized by meeting. From there, you can ask Cowork to create tasks in your project tracker or draft a status update for your manager.

Meeting prep

Walking into a meeting without context on what was discussed last time wastes the first ten minutes on recap. Fellow for Copilot handles prep automatically.

Example prompt: "Before my 2 pm with the Finance team, pull the last recap and any related emails so I know where we left off."

Cowork retrieves the most recent Fellow recap from your last Finance team meeting, searches Outlook for email threads involving the same participants, and delivers a consolidated briefing doc.

Project teams

Project leads need to spot misalignment between what was agreed in meetings and what is actually being executed.

Example prompt: "Compare what was agreed in the last three project syncs with the latest status email, and flag anything that doesn't match."

Cowork pulls Fellow recaps from the last three project syncs, retrieves the latest status email from Outlook, and surfaces discrepancies between commitments and reported progress.

Customer success

CS teams tracking onboarding issues, feature requests, or churn signals across dozens of customer conversations need a faster way to aggregate patterns.

Example prompt: "Pull every mention of onboarding issues from this month's customer meetings into an Excel table."

Cowork searches Fellow transcripts for mentions of onboarding problems across all customer meetings this month, extracts the relevant excerpts with meeting dates and customer names, and outputs a structured Excel sheet your team can triage.

How do Fellow's admin controls protect meeting data in Copilot?

For teams in regulated industries or any organization handling sensitive conversations, the security model behind Fellow for Copilot matters as much as its capabilities. Fellow's governance controls extend fully to the Copilot connection, giving workspace admins granular oversight without requiring a separate security configuration.

Workspace-level MCP toggle

The entire connection is gated behind a single admin setting. A Fellow workspace admin must explicitly enable MCP connections under Workspace Settings before any user can connect. This setting is off by default, meaning no meeting data flows to Copilot (or any other MCP-compatible assistant) until an admin deliberately turns it on.

Per-user, permission-based access

Each user connects as themselves and authenticates with their own Fellow account. There is no shared or admin-level service account. Copilot can only access the meetings, notes, and channels that specific user already has permission to view in Fellow. If a user cannot see a meeting in Fellow's recording library, they cannot access it through Copilot either.

Granular capability controls

Admins can choose which Fellow capabilities Copilot can use (for example, allowing access to recaps but not full transcripts) and decide whether new capabilities are allowed automatically as they become available or require manual approval. This lets compliance teams match the Copilot integration to the organization's data-access policies.

Full audit trail

Every user's MCP connection is recorded in Fellow's security audit log. Admins can view all active connections and revoke any user's connection from the same settings page. This creates a defensible record of who connected, when, and which data Copilot accessed.

Read-only by design

Fellow for Copilot provides read-only access. Copilot can retrieve meeting data but cannot edit, delete, or modify anything in Fellow. This eliminates the risk of an AI system making unintended changes to meeting records, transcripts, or action items.

Microsoft's data handling

On the Microsoft side, Microsoft states that Copilot Cowork only processes partner data to answer a user's live request and does not store or index it. Combined with Fellow's SOC 2 Type II certification, HIPAA compliance, zero-day retention option, and strict policy of never training on customer data, the integration maintains the same security posture teams already rely on in Fellow.

For organizations in financial services, private equity, hedge funds, or legal, this layered approach means meeting intelligence can flow into Copilot workflows without weakening the compliance controls that govern those conversations in Fellow.

How to set up Fellow for Copilot

Getting started requires coordination between your Microsoft 365 admin and your Fellow workspace admin, but the actual setup takes just a few minutes.

Requirements

1. Microsoft 365 Copilot license with Cowork access. Your Microsoft 365 admin needs to enable Cowork in the admin center and may need to approve or deploy the Fellow plugin via the Agents section of the Microsoft 365 admin center. Cowork usage is billed by Microsoft through Copilot Credits.

2. Any paid Fellow plan. Fellow for Copilot works with Solo, Team, Business, or Enterprise plans. It is not available on the free plan.

3. Fellow MCP setting enabled. A Fellow workspace admin must turn on MCP connections under Workspace Settings. This is off by default. From the same page, admins control which capabilities are available and can view or remove any user's connection.

Setup steps

1. Your Fellow workspace admin navigates to Workspace Settings and enables "Allow users to create MCP connections" under the Security section

2. Your Microsoft 365 admin approves the Fellow plugin in the Microsoft 365 admin center (Admin Center, then Agents)

3. Each user opens Copilot Cowork, finds Fellow in the plugin directory, and adds it

4. On first use, the user signs in to their Fellow account and approves the connection

5. Fellow data is now available in Cowork, and the user can start prompting

If your organization has Microsoft 365 Copilot but is not using Cowork, you can still connect Copilot to Fellow by building a custom agent in Copilot Studio using Fellow's MCP Server URL (https://fellow.app/mcp). Each user authenticates with their own Fellow account the same way.

Close the gap between where meeting intelligence lives and where work gets done

Instead of reconstructing what happened in a conversation from memory or toggling between apps, you describe the outcome you need and Copilot delivers it, grounded in what was actually said. Combined with Fellow's enterprise security controls, SOC 2 Type II certification, and workspace-level admin governance, this integration brings every meeting across every platform into Microsoft 365 without compromising the compliance standards your organization depends on. Try Fellow's AI meeting assistant to see how meeting intelligence connects to the rest of your workflow.