Bring Granola meeting context into Microsoft Copilot

TL;DR: Once your Microsoft 365 admin has approved Granola as a federated connector, individual users can connect in under 5 minutes. Enable MCP in Copilot, authorize Granola with browser OAuth, and your meeting notes become queryable in Copilot. Copilot can then ask questions across months of customer interviews, recall specific decisions, and generate briefs from what you talked about rather than from stale documents. The connector is available on all Granola plans. Basic limits MCP access to your personal notes from the last 30 days. Business plans include full personal note history. Enterprise plans include admin-configured scope controls over personal and public workspace notes.

Copilot in Teams answers questions about a meeting from that meeting's transcript, so each answer is limited to one meeting's notes. That context lives in your meeting notes, scattered across tools like Notion, Google Docs, and Slack.

Every AI chat starts from scratch, so you spend the first 10 minutes explaining who you are and what you are working on. Granola's first-party MCP connector fixes that by making your meeting notes, customer research, and decision history available inside Copilot automatically.

Granola is an AI notepad that captures meeting context across Zoom, Meet, Teams, and in-person conversations. Its MCP connector makes that context available inside Microsoft Copilot without manual copy-paste. This guide walks through the setup, shows what Copilot can ask across your meetings, and explains the admin controls for Enterprise teams.

Make meeting context available in Copilot

The Granola Copilot connector makes your meeting notes, transcripts, and meeting context available to Copilot as an MCP (Model Context Protocol) destination. MCP is a standard that lets AI tools access external data sources. Instead of Copilot working only from Teams-native notes or documents you manually upload, it can now query across all your Granola meetings.

Granola is a personal notepad that runs on your laptop or phone, capturing device audio from any meeting platform.

Copilot is part of Microsoft 365 and works within your organization's managed environment. The MCP connector lets Copilot access your Granola notes without copying or storing data in Microsoft 365, and without changing how Granola works.

Granola is listed in the Microsoft 365 Connectors Gallery as a federated connector, which means it can be enabled by your admin through the Microsoft 365 admin center and connected by users directly from Copilot Chat settings.

How to automate research context

The manual alternative is copy-pasting notes into Copilot or re-explaining context every time you start a new chat. If you run multiple customer interviews weekly, that overhead adds up. You lose the ability to ask questions like "What did enterprise customers say about SSO in Q1?" because Copilot only sees the notes you remember to paste in.

Automation keeps context current. Wikis and documents go stale the week they are written, and an agent working from old context gets things confidently wrong. Granola context updates with every conversation, so Copilot works from what you talked about yesterday, not last quarter's summary document.

The connector supports five common uses:

• ASK: Query themes across meetings
• REMEMBER: Recall specific details from past conversations
• ROUTE: Pull relevant detail, organize it, and push it to a CRM or another tool
• MAKE: Create new assets from what you said, like presentations or documents
• BRIEF: Generate summaries and reports from multiple meetings

These patterns cut down the manual work of searching through old notes and stitching together insights.

Automating meeting context retrieval

After you connect Granola to Copilot, your meeting context becomes available through the MCP connector. When you finish a customer interview, Granola generates enhanced notes. What Copilot can reach depends on your plan and, on Enterprise, your admin's settings.

The notes are yours, taken from your point of view, and include your private notes. If you jotted "pricing concerns" during a call, Granola's AI enhancement finds every pricing discussion in the transcript and adds relevant quotes. That structure carries through to Copilot, so when you ask about pricing, you get answers that reflect the points you marked as important.

Granola captures device audio across all meeting platforms, so it works with these platforms:

• Zoom
• Google Meet
• Microsoft Teams
• Slack
• WebEx
• In-person conversations

Your Copilot queries are not limited to Teams meetings. You can ask across every conversation you have captured in Granola, regardless of platform.

How to set up the Granola Copilot connector

Once admin approval is in place, individual user setup takes under 5 minutes. You need a Granola account, a Microsoft account with Copilot access, and MCP enabled in Copilot. Admin approval is a separate step and is covered in Account setup for Copilot connection below.

No training is required. The connector uses browser OAuth, which means you authenticate through your browser without generating API keys or client secrets.

Account setup for Copilot connection

Before you start, confirm you have these three things before starting:

• Granola account: You need existing meeting notes to query
• Microsoft Copilot access: Through your organization's Microsoft 365 subscription
• MCP enabled: In your Copilot settings, covered in Step

Regardless of plan, a Microsoft 365 admin must approve Granola before it is available to users. Granola is a partner-submitted federated connector. The Microsoft 365 admin goes to Copilot connectors > Your connections in the Microsoft 365 admin center and enables Granola for the organization.

