最新资讯
dev.to 我们在 DolphinBench 上测试记忆检索:纯关键词搜索暴露了自身回归 dev.to 别再把 Agent 写成 while 循环,把它建模为状态机 bloomberg.com Rightmove 与 Scout24 借 AI 产品应对低迷房市并上调展望 stackoverflow.blog 欢迎来到芯片时代:半导体制造、AI 数据中心与芯片设计的未来 www.youtube.com AI Agent 总犯同样的错:CentralAgent AI 将记忆重构为经验系统 pub.towardsai.net Netflix 科学家建议重采样 LLM 评判:5 次仅将误差棒缩小 13% pub.towardsai.net Jev 作为 LLM 前的静默层:构建提示感知的模型路由器 reddit.com OpenAI 称 Astra 仅满足 10% 安全任务标准 dev.to FreeToken:在自有 GPU 上运行前沿 MoE 模型及其内存需求 dev.to 当 AI Agent 说“完成”时,究竟完成了什么? dev.to 部署 Underdog Bark 3.0 Pro:逐字转写、自定义后端与分块设置 dev.to 为艰难对话构建 AI:五个 Agent、一条安全正则与一位盲评监督者
多元动态
登录 注册
智能体 vercel.com · @Vercel News

Vercel Connect 新增 Microsoft Teams 托管连接器

原文 我的收藏

Vercel 在 changelog 中宣布 Vercel Connect 支持 Microsoft Teams 托管连接器。创建后组织会获得一个由应用和 Agent 驱动的 Teams 机器人,用户可在频道 @ 提及或私聊,代码接收消息并以机器人身份回复。作为 Vercel Managed Connector,Vercel 会在租户内注册 Entra 应用和 Azure Bot 资源,因此无需存储 client secret,具备 Azure 订阅的租户管理员完成一次性设置即可;传入的 Teams 活动经校验后作为 Connect trigger 转发到项目。可通过 dashboard 或 Vercel CLI 创建,配合 @vercel/connect SDK、eve channel 或 Chat SDK 适配器使用,令牌按请求范围签发并自动刷新,可用 vc connect revoke-tokens 撤销。

AI推荐理由 Vercel 官方 changelog 发布 Connect 新增 Microsoft Teams 托管连接器,具体说明由 Vercel 在租户内注册 Entra 应用与 Azure Bot 资源、无需存储 client secret、Teams 活动经校验后作为 Connect trigger 转发到项目,并提供 @vercel/connect SDK、eve channel 与 Chat SDK 适配器及按需令牌与撤销命令。信息密度高、来源为官方一手,对构建 Teams 内 Agent/机器人的开发者有直接落地价值;局限是仅覆盖 Teams 单一渠道,未给出性能或规模数据。

72

正文

[Vercel Connect](https://vercel.com/docs/connect) now includes a managed connector for [Microsoft Teams](https://vercel.com/connect/microsoft-teams). Creating one gives your organization a Teams bot that your apps and agents run. People can @mention it in channels or message it directly, and your code receives the message and replies as the bot. As a [Vercel Managed Connector](https://vercel.com/docs/connect/concepts/connectors), Vercel registers the Entra app and Azure Bot resource in your tenant, so there's no client secret to store. A tenant administrator with an Azure subscription completes setup once. Incoming Teams activities are verified and forwarded to your project as [Connect trigger](https://vercel.com/docs/connect/concepts/triggers). Create a connector from the [dashboard](https://vercel.com/d?to=%2F%5Bteam%5D%2F~%2Fconnect) or [Vercel CLI](https://vercel.com/docs/cli/connect): Once the connector is set up, your code requests a token only when it needs one. Use it with the [@vercel/connect](https://vercel.com/docs/connect/ts-sdk-reference) SDK, [eve](https://vercel.com/docs/connect/frameworks/eve) channel or [Chat SDK](https://vercel.com/docs/connect/frameworks/chat-sdk) adapter: Each token is scoped to what you request and refreshed automatically, so there's nothing to rotate by hand. Connectors only work in the environments you attach them to, and you can revoke access at any time with `vc connect revoke-tokens`. Read the [Vercel Connect documentation](https://vercel.com/docs/connect), view details about the [Teams connector](https://vercel.com/connect/microsoft-teams) in the Vercel Connect catalog, or [create a Teams connector](https://vercel.com/d?to=%2F%5Bteam%5D%2F~%2Fconnect%2Fcreate%3Ftype%3Dmicrosoft-teams) to get started. [Read more](https://vercel.com/changelog/vercel-connect-microsoft-teams)

来源报道 · 1 篇 · 以下链接均前往原始媒体

← 返回精选动态 原文

更多内容