Microsoft Teams

How Horizon reaches Microsoft Teams — agent conversations through the Horizon bot, and channel notifications through an incoming webhook.

Horizon reaches Microsoft through Microsoft Teams, in two separate ways: agents can hold conversations in Teams, and notifications can be delivered to a Teams channel.

Neither route works like the OAuth connections elsewhere in this section. Teams is not something you authorize per organization from the Connections page, so most of what you read about connecting Salesforce or Google does not transfer here.

Agent conversations in Teams

An agent can be deployed to Teams the same way it can be deployed to Slack: you choose Teams as its messaging platform when you deploy it, and give it the channel to work in.

What makes Teams different is the bot behind it. Horizon operates one Microsoft bot application shared by every customer, rather than installing a separate app into each tenant. That has two consequences worth knowing:

• There is nothing to authorize inside Horizon. No OAuth redirect, no consent screen, no per-organization Microsoft credentials.
• Your own Teams or Azure administrator does the enabling, by permitting the Horizon bot in your tenant. That is an action in Microsoft’s admin tooling, not in Horizon.

If agents deployed to Teams are not receiving or sending messages, that permission is the first thing to check.

Notifications to a Teams channel

Horizon can also post notifications into a Teams channel. This route is unrelated to the bot: you create an incoming webhook on the Teams channel, copy the URL Microsoft gives you, and paste it into Horizon as a notification destination.

Horizon accepts webhook URLs only on Microsoft’s own hosts, so a URL from anywhere else is rejected. The URL is stored encrypted.

This is a one-way channel — Horizon posts to it, and nothing comes back. Use it for alerts rather than conversation.

Which one do you want?

You want	Use
An agent that reads and replies in a Teams channel	Deploy the agent with Teams as its messaging platform
Alerts and system notifications posted to a channel	An incoming webhook notification destination
Mail, files, calendars, or SharePoint	Not available — Horizon has no Microsoft Graph integration

Troubleshooting

Issue	Resolution
Agent deployed to Teams but silent	Confirm your Teams or Azure administrator has permitted the Horizon bot in your tenant, and that the agent has a channel set.
Notifications not arriving	Re-copy the incoming webhook URL from the Teams channel; a regenerated webhook invalidates the old URL.
Webhook URL rejected	Horizon only accepts Microsoft’s own webhook hosts. Check you copied the URL Teams generated, in full.
Looking for Outlook or OneDrive	Not supported. There is no Microsoft Graph integration to build on.