feat(agents): add Microsoft Teams bridge integration#2433
Draft
feat(agents): add Microsoft Teams bridge integration#2433
Conversation
Add AIAgentTeamsBridge proto message and wire it into the console UI as a new Integrations tab on the agent detail page. The tab exposes enable toggle, bot app ID, tenant ID, and client secret fields. When saved and enabled, the computed messaging endpoint URL is displayed for Azure Bot registration. Proto: AIAgentTeamsBridge message added to AIAgent (field 18), AIAgentCreate (field 15), and AIAgentUpdate (field 15).
…ndpoint The agent URL pattern is <id>.ai-agents.<cluster>.clusters.ign.rdpa.co. The old code only stripped the first subdomain, leaving ai-agents in place. Now we find the ai-agents segment and take everything after it as the cluster domain.
Contributor
|
The latest Buf updates on your PR. Results from workflow Buf CI / validate (pull_request).
|
Add optional OUTPUT_ONLY teams_bridge_endpoint field to AIAgent. The bridge controller populates this when it starts serving, so console just displays it -- no URL gymnastics needed.
malinskibeniamin
approved these changes
May 7, 2026
Contributor
malinskibeniamin
left a comment
malinskibeniamin
left a comment
There was a problem hiding this comment.
Seems a bit specific to put teams bridge in AI agent service but otherwise LGTM
The bridge expects a bare key (e.g. TEAMS_BOT_SECRET) that it
resolves directly from the secret store. The ${secrets.} template
pattern is for interpolation in deployment env vars, not for ref
fields read by external services.
Removes extractSecretName regex and SECRET_TEMPLATE_REGEX. Proto
validation updated to accept bare UPPER_SNAKE_CASE keys.
Contributor
Author
yeah that's fair. as per the design, it is a per agent configuration. Other systems, e.g. copilot studio do it the same way |
bot_app_secret_ref validation changed from ${secrets.X} pattern
to bare UPPER_SNAKE_CASE key. Regenerate pb.go and pb.ts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Add Microsoft Teams integration to the AI Agent system. New proto message, generated code, and an Integrations tab on the agent detail page.
Why
Users need to connect AI agents to Microsoft Teams for conversational interactions through a Teams bot. This requires configuring Azure Bot credentials on the agent side so the Teams bridge knows how to authenticate.
Implementation details
Proto
New
AIAgentTeamsBridgemessage with four fields:enabled,bot_app_id,bot_tenant_id,bot_app_secret_ref. The secret ref uses the same${secrets.NAME}template pattern as the existing provider API keys.Added as
teams_bridgetoAIAgent(field 18),AIAgentCreate(field 15), andAIAgentUpdate(field 15).UI
New Integrations tab on the agent detail page, positioned between Configuration and A2A. Contains a Microsoft Teams section with:
AI_AGENT)Update flow uses field masks targeting only
teams_bridge.*fields, so it won't interfere with other agent configuration.References
CRD struct:
AIAgentTeamsBridgein cloudv2