If your organization is on an Enterprise plan, a Granola Enterprise admin must also act. In Granola workspace settings, the Enterprise admin enables MCP and configures which note scopes are available to members: Personal notes, Public notes, both, or neither. MCP is off by default for Enterprise workspaces. Once both steps are complete, each user connects their own Granola account via browser OAuth the first time they use a Granola tool.

Step 1: Enable MCP in Copilot

There are two ways to connect Granola to Copilot. Use the route that matches how your organization has deployed Copilot.

Route 1: Microsoft 365 Copilot (federated connector)

This is the standard route for most users. Your Microsoft 365 admin must have approved Granola in the admin center before this option appears.

1. Open Microsoft 365 Copilot Chat.
2. Select the ellipsis (...) menu and choose Settings.
3. Select Sources in the left pane.
4. Find Granola in the list and select Connect.
5. Complete authentication in the browser window that opens.

Route 2: Copilot Studio (custom agent)

Use this route if you are building or configuring a declarative agent in Copilot Studio.

1. Open your agent and select the Tools page.
2. Select Add a tool, then select New tool.
3. Select Model Context Protocol.
4. In the wizard, enter a server name and description, then set the server URL to https://mcp.granola.ai/mcp.
5. Set the authentication to OAuth 2.0 with Dynamic discovery, which supports Dynamic Client Registration.
6. Complete the wizard to add the Granola server to your agent.

Step 2: Authorize with browser OAuth

If you connected via Route 1, authentication completes when you select Connect in Sources. If you connected via Route 2, search for Granola or enter the server URL https://mcp.granola.ai/mcp manually.

When you connect, a browser window opens and asks you to authorize the connection. Granola uses Dynamic Client Registration, which handles credentials automatically. You do not need to generate or enter any client ID or client secret. Once you authorize, the connection is established and Granola's tools become available in Copilot.

Step 3: Check the connection

To verify the connection is active, check that the Granola tool appears in your Copilot Tools list. In Copilot Studio, all tools are turned on by default when you add an MCP server. Note that other MCP client environments, such as Visual Studio, require you to manually enable each tool after adding the server.

Run a test query to confirm the connection works. Ask Copilot something like "What did I discuss in my last customer interview?" If the connection is active, Copilot searches your Granola meeting history and returns relevant context. On Business and Enterprise plans, Copilot can also pull quotes directly from transcripts. On Basic, transcript access is not included.

To revoke the connection, do so from within your AI client (such as Copilot, Claude, or ChatGPT), depending on which client you used to add the server.

What Copilot can ask across your meetings

Once connected, Copilot can query across all your Granola meetings using natural language. Ask questions in chat and get answers drawn from your meeting history.

Retrieve past customer interview details

You can ask Copilot questions that require synthesizing patterns across dozens of conversations over months. You can ask something like "What did enterprise customers say about SSO in Q1?" Copilot queries your Granola meetings, finds every conversation where SSO came up, and returns an answer with relevant context.

That saves the manual work of searching through old notes or asking teammates "didn't we talk about this before?" The answer is already in your meeting history, and Copilot can surface it without manual searching.

Use recent meeting context in Copilot

Copilot can also pull context from recent meetings to help you prepare for follow-ups. You can ask "What are the open threads from my last three customer calls?" Copilot queries Granola, identifies action items and unresolved questions, and returns a summary.

For stakeholder presentations or roadmap discussions, you ask Copilot to surface what matters from the past week rather than manually reviewing each note.

To recall a decision, ask "What did we decide about the pricing model in the last product review?" and Copilot finds the relevant discussion and returns the decision with the meeting it came from.

Automate meeting summaries and reports

Copilot can generate summaries and reports from multiple meetings. You can ask "Generate a weekly research summary from my customer interviews." Copilot uses Granola context to create the report, pulling themes, quotes, and action items from each conversation.

Because Granola updates after every meeting, the context Copilot draws from stays current. You can ask questions like "What themes came up across my customer interviews this quarter?" and Copilot searches your full Granola history to return an answer.

Instead of spending hours tagging insights and building a synthesis deck, you ask Copilot to generate the first draft, then refine it with your own analysis.

Managing your Granola data within Copilot

Granola's MCP connector includes note-level and admin-level controls that determine what Copilot can query. Within those boundaries, you can manage permissions at the user level, and admins can configure org-wide settings for Enterprise workspaces.

Managing Copilot meeting permissions

Each person connects their own Granola account and queries their own meeting history. On Basic, MCP accesses your personal notes from the last 30 days. On Business, MCP covers your personal notes with full history. On Enterprise, admins configure which note scopes are available to members across the workspace.

Control what Copilot can reach

Enterprise admins configure which scopes are available to members in Granola settings. Options are Personal notes, Public notes, both, or neither. Only admins can change this setting. If neither scope is enabled, members cannot use Granola MCP.

