What This Update Actually Is
HubSpot shipped three distinct improvements to the Microsoft Teams integration in late June 2026. None of them are flashy AI announcements. All three are fixes to real operational gaps that frustrated the humans running go-to-market teams every single day.
Here's exactly what shipped:
- Individual user notifications in workflows: You can now target a specific Microsoft Teams user as the recipient of a workflow notification, not just a channel. This works across any HubSpot object type, including contacts, companies, deals, tickets, and custom objects.
- Multi-participant call logging: When a Teams phone call includes more than one participant, HubSpot now logs that call and associates it with every relevant CRM record. Previously, only single-participant calls were captured.
- Admin-level installation upgrade: If your portal is connected through a user-level Teams app, you can now upgrade to admin-level installation directly from integration settings. No disconnect. No reinstall.
Why HubSpot Shipped This
The external problem is straightforward: Microsoft Teams is embedded in how most mid-market and enterprise teams communicate. If HubSpot can't route information precisely into Teams, sales and service workflows break down at the handoff point.
The internal frustration is more specific. Admins have told us this pattern directly: they set up a Teams notification workflow, it fires to a channel, the right rep never sees it because the channel has 40 posts a day. Or a sales call wraps up with four participants on the line, and only one contact gets the activity logged. The call record doesn't reflect what actually happened.
The installation gap hurt in a different way. Many portals started with a user-level Teams connection because someone wanted to test it quickly. Upgrading to admin-level meant fully disconnecting, losing configuration, and asking IT to reinstall. That friction kept portals stuck on a less capable setup.
How to Use It Step by Step
Individual User Notifications
- Open HubSpot Workflows and create or edit a workflow for any object type.
- Add the "Send Teams notification" action.
- In the recipient field, choose "Specific Teams user" instead of a channel. Search by name or email.
- Finish building your message and save. The notification will go directly to that individual's Teams inbox.
Multi-Participant Call Logging
- Confirm your Microsoft Teams phone integration is active under Settings > Integrations > Connected Apps.
- Run a Teams phone call with multiple participants. HubSpot will automatically detect all participants and log the call against each associated CRM record.
- Review the logged call on each participant's contact or company record. Verify the association is correct and add notes if needed.
Admin-Level Installation Upgrade
- Go to Settings > Integrations > Connected Apps and open the Microsoft Teams integration.
- If you're on a user-level installation, you'll see an option to upgrade to admin-level. Click it.
- An admin in your Microsoft 365 tenant will need to approve the permissions request. Coordinate with IT before starting.
- Once approved, your integration upgrades in place. Your existing configuration stays intact.
What It Touches in Your HubSpot Strategy
This update ripples into more of your portal than it might look like at first glance. Let's break it down by area.
Workflows and Automation
The individual user notification change matters most for revenue ops teams that route work in real time. Deal stage changes, ticket escalations, task assignments: all of these can now ping the exact person responsible rather than a channel that may or may not get attention. This pairs well with the broader trend of smarter CRM notification improvements HubSpot has been shipping across the platform.
Key Takeaway
Routing workflow notifications to individual Teams users instead of shared channels can meaningfully reduce response time on time-sensitive records like high-value deals or escalated service tickets.
CRM Data Integrity
Multi-participant call logging is a data quality improvement. When four humans are on a call and only one gets the activity logged, your CRM tells an incomplete story. Reporting breaks. Sequence logic breaks. Rep handoff notes miss context. Fixing this keeps your call data honest across every associated record.
If you're managing a complex team setup, this also connects to how you structure your HubSpot users and teams overall. A clean installation and well-structured team hierarchy makes the individual-user notification feature much more useful from day one. The recent user import update that added team and seat support is worth reviewing if you haven't set that up yet.
Sales and Service Processes
Sales Hub and Service Hub teams using Teams for calls will feel the call logging change immediately. Account executives running multi-stakeholder calls, customer success managers on renewal conversations, support reps handling escalations: all of them get more accurate activity records without changing anything in their workflow.
Key Takeaway
The admin-level installation upgrade is a one-time fix with compounding value. Admin-level connections unlock more permissions and more stable sync behavior, which means fewer integration errors and more reliable automation down the line.
Reporting
Call activity reports and contact engagement reports will become more accurate as multi-participant logging fills in gaps that previously went unrecorded. If you're tracking call volume by rep, call-to-close rates, or engagement scores, this update quietly makes those numbers more trustworthy.
Who Should Care Most
This update matters most to three specific groups.
- Revenue ops leaders at companies where Microsoft Teams is the primary communication tool. The individual notification routing gives you precision you didn't have before.
- Sales managers running multi-stakeholder deal cycles. Group calls with procurement, legal, and end users can now all be logged against the right contacts and companies automatically.
- HubSpot admins who set up a user-level Teams connection early and never upgraded. The path to admin-level is now frictionless, and the stability improvement is worth ten minutes of your time.
Companies running Service Hub Professional or Enterprise with a high volume of customer calls will also see immediate value from the multi-participant logging fix. This isn't a niche use case. Most real support calls involve more than one person.
George's Take
I've audited a lot of HubSpot portals where Teams is connected but barely doing anything useful. The integration was technically live, but workflows were still routing to channels nobody watched, call records were missing half the participants, and the admin was afraid to touch the installation because reconnecting felt risky. This update fixes all three of those in one shot. It's not the sexiest release HubSpot has shipped this year, but it's the kind of thing that makes an integration actually reliable instead of theoretically useful. Don't sleep on the admin upgrade especially. A stable, admin-level connection is the foundation everything else sits on.
“A stable admin-level Teams connection is the foundation everything else sits on. This update finally makes that upgrade frictionless, and that matters more than most people realize.”
If you want to know whether your Teams integration is set up correctly or if your HubSpot workflows are routing the right way, we can take a look. Book a strategy call with the Sidekick team and we'll show you exactly what to fix and in what order.
Frequently Asked Questions
Can I send a HubSpot workflow notification to a specific Microsoft Teams user?
Yes. As of June 2026, you can select a specific Microsoft Teams user as the notification recipient inside a HubSpot workflow's 'Send Teams notification' action. This works across any HubSpot object type, including contacts, deals, tickets, companies, and custom objects. Previously, notifications could only go to a channel.
Does HubSpot log Microsoft Teams calls with multiple participants?
Yes. HubSpot now logs multi-participant Microsoft Teams phone calls and associates the call record with all relevant CRM records. Previously, only single-participant calls were supported, which left gaps in call history for group sales calls, multi-stakeholder demos, and team support conversations.
How do I upgrade my Microsoft Teams integration from user-level to admin-level in HubSpot?
Go to Settings, then Integrations, then Connected Apps, and open the Microsoft Teams integration. If you're on a user-level installation, you'll see an in-place upgrade option. You'll need a Microsoft 365 admin to approve the new permissions. Your existing configuration won't be lost during the upgrade.
Which HubSpot plans include the updated Microsoft Teams integration features?
The updated Teams features are available on Professional and Enterprise tiers across most HubSpot hubs, including Sales Hub, Service Hub, Marketing Hub, Content Hub, Data Hub, Commerce Hub, and Smart CRM. Check HubSpot's product updates page for the full tier breakdown specific to your hub.
Will the multi-participant call logging in HubSpot affect my sales reports?
Yes, in a positive way. Multi-participant call logging fills in previously missing activity records, which improves the accuracy of call volume reports, engagement scores, and call-to-close rate data. If you were tracking rep call activity before, your numbers will become more complete going forward.
What is the difference between a user-level and admin-level Microsoft Teams installation in HubSpot?
A user-level installation connects Teams to HubSpot for one individual user. An admin-level installation connects at the organizational level, enabling broader permissions, more stable sync behavior, and access to features like organization-wide call logging. Admin-level is the recommended setup for teams, not just individuals.
