How to Integrate Zendesk with Microsoft Teams (Step by Step)

But "connect Zendesk to Teams" actually covers two different things, and conflating them is the single biggest source of confusion. This guide walks through both, clearly separated, with verified step-by-step instructions for the main one. Every step below is checked against Zendesk's own documentation and Microsoft's app guidance as of June 2026 — Zendesk and Microsoft both revise their UI periodically, so confirm labels in your own account.

The two ways to connect Zendesk and Microsoft Teams

Before you touch a setting, get clear on which integration you actually want:

Most people searching for a "zendesk teams integration" want (a) — notifications plus ticket actions inside Teams. That is the main, fully supported product, so we cover it step by step first. We then cover (b) honestly, because Microsoft Teams is not a native Zendesk messaging channel and you deserve the real picture.

Before you start: what you'll need

A few prerequisites save you a mid-setup detour:

• A supported Zendesk plan. The Zendesk for Microsoft Teams integration is available on all Zendesk Suite tiers (Team, Growth, Professional, Enterprise, Enterprise Plus) and on Support Team, Professional, and Enterprise. It is not available on the entry-level Support Essential plan.
• Admin access on both sides. You need a Zendesk admin role and a Microsoft 365 / Teams admin who can approve the app's permissions in Microsoft Entra ID (formerly Azure AD). End users cannot self-install it — this almost always requires a quick handoff to whoever owns your Microsoft tenant.
• A decision on which Team and channels should receive notifications. You can add more later, but knowing your first target (say, an #urgent-support channel) makes the trigger step quick.

Part 1 — Install and set up the Zendesk for Microsoft Teams app

This is the integration that does the heavy lifting: ticket notifications into Teams, plus creating, viewing, commenting on, and updating tickets without leaving the chat client. According to Zendesk's documentation, the app lets you "create, view, and update Support tickets," "add internal notes and public replies to tickets within Teams," and "get notifications on tickets based on status, priority, type, and updates within any Team channel or DM."

Step 1 — Install the app

You can install from either side; they connect the same underlying integration:

1. From Microsoft Teams: open Apps in the left rail, search for Zendesk, and click Add.
2. From the Zendesk side: find the listing in the Zendesk Marketplace and follow the install prompt.

The Zendesk Marketplace is the integrations ecosystem where you discover and install the Teams app (alongside hundreds of others). It's worth a look so you know where the listing lives:

To be precise about what you're seeing: the screenshot above is the public Zendesk Marketplace homepage — the catalog where you find and install the Microsoft Teams app. The actual OAuth authorization and the channel/notification configuration happen afterward, inside the app's settings and inside Microsoft Teams itself (described below from the official docs — we don't fabricate Teams-side screenshots here).

Step 2 — Grant permissions (Microsoft admin consent)

After you add the app, Teams shows a welcome message with a Grant permissions action. Clicking it redirects you to Microsoft Entra ID (Azure AD) to accept the consent request for the app's permissions.

This is the step that catches teams out: depending on your tenant's policy, a Microsoft 365 / Teams admin may have to approve that consent — a regular agent can't push it through. If you hit a "your administrator must approve this app" wall, that's expected; loop in your IT/tenant admin to authorize it once for the organization.

Step 3 — Connect your Zendesk account (OAuth)

Next you link the app to your specific Zendesk instance:

1. Enter your Zendesk subdomain — the part before .zendesk.com in your URL (e.g. acme for acme.zendesk.com).
2. Authenticate with your Zendesk admin credentials to authorize the connection.

Behind the scenes, this OAuth handshake is what gives the app permission to read and write tickets in your account. Because it writes triggers and a webhook (next step), you must authorize it as an admin, not an agent.

Step 4 — Let Zendesk create its triggers and webhook

Here's the part you don't have to do manually but should understand. Once the app is installed and connected, Zendesk automatically creates a set of triggers and a webhook in your account. All of these triggers are named with the prefix [Microsoft Teams Integration], and — per Zendesk's docs — all of them, plus the webhook, are required to support both personal notifications and notifications coming into channels.

Practical implications:

• Don't delete or rename them. If notifications mysteriously stop later, the first thing to check is whether someone cleaned up these triggers or disabled the webhook (Admin Center → Apps and integrations → Webhooks, and Objects and rules → Business rules → Triggers).
• They sit alongside any triggers you've already built. If you're new to how triggers fire on ticket events, our Zendesk ticketing system explainer covers the underlying model.

Step 5 — Add the app to a Team and set up channel notifications

Now you decide where ticket activity shows up. The app has to be added to the relevant Team/channel first — by the team owner or a Zendesk admin — and then notifications are configured inside Teams:

1. In the target channel, type @Zendesk in the message/command box to bring up the app's command menu.
2. Choose the notifications command (you can also just type notifications).
3. Configure which events post to that channel — you can filter by ticket status, priority, type, and field updates, and direct different events to different channels or DMs.

A common, effective pattern: route high-priority ticket events to a dedicated #urgent-support channel for immediate visibility, while routine updates only ping the assigned agent as a personal notification. Note that only admins and agents can manage notifications in a channel — end users can't reconfigure them.

Step 6 — Create and manage tickets from Teams

With the app live, your team can work tickets without switching apps. From Teams you (and internal requesters) can:

• Create a ticket from a Teams message or via the app's compose action.
• View open and closed personal tickets in a single list.
• Add internal notes and public replies, and update ticket fields like status or priority.
• Import Zendesk ticket views as tabs in a Teams workspace to list tickets by different criteria (this one is agents only).

This is exactly what makes the integration double as an internal IT helpdesk front end: an employee pings a request, an agent turns it into a tracked ticket, and the whole thread stays visible in Teams.

Step 7 — Turn on Answer Bot for self-service (optional)

The app can surface AI-powered article recommendations ("Answer Bot for Microsoft Teams") so common questions get a self-service answer inside the channel before an agent is pulled in. One honest caveat from the docs: this doesn't work out of the box — you have to activate Answer Bot separately in your Zendesk Admin Center and point it at your knowledge base. If your help center is thin, the recommendations will be too.

Step 8 — Test the full loop

Before you announce it, run the round trip yourself:

1. Trigger a notification. Create or update a ticket that matches a condition you configured (e.g. set priority to Urgent) and confirm it posts to the right channel.
2. Create a ticket from Teams and verify it appears in Zendesk with the right requester.
3. Reply from Teams and confirm the public reply/internal note lands on the ticket.
4. Test Answer Bot (if enabled) by asking a question your knowledge base should answer.

If a notification never arrives, 90% of the time it's the auto-created triggers/webhook being disabled, the app not added to that channel, or the event not matching your notification filter.

Part 2 — Using Teams as an inbound channel (the honest version)

Now the second meaning of "integrate Zendesk with Teams": letting people message your support through Teams and have it land as a ticket — the internal IT/employee-helpdesk scenario, where Teams is the front door instead of a web widget.

Here's the part most guides gloss over: Microsoft Teams is not a native Zendesk messaging channel. In Admin Center, native conversational channels live under Channels → Messaging and social, and the supported social messaging options are things like WhatsApp, Facebook Messenger, Instagram, Apple Messages for Business, LINE, Telegram, Viber, and WeChat (delivered via Sunshine Conversations). Microsoft Teams is not on that list — there's no one-click "Add Teams" channel toggle. (If you're new to setting up those native channels, our guide to setting up Zendesk messaging walks through the Messaging and social path.)

So how do teams actually get a "Teams → ticket" experience? Two real options:

• Use the Zendesk for Teams app from Part 1. For internal IT/employee support, this is the practical channel: employees raise and track tickets directly in Teams, get Answer Bot recommendations, and agents work them as normal tickets. For most internal helpdesks, this is the right and supported answer — no custom build required.
• Build a custom channel with Sunshine Conversations. If you need true conversational messaging where a Teams chat becomes a live ticket thread, that requires a custom integration via Sunshine Conversations (Zendesk's messaging platform / API), or a third-party connector. This is a developer project, not a setting — budget for it accordingly.

Being straight about it: if a vendor or blog implies you can flip Teams on as a customer-facing messaging channel in two clicks like WhatsApp, that's not accurate today. For internal IT, the app covers it; for a custom conversational channel, you're in Sunshine Conversations territory.

Bonus — Microsoft Teams in side conversations (agent collaboration)

There's a third, separate connection worth knowing about because it's easy to confuse with the above. Agents can loop in colleagues over Teams from inside a ticket using side conversations. A reply in the Teams thread is automatically recorded back on the ticket, and "anyone in the Microsoft Teams channel can view your message and reply to the thread directly, without logging into Zendesk Support."

This is agent-to-agent collaboration, not a customer channel. It requires Suite Professional or above (or the Collaboration add-on on Support Professional+), plus the latest Zendesk for Teams app installed. You enable it in Admin Center → Workspaces → Agent tools → Side conversations → Turn on side conversations in Microsoft Teams.

Permissions and limitations to know

Worth setting expectations before you roll it out:

• Admin permissions on both platforms. You need a Zendesk admin and a Microsoft 365/Teams admin to consent. End users can't self-install.
• No bots in private channels. Teams itself doesn't support bots in private channels, so the app's notifications/commands won't work there — use standard channels.
• Direct messages aren't natively supported as a Teams feature for the integration. A documented workaround is to create a channel with a single member if you want "DM-like" personal delivery.
• Answer Bot isn't automatic — activate it separately in Zendesk.
• The auto-created triggers/webhook are load-bearing. Don't delete the [Microsoft Teams Integration] triggers or the webhook, or notifications break.
• Plan floor: Suite (any tier) or Support Team and above — not Support Essential.

Where AI fits in

If your reason for connecting Teams to Zendesk is an internal IT or employee helpdesk, here's the pattern worth noticing: the questions employees ask over Teams are extremely repetitive — "how do I reset my VPN," "request a license for X," "I'm locked out of my account." The Zendesk for Teams app plus Answer Bot can suggest an article, but suggesting an article isn't the same as resolving the request.

That's the layer an AI agent like Macha adds. Macha isn't a help desk and it's not a Zendesk replacement — it runs on top of your existing Zendesk. For the repetitive internal questions, it reads what the employee actually asked, pulls from your connected knowledge base and past tickets, and resolves the common ones before a human is pinged, escalating with full context when it isn't confident. You can read how that works on Macha for Zendesk.

The honest framing: it's another integration to configure, and it's only as good as the knowledge you connect to it. On cost, Macha bills per AI action — any automated step it takes, like drafting a reply, tagging, or resolving — not per closed ticket, because most automation is work done along the way, not a tidy "resolution." If your Teams helpdesk volume is mostly questions your knowledge base could answer, that's the line where article suggestions stop scaling. You can try it free — 7-day free trial, no credit card required.

Frequently asked questions

What does the Zendesk Microsoft Teams integration actually do? The official Zendesk for Microsoft Teams app posts ticket notifications into Teams channels or DMs (filtered by status, priority, type, and updates) and lets people create, view, comment on, and update Zendesk tickets directly from Teams. It can also surface Answer Bot article recommendations for self-service.

How do I install the Zendesk app in Microsoft Teams? In Teams, open Apps, search for Zendesk, and click Add (or install it from the Zendesk Marketplace). Then click Grant permissions to approve it in Microsoft Entra ID (Azure AD) — a Microsoft admin may need to consent — enter your Zendesk subdomain, and authenticate with your Zendesk admin credentials.

Do I need admin access to set it up? Yes, on both sides. You need a Zendesk admin and a Microsoft 365/Teams admin (for the permission consent). End users cannot self-install the app.

How do I set up Zendesk ticket notifications in a Teams channel? After the app is added to the channel, type @Zendesk to open its command menu, choose the notifications command, and pick which ticket events (by status, priority, type, or field updates) post to that channel. Only admins and agents can manage these notifications.

Can customers message my support through Microsoft Teams and create tickets? Not as a native messaging channel — Microsoft Teams isn't in Zendesk's native Messaging and social channel list (WhatsApp, Messenger, Instagram, etc.). For an internal IT/employee helpdesk, the Zendesk for Teams app already lets staff raise and track tickets in Teams. For a true custom conversational channel, you'd build one via Sunshine Conversations.

Which Zendesk plans support the Teams integration? All Zendesk Suite tiers (Team, Growth, Professional, Enterprise, Enterprise Plus) and Support Team, Professional, and Enterprise. It is not available on Support Essential.

Why did my Teams notifications suddenly stop? Most often because the integration's auto-created triggers (named [Microsoft Teams Integration]) or its webhook were disabled or deleted in Zendesk, the app was removed from the channel, or the ticket event no longer matches your notification filter. Note that bots don't work in Teams private channels.

The bottom line

A Zendesk Teams integration means one of two things, so name yours first. For the common case — notifications and ticket actions inside Teams — install the official Zendesk for Microsoft Teams app from the Teams app store or Marketplace, grant the Microsoft consent, connect your subdomain via OAuth, let Zendesk create its [Microsoft Teams Integration] triggers and webhook, add the app to a channel, set up notifications with @Zendesk → notifications, and test the loop. For an internal IT helpdesk, that same app is your practical Teams-as-channel answer; a true customer-facing Teams messaging channel isn't native and means a Sunshine Conversations build. And remember side conversations are a separate, agent-only collaboration feature. Get those distinctions right and the setup is straightforward.

Setup steps verified against Zendesk's and Microsoft's official documentation, June 2026. Both products update periodically — confirm labels in your own account before relying on them.