Set Up Teams Connector
An authenticated connection to Microsoft Teams so your agent can post updates, reply to threads, and read channel messages. Learn more → Send Notifications. Time: ~5 minutes.
Your agent has one of two Teams connector experiences depending on its configuration:
- Connector Gateway-enabled agents — You see Microsoft Teams in the connector picker. After signing in, you configure which Teams tools (post, reply, read) your agent can use. The target channel is specified per message at runtime, so your agent can post to any channel the signed-in user can access. Follow the steps below.
- Legacy connector agents — You see Send notification (Microsoft Teams) in the connector picker. After signing in, you paste a Teams channel link and select a managed identity. This configures a single default channel. See Legacy "Send notification" setup below.
If you are unsure which you have, click Add connector and look at the connector picker — the label tells you.
Prerequisites
- An agent created in the Azure SRE Agent portal
- A Microsoft Teams account with access to the target channel
- SRE Agent Administrator role on the agent (auto-granted to the agent's creator; required for anyone else to manage connectors). See User roles.
- Owner role on the agent's resource group, or a custom role with
Microsoft.Web/connections/writeandMicrosoft.Authorization/roleAssignments/writepermissions on the resource group
Step 1: Navigate to Connectors
- Open your agent in the Azure SRE Agent portal
- In the left sidebar, expand Builder
- Select Connectors
Step 2: Add a Teams connector
- Click Add connector in the toolbar
- In the connector picker, select Microsoft Teams
- Click Next
Your agent can have one Teams connector at a time. If a connector already exists, the card is disabled with the message "Your agent can only have one Teams connector."
Step 3: Sign in to Microsoft Teams
- Wait for the permission check to complete
- Click Sign in to Microsoft Teams
- Complete the OAuth authentication in the popup window
- On success, you'll see a Connected as card showing your email address with a green checkmark
Checkpoint: Green checkmark with your email address visible. If you see a permissions warning, verify you have Owner on the resource group (or a custom role with Microsoft.Web/connections/write and Microsoft.Authorization/roleAssignments/write).
If the authentication dialog doesn't appear, check that your browser isn't blocking popups from sre.azure.com.
Step 4: Enable Teams tools
After signing in, you see a list of Teams operations your agent can perform. Each tool has an Allow / Ask / Deny setting:
| Tool | What it does | Recommended |
|---|---|---|
| PostMessageToConversation | Post a new message to a Teams channel | Allow |
| ReplyWithMessageToConversation | Reply to an existing thread | Allow |
| GetMessagesFromChannel | Read recent channel messages | Allow |
| GetAllTeams | List teams the signed-in user belongs to | Allow |
| GetChannelsForGroup | List channels in a specific team | Allow |
| GetUnifiedActionSchema | Build the required body schema for post, reply, and card operations | Allow |
| PostCardToConversation | Post an Adaptive Card to a Teams channel | Optional |
| UpdateCardInConversation | Update an existing Adaptive Card | Optional |
Enable the tools your agent needs. At minimum, enable PostMessageToConversation to send notifications, GetUnifiedActionSchema to build the message body, and GetAllTeams + GetChannelsForGroup so the agent can find the right channel.
Step 5: Save the connector
- Click Next to proceed to the Review + add step
- Verify your connector details
- Click Add connector to create the connector
Checkpoint: A toast notification confirms the connector was created successfully. Your connector appears in the connectors list.
Step 6: Test your Teams connector
Ask your agent:
Post to the General channel in [Your Team Name]: "SRE Agent is connected and ready for notifications"
Your agent uses the discovery tools to find the team and channel, then posts the message as HTML.
Checkpoint: The agent shows a tool card confirming the message was posted. Check your Teams channel to verify the message appeared.
Prefer a default channel with agent instructions
The current Teams connector does not store or enforce a default channel. The target channel is specified per message, which means your agent can post to any channel the signed-in user has access to.
To avoid specifying the channel every time, open Builder > Agent Canvas, select the agent that will post to Teams, select Edit, and add the preferred team and channel under Instructions. For example:
Always post Teams notifications to the "Incidents" channel in the "SRE Team" team
unless I specify a different channel.
This is a routing preference only, not an access-control boundary. The connector can still post to other channels that the signed-in user can access.
For automation scenarios (scheduled tasks, incident response), you can include the team group ID and channel ID directly in the task or response plan instructions so the agent skips the discovery step.
What your agent can do with Teams
| Tool | What it does |
|---|---|
| Post message | Send a message to any Teams channel |
| Reply to thread | Continue an existing conversation thread |
| Get messages | Read recent messages from a channel |
| Post card | Send an Adaptive Card to a channel when PostCardToConversation is enabled |
| Update card | Update an existing Adaptive Card in place when UpdateCardInConversation is enabled |
Teams messages are formatted as HTML. Your agent handles this formatting automatically when composing messages.
Edit or remove the connector
Edit
- In the connectors list, click the ⋯ (more actions) menu on the Teams connector row
- Select Edit connector
- The edit dialog opens — you can re-authenticate, change tool permissions, or toggle the Add "Powered by Azure SRE Agent" footer to messages checkbox
- Click Save
Delete
- Click ⋯ on the connector row → Delete connector, or select the checkbox and click Remove in the toolbar
- Confirm the deletion
After deleting, your agent can no longer post to Teams. You can add a new Teams connector at any time.
Legacy "Send notification" setup
Some agents show Send notification (Microsoft Teams) in the connector picker instead of Microsoft Teams. This is the legacy connector that configures a single default channel and managed identity during setup.
Legacy setup steps (click to expand)
Additional prerequisites (legacy only):
- A Teams channel URL (you'll get this during setup)
- A managed identity configured on the agent
Step 2 (legacy): Add the connector
- Click Add connector in the toolbar
- In the connector picker, select Send notification (Microsoft Teams)
- Click Next
Step 3 (legacy): Sign in — Same as Step 3 above.
Step 4 (legacy): Paste Teams channel link
- In Microsoft Teams, right-click the target channel and select Get link to channel
- Copy the channel URL
- Back in the connector setup form, paste the URL into the Teams channel link field
The URL should look like:
https://teams.microsoft.com/l/channel/19%3A...%40thread.tacv2/channel-name?groupId=...
The form automatically extracts the channel ID and group ID from this URL.
Below the channel link, a checkbox labeled Add "Powered by Azure SRE Agent" footer to messages is enabled by default. Uncheck this option if you prefer messages without the footer.
Step 5 (legacy): Select managed identity and save
- From the Managed identity dropdown, select a managed identity (system-assigned or user-assigned)
- Click Next to proceed to the Review + add step
- Verify your connector details
- Click Add connector to create the connector
Step 6 (legacy): Test
Ask your agent: "Post to our Teams channel: SRE Agent is connected and ready for notifications"
Legacy tools:
| Tool | What it does |
|---|---|
| Post message | Send a message to the configured default channel |
| Reply to thread | Continue an existing conversation thread |
| Get messages | Read recent messages from the channel |
What you learned
- How to add a Teams connector using OAuth
- How to enable Teams tools for your agent
- How to verify the connector by posting a test message
- How to prefer a default channel using agent instructions
- What Teams tools become available to your agent
Troubleshooting
| Issue | Solution |
|---|---|
| I see "Microsoft Teams" instead of "Send notification" | This is the current connector experience — follow the main steps in this guide. The "Send notification" option is the legacy connector. |
| I see "Send notification" instead of "Microsoft Teams" | Your agent uses the legacy connector. See Legacy setup. |
| Permissions warning | Grant Owner on the resource group, or assign a custom role with Microsoft.Web/connections/write and Microsoft.Authorization/roleAssignments/write permissions. |
| OAuth popup blocked | Allow popups from sre.azure.com in your browser settings |
| Message doesn't appear in channel | Verify the signed-in account has access to the target channel |
| Agent can't find my team or channel | Enable GetAllTeams and GetChannelsForGroup tools on the connector |
| Channel link not accepted (legacy) | Ensure the URL is from Get link to channel in Teams, not a meeting or chat link |
| No managed identities in dropdown (legacy) | Click Add identity to configure one in the Azure portal, then click the refresh button |
Related
| Resource | What you'll learn |
|---|---|
| Send Notifications → | How your agent uses Outlook and Teams for contextual notifications |
| Set Up Outlook Connector → | Connect Outlook for email notifications |
| Create a Scheduled Task → | Automate Teams notifications on a schedule |