Product Update: HubSpot & Microsoft 365 Copilot Integration

If your team spends half the day bouncing between HubSpot and their inbox, you already know the cost. Every tab switch is a small tax on focus, and those small taxes add up fast across a sales floor or a support queue. HubSpot's newest integration is aimed squarely at that problem.

The HubSpot Agent for Microsoft 365 Copilot lets your team query HubSpot CRM data using natural language, without leaving Copilot Chat, Teams, or Outlook. Ask for a pipeline snapshot, a ticket summary, or an account briefing, and the agent pulls it straight from HubSpot into the conversation you're already having. No new tab, no context switch, no losing your train of thought mid-call.

Here's what it actually does, how to set it up, who benefits most, and the constraints worth knowing before you roll it out to your team.

What the Integration Actually Does

Once the HubSpot Agent is added to your Microsoft 365 environment, it shows up as an agent inside Copilot Chat and Copilot in Teams, across web, desktop, and mobile. From there, your team can ask natural-language questions about their HubSpot data and get answers pulled live from the CRM.

Under the hood, it works over core CRM objects, contacts, companies, deals, and tickets, along with the associations between them. That means a rep can ask for a summary of an account before a call and get open deals, key contacts, and recent engagement in one response, all without switching out of Teams or Outlook.

It's worth being clear about what this integration is and isn't. It's a research and prioritisation tool. It fetches and summarises data. It does not create or edit records in HubSpot. If you ask Copilot to update a deal stage or log a note, it won't. Think of it as a faster way to see and understand your CRM data, not a new way to change it. For most teams, that's exactly the right scope: the friction it removes is in finding and digesting information, not in the CRM actions themselves.

Getting Set Up

Rolling this out isn't complicated, but there are a few steps and a couple of licensing requirements to plan around.

On the Microsoft side:

• A Microsoft 365 admin needs to enable the HubSpot Agent for your tenant first. This is a one-time, organisation-wide step.
• Each individual user needs a Microsoft 365 Copilot license, or the Copilot Chat add-on paired with an eligible Microsoft 365 license.

On the HubSpot side:

• Once the agent is enabled, each user signs into their HubSpot account and grants permission the first time they use it.
• You can only connect one HubSpot account per Copilot account at a time, so this works best when each user has a single, clear HubSpot login.

Permissions: The agent respects whatever HubSpot permissions a user already has. If someone can't see a record in HubSpot, they won't see it in Copilot either. This matters for team-wide queries in particular: a sales manager asking about "my team's pipeline" will only get a full answer if their HubSpot permissions actually grant visibility into the team's records. Otherwise, they'll just get their own.

One caveat worth flagging to any client with Sensitive Data settings turned on in HubSpot: if that's enabled, Copilot can't access engagement data at all. Prompts that lean on activity history, like "which accounts have gone quiet," won't return much in that scenario. Object and property data such as deal stage, ticket priority, close date, and owner will still work fine.

Use Cases by Team

The most useful way to think about this integration isn't as a single feature, but as a different entry point into the same CRM data for each part of the business.

Sales

HubSpot's own use case here is straightforward: reps can review their active deals and sort by close date to prioritise their day. But the real value shows up in the small moments around that, pulling deal context, contact and company records, and their associations into Copilot without switching tabs. A rep can ask for an account summary two minutes before a call and actually have time to read it.

Example prompts that map to this:

• "Show me my open deals closing this month, sorted by close date."
• "Which of my deals have had no activity in the last two weeks?"
• "Summarize everything on the [Company Name] account, open deals, key contacts, and recent engagement, before my call."
• "List my deals over $50k by stage so I can see where my pipeline is concentrated."
• "Who are the primary contacts associated with my three largest open deals?"
• "Compare this quarter's deals I've closed-won against the ones I lost and tell me what stands out."

Support

For support teams, this is a queue management tool as much as anything else. Reps can view their assigned tickets and sort by priority and creation date, which makes triaging the start of a shift considerably faster.

Example prompts:

• "Show my assigned tickets sorted by priority, then by creation date."
• "Which of my open tickets have been sitting the longest?"
• "Summarize the high-priority tickets assigned to me right now."
• "List tickets associated with [Company Name] and their current status."
• "How many open tickets do I have by priority level?"
• "Give me a rundown of tickets created in the last 24 hours that are still unresolved."

Customer Success

This is where the cross-record analysis really earns its keep. CS teams can compare resolution approaches and results across support channels to spot trends, the kind of pattern-finding that's genuinely tedious to do manually inside the CRM.

Example prompts:

• "Compare how our recent support tickets were resolved across channels and flag any patterns."
• "Summarize the open tickets and active deals for [Company Name] so I can prep for the renewal conversation."
• "Which of my accounts have multiple open tickets right now?"
• "Show me recent engagement across my book of business and highlight accounts that have gone quiet."
• "List the companies I own with deals closing this quarter, along with any open tickets."
• "Look across my accounts' tickets and tell me which issue types come up most often."

Use Cases by Role

Team-level prompts are a good starting point, but the real adoption win comes from tailoring this to specific roles. Here's how it breaks down further.

