What This Update Actually Is
HubSpot shipped a native AI connector called HubSpot Agent for Copilot. It connects your HubSpot portal to Microsoft 365 Copilot so the humans on your team can ask plain-language questions about their CRM data and get real-time answers.
This isn't a chatbot bolted onto HubSpot. It's a connector that lives inside Microsoft 365 Copilot Chat and the Copilot interface in Teams. When a user asks a question, Copilot fetches live data directly from HubSpot at query time. Nothing is indexed or stored in Microsoft 365.
Three use cases are built in from day one:
- Sales reps can ask for a summary of active deals sorted by closing date, deal name, amount, and stage to prioritize the week without opening HubSpot.
- Support reps can pull all open tickets assigned to them, sorted by priority and creation date, straight from a Teams chat.
- Customer success teams can compare resolution approaches and outcomes across support channels to spot inconsistencies and drive quality.
It joins HubSpot's growing list of AI connectors alongside Claude, ChatGPT, and Gemini. The connector respects each user's existing HubSpot permissions. You only see what you'd already see inside your portal.
Why HubSpot Shipped This
Here's the pattern we see across portals: HubSpot holds the data, but the humans doing the work are living in Microsoft Teams, Outlook, and Word. Switching context costs time and kills momentum.
HubSpot's own data backs this up. Nearly half of HubSpot customers already use multiple LLMs in their work. The internal frustration is real: your CRM is valuable only when it's accessible. If your team has to stop what they're doing and tab over to HubSpot just to answer a basic deal question, they often won't.
HubSpot's answer is to go where the humans already are. Rather than forcing a workflow change, the connector makes HubSpot data available inside the AI tool many enterprise and mid-market teams already have turned on.
How to Use It Step by Step
Setup happens in two stages: admin activation, then individual user connection. Both are straightforward.
Admin steps:
- Open the Microsoft 365 Admin Center and navigate to Copilot connectors, then select Your connections.
- Find HubSpot in the connector list and review the details. No custom development, no file uploads, and no third-party integration tool is required.
- Enable the connector once for the tenant. Every licensed user in the organization can then connect their own HubSpot account.
User steps:
- Open Microsoft 365 Copilot Chat or the Researcher agent. You can also find and install it from the Agent Store inside Microsoft 365 Copilot.
- Open the Sources menu and select HubSpot.
- On first use, sign in to your HubSpot account and grant the required permissions.
- Type your prompt. Copilot fetches your HubSpot data in real time and responds. The result can be acted on back inside HubSpot.
What It Touches in Your HubSpot Strategy
On the surface this looks like a convenience feature. It isn't. It's a strategic shift in how your team interacts with CRM data every day.
Sales Hub is the first beneficiary. Deal prioritization and pipeline reviews no longer require a HubSpot login. A rep in a Teams meeting can ask for deal summaries and get a prioritized list in seconds. That's fewer context switches and faster pre-call prep.
Service Hub gets a real lift too. Support reps can triage their ticket queue from inside Teams before they ever open HubSpot. Customer success teams can run cross-channel resolution comparisons that previously required pulling reports manually.
Key Takeaway
Your HubSpot permission structure is your safety net here. The connector enforces the same role-based access your team already has in HubSpot. A rep who can't see deal amounts in the portal won't see them in Copilot either.
There's one important caveat. If your HubSpot account has Sensitive Data turned on, the connector cannot access engagement data. Plan around this before you roll it out to your team.
This update fits a bigger pattern HubSpot is executing consistently right now. We've covered how HubSpot is expanding its AI footprint across daily workflows in our deep dive on
If you want the full picture of where HubSpot's agentic strategy is going, our HubSpot Agentic Platform pillar page breaks down what's live, what's coming, and what it means for your team.
Key Takeaway
HubSpot data is never indexed into Microsoft 365. Every response is fetched live at query time. This protects data integrity and means your Copilot answers reflect the current state of your CRM, not a cached snapshot.
Pair this connector with the In-Person AI Meeting Notetaker HubSpot shipped for iOS field reps and you have a full loop: capture notes in the field, query deal context from Teams, and act back in HubSpot without ever breaking your workflow.
Who Should Care Most
This update matters most to teams already running Microsoft 365 Copilot. Without that license, it doesn't apply. Here's who gets the most immediate value:
- Sales managers and reps at mid-market and enterprise companies who live in Teams and want deal context without a second tab open.
- Support and service teams with high ticket volumes who need fast triage before they start their day.
- Customer success managers who run QBRs or team reviews inside Teams and want CRM data without building a manual report first.
- HubSpot admins and RevOps leads who need a low-friction way to roll out broader AI adoption without major change management.
- IT and systems admins who need a connector they can enable, govern, and disable from a single admin center without custom code.
If your organization hasn't invested in Microsoft 365 Copilot yet, this update isn't actionable today. But it's a signal worth noting as you evaluate your AI stack.
George's Take
“The best CRM in the world is useless if the humans on your team have to fight to get to it. When your data goes where your people already work, adoption stops being a training problem and starts being a natural habit.”
What excites me about this isn't the technology. It's the behavioral unlock. We talk to companies every week who have a healthy HubSpot portal and a struggling adoption story. The data is there. The discipline to use it consistently isn't. This connector removes one of the most common friction points we see: the tab switch. When a sales rep can ask a deal question without leaving the meeting they're already in, they actually do it. That habit compounds. Better queries lead to better prep, better conversations, and better data back in the CRM. The loop closes in a way that manual workflows rarely achieve.
If you're also rethinking how your team consumes HubSpot data, it's worth pairing this with the recent Customizable Analyze Tabs update, which gives your team a tailored reporting home base inside HubSpot itself.
Ready to figure out where the HubSpot Agent for Copilot fits inside your specific tech stack and team structure? Book a strategy call with Sidekick and we'll map it out with you.
Frequently Asked Questions
What is the HubSpot Agent for Microsoft 365 Copilot?
It's a native connector that lets you query your live HubSpot CRM data and take actions directly inside Microsoft 365 Copilot Chat or Teams. No custom development is required. Admins enable it once in the Microsoft 365 Admin Center, and each user connects their own HubSpot account to get started.
Who can use the HubSpot Agent for Copilot?
Any HubSpot customer on any tier can use it, as long as they have a Microsoft 365 Copilot license or the Microsoft 365 Copilot Chat add-on with an eligible Microsoft 365 license. It works in Microsoft 365 Copilot Chat and the Copilot interface inside Microsoft Teams.
Is HubSpot data stored inside Microsoft 365 when using this connector?
No. HubSpot data is never indexed into Microsoft 365. Every response is fetched live from HubSpot at query time. This means the data in your Copilot answers always reflects the current state of your CRM, not a cached copy.
Does the connector respect HubSpot user permissions?
Yes. The connector enforces the same role-based permissions each user has inside HubSpot. If a rep can't see specific records or deal amounts in the portal, they won't see them through Copilot either. Permission management stays in HubSpot where admins already control it.
Are there any limitations to the HubSpot Copilot connector?
One key limitation: if your HubSpot account has Sensitive Data turned on, the connector cannot access engagement data. Also, the connector requires a Microsoft 365 Copilot license, which is a separate purchase from HubSpot. Admins can disable the connector at any time from the Microsoft 365 Admin Center.
What actions can sales and service teams take with the HubSpot Copilot connector?
Sales teams can query active deals sorted by closing date, amount, and stage. Support reps can retrieve open tickets sorted by priority. Customer success teams can compare resolution approaches across channels. All responses can be actioned back in HubSpot after Copilot surfaces the insights.
