Managed Microsoft Teams Connector for AI Agents
On September 21, 2026, Vercel announced two major technical updates to its platform: a managed connector for Microsoft Teams on Vercel Connect, and detailed visibility into billable duration and CPU minutes for each deployment.
According to Vercel, the new Microsoft Teams connector enables organizations to run bots or AI agents for internal workflows. Once configured, team members can @mention the bot in channels or send direct messages; the application code then receives the event and responds as the bot. As a managed connector, Vercel automatically provisions the Entra application and Azure Bot resources directly within the organization's tenant. Initial setup requires a one-time configuration by a tenant administrator with an Azure subscription, completely eliminating the need to store client secrets in the project. Incoming activities from Microsoft Teams are pre-authenticated before being forwarded to the project as Connect triggers.
Developer Integration and Security Controls
Developers can initialize the connector via the Vercel Dashboard or the Vercel CLI. In production, applications request tokens only on demand through the @vercel/connect SDK, event streams, or Chat SDK adapters. Each token is strictly scoped to the required permissions and rotated automatically, removing the overhead of manual key rotation. The connector only operates within designated environments, and administrators can revoke access at any time using the vc connect revoke-tokens command.
Granular Billable Duration and CPU Minute Metrics
In the second update, Vercel introduced billable duration and CPU minutes to the dashboard, the vc inspect CLI command, and the REST API. This update is designed to give engineering teams complete visibility into infrastructure resource consumption for every build. Vercel defines billable duration as the total build and post-build runtime combined, rounded up to the nearest full minute. CPU minutes are calculated by multiplying the billable duration by the vCPU count of the execution machine. To inspect this breakdown from the command line, developers can update their CLI to version 59.23.1 or later using npm i -g vercel@latest before running vc inspect.