What This Update Actually Is
The HubSpot connector for Microsoft 365 Copilot has always let you read CRM data from inside Copilot Chat and Microsoft Teams. That was useful. But read-only meant you still had to jump back to HubSpot to do anything about what you found.
This update removes that wall. The connector now supports write access across a wide range of HubSpot objects and activities. Here's the full list of what you can now create or update from Copilot:
- CRM records: contacts, companies, deals, and tickets
- Products and line items: add products from your library, update quantities, pricing, and discounts on deals
- CRM activities: log calls, meetings, notes, and emails; create and assign follow-up tasks
Two important caveats worth knowing before you get excited. First, the connector respects your existing HubSpot permissions. Humans can only write to records they're already authorized to edit inside HubSpot. Second, if your HubSpot account has Sensitive Data enabled, Copilot cannot access any engagement data at all.
Some objects remain read-only even with this update. Users, quotes, invoices, orders, carts, subscriptions, and lists (segments) can be read but not written from Copilot. That matters for teams who assumed everything would be writable.
Why HubSpot Shipped This
Here's the pattern we've seen in portal after portal. A rep finishes a call in Teams. They get a summary from Copilot. Then they open a new tab, log into HubSpot, find the right contact, update the deal stage, log the call, and create a follow-up task. That's five or more steps that have nothing to do with selling.
The frustration isn't just wasted time. It's data decay. When context-switching costs five minutes, humans skip logging. Deals stay in the wrong stage. Tasks don't get created. CRM data gets stale, and nobody trusts the reports.
HubSpot's answer: collapse the gap between finding information and acting on it. By adding write access to the Copilot connector, the whole conversation from review to update can happen in one place. That's the real unlock here.
How to Use It Step by Step
Setup requires two admins working in sequence. A Microsoft 365 admin goes first. A HubSpot Super Admin (or someone with App Marketplace permissions) finishes the authorization. After that, individual users connect on their own.
- Microsoft 365 admin: open the Microsoft 365 admin center, navigate to Agents, then All Agents, and search for HubSpot. Confirm the status shows Available. If it shows Blocked, click the agent and select Unblock.
- Microsoft 365 admin: on the Users tab, choose whether to push the agent to all users automatically or allow self-install. Auto-install means users don't have to find and add it manually in Copilot Chat.
- HubSpot Super Admin or user with App Marketplace permissions: authorize the connection and select the allowed HubSpot permissions for the agent.
- Individual user: open Microsoft 365 Copilot Chat or Copilot in Microsoft Teams. In the left sidebar, click HubSpot under Agents.
- Sign in to HubSpot when prompted. Select your account and confirm the permissions you're granting. Click Connect app.
- Start using natural language prompts. When you ask Copilot to create or update a record, it'll ask you to confirm before making any changes in HubSpot. That confirmation step is built in; it's not optional.
One requirement worth flagging upfront: you need a Microsoft 365 Copilot license or the Microsoft 365 Copilot Chat add-on license with an eligible Microsoft 365 subscription. The HubSpot side is available on all plans, but Copilot itself is a paid Microsoft product.
What It Touches in Your HubSpot Strategy
This update lands across the Smart CRM, Sales Hub, and Service Hub simultaneously. Any team that creates or updates records as part of their daily workflow is affected.
Key Takeaway
CRM data quality is the hidden win here. When logging a call or updating a deal stage takes one sentence instead of five clicks, humans actually do it. Better input means better reporting, better pipeline visibility, and better decisions downstream.
Sales Hub and Deal Management
Sales reps can update deal stages, log calls, capture meeting notes, and add products with line item details like quantity and discount percentage, all from a single Copilot conversation. That means your pipeline reports in HubSpot stay current without reps needing to context-switch. If you've ever looked at a sales dashboard full of deals stuck in the same stage for weeks, this is worth paying attention to.
Service Hub and Ticket Management
Support reps can create tickets, update statuses, log resolution details, and assign follow-up tasks without leaving Teams. For teams already using Copilot for call summaries or email drafting, this closes the loop so the resolution context lives in HubSpot, not just someone's head.
RevOps and CRM Data Accuracy
RevOps leaders often find bad data in CRM records because correcting it requires too many steps. With Copilot write access, a RevOps human can say "update the close date for Deal X to December 15 and add a note explaining the change" and it's done. That's a meaningful shift for teams managing data hygiene at scale.
It's also worth thinking about how this connects to AI-driven workflows more broadly. If you're exploring how AI tools should fit into your sales motion, our piece on
how AI should handle lead follow-up without losing the human touch gives useful framing. And if you're looking at how HubSpot's AI layer is growing, our breakdown of Breeze Assistant building Prospecting Agent plays shows where the platform is heading.
Key Takeaway
Permissions are enforced at the HubSpot level, not the Copilot level. A user who can't edit a contact record in HubSpot won't be able to edit it through Copilot either. That's a good thing for data governance, and it means you don't need to create new access controls just for this integration.
API Limits and the Sensitive Data Flag
Every interaction with the HubSpot Agent counts against your HubSpot API usage limits. If your portal already runs high-volume integrations, factor that in. And if Sensitive Data is enabled in your account, engagement data is completely off-limits to Copilot, by design. That's not a bug; it's the expected behavior for accounts that need stricter data handling.
Who Should Care Most
This update matters most to teams already living in Microsoft 365 tools. If your company runs Teams, Outlook, and Copilot daily, the value is immediate. If your team primarily works in HubSpot's native interface, the benefit is smaller.
- Sales reps on enterprise or mid-market teams who close deals through Teams calls and need fast post-call logging without tab-switching
- Support reps managing ticket queues in Teams who need to update statuses and log resolutions without opening a second tool
- Marketing humans capturing leads from live events or campaigns who want to create contacts and log context in real time
- RevOps leaders who need a faster way to correct CRM data without building a full data cleanup workflow
- Companies on any HubSpot plan that have already invested in Microsoft 365 Copilot licensing
If your company hasn't moved to Microsoft 365 Copilot yet, this update is still worth bookmarking. As more teams add that license, they'll want their HubSpot connected and writing from day one.
George's Take
We've been watching this integration evolve, and read-only was always the gap. Humans don't want two tools; they want one conversation that gets things done. What HubSpot shipped here is a real behavior change. When updating a deal takes one sentence, reps actually do it. CRM data stays fresh. Pipeline reports tell the truth. That's not a small thing. That's the whole game for revenue teams.
“CRM data only gets better when logging it costs less than skipping it. Write access in Copilot finally tips that balance in the right direction.”
The confirmation step before changes are made is smart design. It keeps humans in control without slowing the workflow down. And the permission inheritance means your data governance rules already in HubSpot carry over automatically. No new policy needed.
This is a good example of what we mean when we talk about human-centered AI: humans set the direction, AI adds the speed. Copilot doesn't replace your judgment. It just removes the friction between judgment and action.
If your team is running Microsoft 365 Copilot and you want help connecting it to your HubSpot portal the right way, let's talk. We'll make sure permissions, data governance, and your existing workflows are set up before anyone starts typing prompts. Book a strategy call with the Sidekick team at sidekickstrategies.com and we'll walk through your setup together.
Frequently Asked Questions
What can I do with the HubSpot connector for Copilot now that I couldn't do before?
You can now create and update CRM records, including contacts, companies, deals, and tickets, and log activities like calls, meetings, notes, emails, and tasks, all from Microsoft 365 Copilot using plain-language prompts. Previously the connector was read-only, so you had to switch to HubSpot to make any changes.
Does the HubSpot Copilot connector work with all HubSpot plans?
Yes. Write access in the HubSpot connector for Copilot is available to all HubSpot customers across every plan. However, you also need a Microsoft 365 Copilot license or the Copilot Chat add-on with an eligible Microsoft 365 subscription on the Microsoft side.
Will users be able to edit records they don't have permission to edit in HubSpot?
No. The connector respects your existing HubSpot permissions exactly. If a user can't edit a contact or deal in HubSpot, they can't edit it through Copilot either. This means your existing permission structure controls what Copilot can and can't change, with no additional setup required.
What HubSpot objects are still read-only in Copilot even after this update?
Users, quotes, invoices, orders, carts, subscriptions, and lists (segments) remain read-only. You can view data for these objects in Copilot but can't create or update them. Contacts, companies, deals, tickets, products, line items, and engagement activities all support write access.
What happens if my HubSpot account has Sensitive Data enabled?
If Sensitive Data is turned on in your HubSpot account, the Copilot agent cannot access any engagement data at all. This is intentional and applies to calls, meetings, notes, emails, and tasks. All other object types with read or write permissions are still accessible.
How do I set up the HubSpot connector for Copilot for my team?
A Microsoft 365 admin must first enable the HubSpot Agent in the Microsoft 365 admin center under Agents, then All Agents. A HubSpot Super Admin or user with App Marketplace permissions must then authorize the connection. After that, individual users sign in to HubSpot from Copilot Chat or Teams to connect their account.
