Connect a notification service

Use a notification service when the agent needs to share what it finds. It can email an incident summary or post an update to a collaboration channel so the right people see the investigation status.

This tutorial covers Office 365 Outlook, Microsoft Teams, Google Gmail, and Yammer/Viva Engage. These connectors use the managed connector wizard, so this article focuses on notification details: authentication, operations, and governance that keeps messages going to the right destination.

Prerequisites

• A running SRE Agent and access to sre.azure.com.
• Permission to configure connectors on the agent.
• An account for the service with permission to send mail or post to the destination you want to use.

If you haven't set up a connector before, start with Set up a managed connector for the full wizard walkthrough. This article calls out only the notification differences.

Notification connectors

These notification connectors use a single sign-in. Messages come from the account you authorize, so the agent's messages appear from you or that account.

Step 1: Add the connector

1. Go to sre.azure.com and select your agent.

2. In the left sidebar, expand Builder, and then select Connectors.

3. Select Add connector.

4. On the Notification tab, select your service.

Step 2: Authenticate

1. Complete the sign-in or credential flow shown by the connector.

2. Wait for the connection card to show a green checkmark and your account name or connection status.

Step 3: Set up tools

On the Set up tools step, enable the operation that sends the message you want. For example, choose a send-email operation, a post-to-channel operation, or another notification operation shown by the connector.

A notification connector usually needs only one or two operations. Enable the smallest set that supports your incident communication process.

Step 4: Govern destinations

Notification operations reach people and durable systems, so govern them carefully. Lock the destination and require approval.

1. Set send and post operations to Ask so the agent shows you each message before it sends.

2. Turn on Parameter policy for that operation and lock the destination. Lock the recipient address for email or the channel, chat, or community for Teams, Gmail, or Viva Engage.

For a send-email operation, a safe configuration looks like this:

For a channel or community post, lock the channel, chat, or community destination and let the agent fill the message body from incident context. The agent can draft the update without choosing where it lands.

Step 5: Validate with a scenario

1. Open a chat with your agent.

2. Ask it to send a summary, such as:

   Send a summary of the last incident to the on-call channel.
   

3. Because you set the operation to Ask, the agent shows the message it plans to send, including the locked destination.

4. Review and approve the action. Confirm it arrived in the mailbox, channel, chat, or community.

When the update lands in the right place with your approval, the connector and its governance work end to end.

Troubleshooting

Related content

• Connect a source code service
• Connect a telemetry source
• Set up a managed connector