Enterprise-Managed Authorization requires an Enterprise Granola workspace with SSO enabled and a compatible identity provider such as Okta. Your MCP client must also support EMA. Granola has tested EMA with Claude using Okta as the identity provider. Copilot has not been confirmed as a tested EMA client.

Enterprise-Managed Authorization lets your company control access to Granola MCP through its identity provider. Users sign in to their MCP client with their company account, and the identity provider decides whether they can connect to Granola. Your identity provider controls who can connect, and Granola's workspace settings control which notes they can access.

Admins can assign specific users or groups through their identity provider to control which teams can connect, giving granular control over what is shared. You can also configure transparency features like automated chat messages or video watermarks to let meeting participants know Granola is transcribing.

Enterprise controls for audit logs

Granola is SOC 2 Type 2 certified as of July 2025 and GDPR compliant. Granola captures device audio and transcribes in real time, deleting audio immediately after processing. No audio files are stored.

Enterprise plans include an Audit API that lets you pull workspace audit events into your security and compliance tools. Granola encrypts data in transit and at rest.

Granola vs. native Copilot note limitations

Granola and native Teams meeting notes serve different purposes. Copilot in Teams meetings works well for single-meeting summaries within Teams. Granola works well when you need cross-platform capture, cross-meeting queries, and research-specific workflows.

The table below shows how they compare:

Copilot in Teams meetings requires an add-on Microsoft Copilot license per user. Without transcription or recording enabled, notes do not persist after the meeting window closes. Granola notes persist and become part of a searchable archive you can query across months or years.

When to use Granola and when to use Teams notes

Use Granola when you need to capture context across multiple platforms or when you are doing customer research. If you run interviews on Zoom, Meet, and Teams, Granola captures all of them and makes them queryable in Copilot. You are not limited to Teams meetings.

Use Granola when research rigor matters. The human-in-the-loop enhancement means your notes reflect what you thought was important during the conversation. When you ask Copilot to find patterns, it searches notes that were structured by your judgment during the conversation.

Use Copilot in Teams meetings when you only need a single-meeting summary and your organization already has an add-on Microsoft Copilot license. If your workflow is entirely within Teams and you do not need cross-meeting queries, native notes cover your needs.

For product managers running discovery research, Granola is the input layer. You capture customer interviews in Granola, then use Copilot to query across those interviews when you need to validate a roadmap decision or answer a stakeholder question. Copilot becomes the interface for asking questions, and Granola is the memory that makes those questions answerable.

For enterprise meeting management within Teams, Copilot in Teams meetings may cover your needs. The two tools can coexist. Granola captures the research context, and Copilot uses that context for enterprise workflows.

Start querying your meeting context in Copilot

Granola captures the meeting context that Copilot cannot reach on its own. Cross-platform interviews, in-person conversations, and months of customer discussions across Zoom, Meet, Teams, and Slack all stay searchable in one place, and Copilot can query across all of it the moment you connect.

Try Granola for free. Once your Microsoft 365 admin approves Granola as a federated connector, individual user setup takes under 5 minutes. Download the app, run your next meeting, and your notes become queryable in Copilot from that point forward.

FAQs

What is the Granola Copilot connector?

The Granola Copilot connector is a partner-submitted federated connector listed in the Microsoft 365 Connectors Gallery. It uses MCP to make your Granola meeting notes available inside Microsoft Copilot in real time, without indexing data into Microsoft 365. It lets Copilot query across all your meetings and return answers drawn from your meeting history.

How long does setup take?

Individual user setup takes under 5 minutes once your Microsoft 365 admin has approved Granola in the admin center. If your organization is on Enterprise, a Granola Enterprise admin must also enable MCP for the workspace before users can connect. Admin steps are covered in the Account setup section above.

Does the connector work on the free Basic plan?

Yes, MCP is available on all Granola plans. On Basic, MCP accesses your personal notes from the last 30 days. Business plans include personal notes with full history.

What admin controls are available for Enterprise?

Enterprise admins can enable MCP for the workspace, configure which note scopes are available to members, and use Enterprise-Managed Authorization to control access through an identity provider.

Key terms glossary

Model Context Protocol (MCP): A standard that lets AI tools access external data sources. Granola's MCP connector makes your meeting notes available to Microsoft Copilot and other MCP-compatible AI tools.

Browser OAuth: An authentication method that lets you authorize connections through your browser without managing API keys. Granola uses Dynamic Client Registration to handle credentials automatically, so you never copy-paste secrets.

Research repository: A centralized, searchable archive of all your customer interviews and meeting notes. Granola acts as a research repository that Copilot can query across months of conversations.

Enterprise-Managed Authorization (EMA): A feature that lets your company control access to Granola MCP through its identity provider. Requires an Enterprise Granola workspace with SSO and a compatible identity provider such as Okta. Granola has tested EMA with Claude and Okta. Users sign in with their company account, and the identity provider decides whether they can connect.