Microsoft 365 Copilot + HubSpot: What the Integration Can (and Can't) Do in 2026
Partly — there are two official ways to reach HubSpot from Microsoft 365 Copilot, and both are read-only. Microsoft publishes a HubSpot federated Copilot connector (in preview in the CRM section of the Connectors Gallery) that uses Model Context Protocol to pull HubSpot CRM data into Copilot in real time — and Microsoft’s own docs state plainly that federated connectors “are read-only.” Separately, HubSpot ships the HubSpot Agent for Copilot, which HubSpot describes as “limited to read-only access… it doesn’t have the ability to create or edit data in HubSpot.” So Copilot can answer questions grounded in your HubSpot records, but neither path can create a contact, update a deal stage, or log an activity back in HubSpot. And either way, everything happens inside a Copilot chat you’re driving — nothing watches your pipeline between prompts.
Here’s what each path actually does, how to turn it on, where the ceiling is, and what to use if you want HubSpot-adjacent work that runs on its own.
What Microsoft 365 Copilot can actually do with HubSpot
Through the HubSpot federated connector (Microsoft-published, MCP-based, real-time):
- Answer questions grounded in live HubSpot CRM data. The connector “connects to HubSpot CRM data to enable users to access and enrich responses with customer, sales, and marketing insights,” per the Microsoft connectors gallery — fetched at runtime via MCP, never indexed into Microsoft 365.
- Work inside specific Copilot surfaces. Federated connectors are supported in Microsoft 365 Copilot Chat, Copilot in Excel, and the Researcher agent — users pick HubSpot from the Sources menu and authenticate with their own credentials.
- Respect HubSpot permissions. Access runs on the authenticated user’s identity via OAuth 2.0, so a person only sees the records they can already see in HubSpot.
Through HubSpot’s own HubSpot Agent for Copilot (HubSpot-published, listed on the HubSpot marketplace):
- Query core CRM objects and their associations in natural language — contacts, companies, deals, tickets, and users, plus commerce objects (quotes, invoices, orders, products, subscriptions) and engagements (calls, meetings, notes, tasks, emails), with associations across contacts, companies, and deals.
- Runs on web, desktop, mobile, and Microsoft Teams, generating AI insights from those records inside Copilot.
Both are grounding tools. Neither writes.
How to set it up
The Microsoft-built federated connector is largely on by default:
- Microsoft-published federated connectors are enabled by default for a tenant, but a new one is visible only to admins for seven calendar days before it reaches users. During that window a Microsoft 365 admin can review, disable, or stage the rollout in the Microsoft 365 admin center → Copilot connectors → Your connections, per Microsoft’s federated connectors guide.
- In Microsoft 365 Copilot Chat, open the … → Settings → Sources, find HubSpot, select Connect, and complete authentication with your HubSpot credentials.
- Enter a read-only prompt, for example: “Summarize the open deals for Northwind Traders and their last activity dates.”
For HubSpot’s Agent for Copilot, the setup is a two-side job: a Microsoft 365 admin adds the HubSpot Agent to the tenant and chooses who can use it, and a HubSpot Super Admin (or a user with App Marketplace permissions) authorizes the connection and selects the allowed permissions. Each user needs a Microsoft 365 Copilot license or the Microsoft 365 Copilot Chat add-on with an eligible Microsoft 365 license.
The limits that matter
- Both official paths are read-only. Microsoft’s docs say federated connectors “are read-only,” and HubSpot says its agent “doesn’t have the ability to create or edit data in HubSpot.” Copilot cannot create a contact, move a deal stage, or log a call back in HubSpot through either one.
- Sensitive Data is walled off. If your HubSpot account has Sensitive Data turned on, the HubSpot Agent for Copilot cannot access engagement data for those records.
- Preview and surface-bound. The Microsoft HubSpot connector is in preview, and federated connectors only work in Copilot Chat, Copilot in Excel, and the Researcher agent — not everywhere Copilot appears.
- Subject to HubSpot API limits. The agent’s fetches count against your HubSpot API usage.
- No triggers, ever. Neither path fires on a HubSpot event. Copilot answers when you prompt it; it never reacts on its own. A deal can stall or a lead can sit unrouted over the weekend and nothing moves.
- Session-bound. Every action needs a person in a live Copilot chat. There’s no standing watch on your pipeline.
If you want HubSpot-adjacent work that runs on its own: Carly
The moment you want something to happen around HubSpot without you in the chat — a new lead routed and emailed within minutes, a nudge when a deal stalls in a stage, a Monday pipeline digest built and sent, a won deal posted to the right Slack channel and logged as a task — you’ve crossed past what a read-only grounding connector is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud. When a deal changes stage or a form fill lands in HubSpot, Carly reacts — summarizes it, emails the owner, updates the record, posts to Slack — while your laptop is closed.
- Actually reads and writes. HubSpot is a native Carly integration, so Carly can update deals, log activity, and create contacts and tasks — not just surface them in a chat.
- Sends, not just drafts. Carly drafts and sends email across Gmail and Outlook, books meetings, manages tasks, and records meetings — the follow-through that stops at the chat with Copilot.
- Builds the workflow by interviewing you. Tell Carly “when a deal moves to Contract Sent, draft a recap email to the deal owner and create a follow-up task” in plain English; it interviews you and builds it — no admin center, no MCP setup, no prompt engineering.
Carly connects to 200+ tools across 40+ categories natively, plus any other tool via your own API key — paste it on carlyassistant.com/integrations. AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. See integrations.
Microsoft 365 Copilot vs Carly
| Microsoft 365 Copilot (HubSpot) | Carly | |
|---|---|---|
| Answer questions grounded in CRM data | Yes (connector, read-only) | Yes |
| Query HubSpot records in Copilot Chat | Yes | Via the integration |
| Update / create records in HubSpot | No | Yes, natively |
| Log activity, create tasks in HubSpot | No | Yes |
| Objects reachable | Core CRM + commerce + engagements (read) | Full API scope |
| Acts on HubSpot triggers / events | No | Yes |
| Monday pipeline digest, on schedule | No | Yes |
| Sends email as part of the flow | No | Yes (Gmail + Outlook) |
| Works while laptop is closed | No (session-bound) | Yes (cloud, 24/7) |
| Setup | Admin center + connector, per-user Copilot license | Describe it in plain English |
| Pricing | Microsoft 365 Copilot license per user | AI agents from $35/mo |
Copilot’s HubSpot paths are a grounding layer that pulls CRM context into your chats. Carly is a teammate that acts on HubSpot events as they land.
Frequently Asked Questions
Does Microsoft 365 Copilot work with HubSpot?
Yes, for reading. There are two official paths: Microsoft’s HubSpot federated Copilot connector (preview) pulls HubSpot CRM data into Copilot in real time via MCP, and HubSpot’s own HubSpot Agent for Copilot lets you query contacts, companies, deals, and tickets in natural language. Both are read-only — they surface records but don’t write anything back to HubSpot.
Can Microsoft 365 Copilot update or create records in HubSpot?
No. Microsoft’s documentation states that federated connectors “are read-only,” and HubSpot says its agent is “limited to read-only access… it doesn’t have the ability to create or edit data in HubSpot.” Neither official path can create a contact, update a deal stage, or log an activity in HubSpot.
How do I connect Copilot to HubSpot?
For the Microsoft connector, an admin manages it in the Microsoft 365 admin center → Copilot connectors → Your connections (it’s on by default after a seven-day admin review window), then users connect HubSpot under Copilot Chat → Settings → Sources with their own credentials. For the HubSpot Agent for Copilot, a Microsoft 365 admin adds the agent to the tenant and a HubSpot Super Admin authorizes the connection; each user needs a Microsoft 365 Copilot or Copilot Chat license.
Can Copilot react to a new HubSpot lead or a stalled deal automatically?
No. Neither path fires on HubSpot events — Copilot answers only when you prompt it in a session. For “when a lead lands, route it and email the owner” or “when a deal stalls, nudge the rep,” you need a trigger-based assistant like Carly, which integrates natively with HubSpot, reads and writes, and runs in the cloud around the clock.
More: Best AI CRM tools · Best AI agents for productivity · Microsoft Copilot + Salesforce · ChatGPT + HubSpot
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