SDR / BDR (top of funnel, prospecting)

• "List contacts I own that aren't yet associated with a deal."
• "Which companies I'm working have more than one contact but no open deal?"
• "Summarize recent engagement on my newest contacts so I know who's warm."
• "Show my contacts by lifecycle stage so I can see who's ready to hand off."

Account Executive (managing active deals)

• "Show my open deals closing this month, sorted by close date."
• "Which of my deals have had no activity in the last two weeks?"
• "Summarize the [Company Name] account, open deals, key contacts, recent engagement, before my call."
• "Compare my closed-won deals this quarter against my closed-lost and tell me what stands out."

Account Manager (existing accounts, expansion)

• "List my accounts with deals closing this quarter plus any open tickets on them."
• "Which of my companies have gone quiet on engagement recently?"
• "Show me all deals associated with [Company Name], including past closed ones."
• "Summarize the health of my top five accounts by open deals and support activity."

Sales Manager (team oversight)

• "Show open deals across my team sorted by close date and flag the stalled ones."
• "Which deals over $50k are closing this month, and who owns them?"
• "Compare pipeline by stage so I can see where deals are piling up."
• "Summarize deals with no activity in the last two weeks across the team."

Support Rep / Tier 1 (own queue)

• "Show my assigned tickets sorted by priority, then creation date."
• "Which of my open tickets have been sitting the longest?"
• "Summarize my high-priority tickets right now."
• "How many open tickets do I have by priority level?"

Senior / Escalation Rep (complex tickets)

• "List my high-priority tickets and the companies they're associated with."
• "Summarize open tickets tied to [Company Name] and their status."
• "Which of my tickets are linked to companies that also have open deals?"
• "Give me a rundown of the oldest unresolved tickets in my queue."

Support Team Lead / Manager (queue oversight)

• "Show all open tickets across the team sorted by priority and age."
• "Which unresolved tickets were created in the last 24 hours?"
• "Compare how recent tickets were resolved across channels and flag patterns."
• "How is open ticket volume distributed by priority right now?"

CSM (renewals, account health)

• "Summarize open tickets and active deals for [Company Name] ahead of the renewal."
• "Which of my accounts have multiple open tickets?"
• "Show my accounts with deals closing this quarter alongside their ticket activity."
• "Highlight accounts in my book that have gone quiet recently."

Onboarding Specialist (new customers)

• "List my newly assigned accounts and their primary contacts."
• "Summarize open tickets for the companies I'm onboarding so I can spot early friction."
• "Which of my onboarding accounts have raised support tickets already?"
• "Show recent engagement across my new accounts."

CS Manager (portfolio oversight)

• "Compare ticket resolution approaches and outcomes across the team's accounts and flag trends."
• "Which accounts across the portfolio have both open tickets and deals closing soon?"
• "Show me which issue types come up most often across our accounts' tickets."
• "Summarize the accounts with the most open tickets right now."

A couple of things worth flagging for the manager and lead prompts specifically. Team-wide queries only work fully if the manager's own HubSpot permissions grant visibility into the team's records. If they don't, the manager will just get their own data back, which can be confusing the first time it happens. And as above, if Sensitive Data is turned on, the "gone quiet" and "recent engagement" style prompts will come back thin, since they rely on engagement data that Copilot can't reach in that configuration.

What's Coming Next: Federated Connectors

Worth a mention, even though it's a slightly separate path: Microsoft has also introduced federated connectors that use the Model Context Protocol, or MCP, to pull external data into Copilot in real time, without indexing it first. HubSpot is one of the systems available through this route.

Practically, this means HubSpot data can also show up as a source inside Copilot's Researcher and deep-research modes, and in general Copilot Chat, which is useful for research-style questions that need to blend CRM data with other work content, documents, emails, meeting notes, and so on, in a single answer. It's a newer and slightly different mechanism to the HubSpot Agent itself, but it points at the same direction of travel: your CRM data becoming more accessible from wherever your team already works.

A Couple of Practical Tips

If you're planning to roll this out, two things will make adoption smoother.

First, coach your team to be specific. Naming the object you want, deals, tickets, or contacts, along with the sort or filter you have in mind, is how the agent maps your request to the right CRM data. Vague prompts get vague answers.

Second, set expectations around permissions early. Because results are scoped to each user's existing HubSpot access, two people on the same team asking the same question can get different answers. That's by design, but it's worth explaining upfront so nobody assumes something's broken.

Should You Roll This Out?

If your team already has Microsoft 365 Copilot licensing, or is considering it, this is a genuinely low-lift addition. The setup is a single admin step plus a one-time sign-in per user, and the daily payoff, less tab-switching, faster answers, quicker meeting prep, adds up quickly across a sales floor or support team.

It's not a replacement for HubSpot itself, and it won't help you update records or build automation. What it does well is put the right CRM answer in front of the right person at the moment they need it, wherever they happen to be working.

If you're weighing whether this fits your team, or want help figuring out which roles would benefit most from which prompts, get in touch. We're happy to walk through it.