Vercel Connect adds managed Microsoft Teams connector for apps and agents

Vercel Connect adds Microsoft Teams support

Vercel has launched a managed Microsoft Teams connector for Vercel Connect. According to the Vercel blog, creating a connector provisions a Teams bot for your organization, and your apps and agents run behind it. People can @mention the bot in channels or message it directly; the message is delivered to your code, which can then reply as the bot.

What the managed connector covers

The notable part is what Vercel takes off the developer's plate. When you create a connector, Vercel registers the Entra application and the Azure Bot resource in your own tenant, so there is no client secret for your team to store. Setup is completed once by a tenant administrator who has an Azure subscription. After that, incoming Teams activities are verified and forwarded to your project as Connect triggers, arriving like any other event your code responds to.

Creating a connector and replying to messages

Connectors can be created from the Vercel dashboard or through the CLI. Vercel's example creates a connector named acme-teams with triggers enabled:

vc connect create microsoft-teams --name acme-teams --triggers

On the code side, your application requests a token only when it actually needs one, rather than holding long-lived credentials. Tokens are used with the @vercel/connect SDK, the eve channel, or a Chat SDK adapter, and let your code reply to a forwarded Teams message through the Bot Framework API. Vercel says each token is scoped to what was requested and refreshed automatically, which removes manual rotation from the operational checklist.

Access is also bounded. Connectors only work in the environments they are attached to, and tokens can be revoked at any time with the vc connect revoke-tokens command.

Why it matters

Building a Teams bot the traditional way means wrestling with Azure portal registrations, bot resource provisioning, client secrets and token lifecycles before a single message flows. Vercel's connector collapses that into one CLI command plus a one-time administrator sign-off, which lowers the barrier for teams that want to expose internal tools or agents where their colleagues already work.

The design also fits the broader shift toward agents. Instead of building a dedicated chat interface for an agent, teams can let it live inside Teams, respond to @mentions in channels, and carry credentials that are scoped, automatically refreshed and revocable. For organizations standardized on Microsoft 365, that turns Vercel-hosted apps into participants in existing conversations rather than separate destinations users have to visit.

There are reasonable caveats. Setup requires an Azure subscription and a tenant administrator, so individual developers cannot spin connectors up entirely on their own — though that governance is partly the point. And because the connector is a managed abstraction over the Bot Framework, teams with unusual Teams requirements may still need to drop down to Azure's own tooling.

Overall, the release positions Vercel Connect less as a hosting feature and more as a distribution layer: the same platform that runs your code now also handles the identity, verification and messaging plumbing needed to put that code in front of users inside Microsoft Teams.