
The Managed Connector for Microsoft Teams is now part of Vercel Connect. According to Vercel’s changelog, it creates a Teams bot for an organisation and connects that bot to apps and agents running on Vercel.
People can @mention the bot in a Teams channel or send it a direct message. The project receives the message through a Connect trigger, runs the relevant code and replies as the bot.
How the Managed Connector for Microsoft Teams Works
Vercel handles registration of the Entra app and Azure Bot resource inside the organisation’s tenant. This means builders do not need to create and store a client secret for the bot. Tokens are also managed across the supported Vercel tools.
A tenant administrator with an Azure subscription completes the setup once. They can do this through the Vercel dashboard or Vercel CLI. The resulting connector can then be used by projects in the organisation.
- 1
Set up the connector
a tenant administrator starts setup from the dashboard or Vercel CLI
- 2
Register the bot
Vercel creates the Entra app and Azure Bot resource in the tenant
- 3
Connect the project
choose the supported SDK or adapter for the bot
- 4
Handle messages
receive verified Teams activities as Connect triggers and reply from code
Incoming Teams activities are verified before they reach the project. Connect then forwards them as triggers, giving the project code the message it needs to process and answer.
Three Ways to Use the Teams Bot
Projects can interact with the bot through the @vercel/connect SDK, an eve channel or the Chat SDK adapter. Each route connects the Teams conversation to code running through Vercel Connect, with credentials and tokens managed by the connector.
The same bot can receive channel mentions and direct messages. That supports both shared conversations in a team and one-to-one interactions without requiring separate bot registrations.
Frequently asked questions
What is the Managed Connector for Microsoft Teams in Vercel?
It is a Vercel Connect connector that creates a Teams bot for an organisation. It handles the Entra app and Azure Bot registration, verifies incoming Teams activities and forwards them to a project as Connect triggers.
Who can set up the Managed Connector for Microsoft Teams?
A tenant administrator with an Azure subscription must complete the setup. It only needs to be completed once and can be started from the Vercel dashboard or Vercel CLI.
Which Vercel plan includes the Managed Connector for Microsoft Teams?
The changelog does not name an eligible Vercel plan or a separate price. It confirms support through the Connect SDK, eve and the Chat SDK adapter.
Sources
3 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.






