Set up the Teams integration for Azure SRE Agent (preview)
Connect Azure SRE Agent to Microsoft Teams as an agent user, then verify it in a one-to-one chat.
Where available, an agent identity enables sending conversation content, including prompts, responses, and tool content from chats that a person starts, to Microsoft Agent 365 for observability. There's no per-agent opt-out. Review Agent 365 data handling before setup.
For scheduled posts and reports, use a notification connector instead.
Prerequisites
- Write access to the agent resource for setup and disconnect.
- A user account in the agent's subscription tenant. The person completing setup becomes the agent user's manager.
- The object ID of a sponsor: a user, or a Microsoft 365 or dynamic-membership group, in the subscription's tenant. Security groups aren't supported. In the Microsoft Entra admin center, find the user under Users or the group under Groups > All groups, and copy its Object ID.
- A Microsoft 365 administrator who can assign the agent user a license that includes Teams. Agree on the agent user's name and domain with them. SRE Agent doesn't assign or validate licenses.
Set up the agent identity and user
If Communication Hub already shows Connected to Teams, skip to licensing and verification. Don't delete an existing identity or user to repeat setup.
-
In the portal, open Communication Hub and select Get started.
-
Review or enter the identity details:
- New identity: Enter an Identity name and Sponsor object ID for the user or group sponsoring the identity. Confirm Tenant ID matches your subscription's tenant.
- Existing identity: The details are prefilled. Keep them.
-
Review or enter the agent user details:
- New user: Enter a User name, Domain, and Display name. The sign-in name is user name at domain, such as
sre-oncall@contoso.com. The service adds(SRE Agent)to the display name. - Existing user (for example, created with the agent): Keep the prefilled values unchanged to reuse the user.
Record the user's sign-in name; your Microsoft 365 administrator needs it to assign the license.
- New user: Enter a User name, Domain, and Display name. The sign-in name is user name at domain, such as
-
Confirm Manager shows your account and can't be changed in the wizard, then review the license information.
Caution: The tenant and sponsor can't be changed after the identity is created. Verify both before finishing setup.
-
Select Save.
After connecting successfully, the agent sends you a welcome message in Teams. Receiving this message doesn't necessarily mean the agent is ready to chat. A Microsoft 365 administrator must still assign the agent user a license that includes Teams before you can chat with it.
Assign a Teams license and verify a one-to-one chat
- Have your Microsoft 365 administrator assign the agent user a license that includes Teams.
- In Teams, search for the agent by its display name and start a one-to-one chat.
- Send a read-only question, such as "What is your Azure SRE Agent resource ID? Don't make any changes." You don't need to mention the agent in a one-to-one chat.
- If a private Sign in card appears, sign in with your work account. If your question gets no response after Signed in, send it again.
Checkpoint: The agent replies in Teams, and the conversation appears in Communication Hub.
For commands, approvals, and day-to-day use, see Chat with Azure SRE Agent in Teams.
Disconnect
- In Communication Hub, select Disconnect.
- To keep the identity and agent user, leave Also delete the agent user and agent identity cleared.
- Select Disconnect and wait for Agent disconnected from Teams.
Disconnecting deletes conversation grants and the bindings between Teams conversations and SRE Agent threads. Existing Teams conversations and history aren't deleted. Remove the Teams license separately if it's no longer needed.
Troubleshooting
| Symptom | What to check |
|---|---|
Setup reports a tenant mismatch or TenantNotAllowed | Use the subscription's tenant and sign in to that tenant. |
ProvisioningDisabled | Agent identity isn't available in this region yet. |
| Identity provisioning fails | Review the provisioning error and check the sponsor and identity name: at most 128 characters, no /, and not system or none. |
| You can't find the agent in Teams | Confirm that the correct agent user has a license that includes Teams. |
| You get no response in a one-to-one chat | Confirm you have a chat-capable SRE Agent role, you've signed in, and you sent a new message after Signed in. |