Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Connectors in Azure SRE Agent let you integrate external services for communication and data ingestion. Use connectors to send notifications, receive updates, and pull telemetry from monitoring platforms. This article explains connector types, how they work, and how to set them up.
What are connectors?
Connectors are modular integrations that extend the SRE Agent's capabilities. There are two main types:
| Type | Description | Possible use case |
|---|---|---|
| Communication connectors | Send notifications and updates to services like Outlook and Microsoft Teams. | When the SRE Agent detects an incident, it can email stakeholders or post updates in Teams. |
| Custom connectors | Create a custom connection to an MCP server endpoint of your choice. The Azure MCP Center gives you access to various MCP endpoints you can integrate into SRE Agent. | When connected to a custom endpoint, SRE Agent can gain insight into external services like GitHub, Hugging Face, Stripe, and many more. For a full list of cataloged MCP server endpoints, see Azure MCP Center. |
Available connectors
Azure SRE Agent includes these connectors:
- Outlook for sending email notifications.
- Microsoft Teams to post messages to Teams channels.
- Custom MCP Servers for integration with your own remote MCP server.
Configure a connector
Follow these steps to set up a connector:
- Go to Settings in the SRE Agent portal.
- Select Connectors.
- Choose a connector type (Outlook, Teams, or Custom MCP Server).
- Authenticate:
- For Outlook and Teams, use OAuth-based authentication. You will need to sign in with the Outlook or Teams account. Additionally, you will need to select the user-assigned managed identity so that the connector can authenticate with Office 365 APIs.
- For MCP Servers, provide the MCP URL and credentials or OAuth token.
- Confirm and save your configuration.
Note: For connectors that use a managed identity, only user-assigned managed identities are currently supported. Using system-assigned managed identities in connectors is not fully functional yet.