Create and set up Azure SRE Agent

Azure SRE Agent is an AI solution that helps site reliability engineers (SREs) manage Azure cloud resources. This article shows you how to set up Azure SRE Agent and create an agent.

In this tutorial, you learn how to:

Prerequisites

• An Azure subscription. Create one for free.
• A Contributor role on the subscription. (You need it to register resource providers and create resources.) If your team assigns managed resource groups with role-based access control, you also need Owner or User Access Administrator privileges to create role assignments.
• Network access to *.azuresre.ai from your browser.

Open the onboarding wizard

1. Go to the Azure SRE Agent webpage.
2. Sign in with your Azure credentials.
3. Select Basics > Review > Deploy to open the wizard.

Configure basics

To define your agent, fill in the fields.

After you select a region, the Model provider field appears. Select the AI provider that powers your agent's investigations and conversations. Select the ℹ icon next to the label for pricing details.

Organizations with European Union (EU) data residency requirements should select Azure OpenAI. Anthropic is excluded from EU Data Boundary commitments. Anthropic (Claude) models require a direct Anthropic agreement and aren't available to all tenants.

Anthropic is selected by default for most regions. For Sweden Central, Azure OpenAI is selected by default. You can change the model provider after creation in Settings > Basics.

Select Next to proceed.

Checkpoint: All the fields are filled, including the model provider. The Next button is enabled.

Review

The wizard shows a summary of your configuration. Verify that the:

• Subscription and resource group are correct.
• Agent name and region match your intent.

Select Create to begin provisioning.

Checkpoint: The summary matches what you entered. No validation errors appear.

Deploy

The deployment creates the following Azure resources.

If you selected Create new for Application Insights, the deployment also creates an Application Insights instance and Log Analytics workspace.

Wait for the deployment to complete. This step typically takes two to five minutes.

Checkpoint: Deployment status shows Succeeded. All resources are listed as created.

Set up your agent

After deployment finishes, select Set up your agent to open the setup page. You see the header More context. Better investigations. This page has the following two tabs.

Start with the Quickstart tab. Not all sources are required, although connecting more sources gives your agent better context for investigations. This guide walks through connecting code (from Quickstart) and Azure resources (from Full setup).

Connect your code repository

1. On the Code card, select the + button to connect repositories.
2. To choose a platform, select GitHub. (Azure DevOps is also supported.)
3. To choose a sign-in method, select Auth or PAT.
   • Auth: Select Sign in, authenticate in the browser, and approve access when prompted.
   • PAT: Paste your personal access token (PAT) and select Connect.
4. Select Next to proceed to repository selection.
5. Use the dropdown list to select one or more repositories. They're listed alphabetically.
6. Select Add repository.

Checkpoint: The Code card shows a green checkmark and lists the connected repositories.

Add Azure resource access

Granting the agent Reader access to your Azure resources allows it to query metrics, logs, and resource configurations during investigations.

1. On the setup page, switch to the Full setup tab. You can also use the Azure Resources card if it's visible on Quickstart.

2. On the Azure Resources card, select the + button to add resources.

3. To choose the resource type, select Subscriptions or Resource groups, and then select Next.

   • If you choose Subscriptions:

     1. Use the search box to find subscriptions. Select the ones that you want the agent to access.
     2. Select Next to review agent permissions.
     3. The agent's managed identity is automatically granted the Reader role on each selected subscription. Review the permissions status.
     4. Select Add subscriptions.

   • If you choose Resource groups:

     1. To filter by subscription, use the subscription dropdown list to filter which resource groups are shown.
     2. To select resource groups, use the search box to find resource groups. Select the ones that you want the agent to access. The grid shows the resource group name, subscription, and region.
     3. Select Next to review agent permissions.
     4. Choose the permission level for the agent, and review the role assignments.
     5. Select Add resource group.

Checkpoint: The Azure Resources card shows the connected subscriptions or resource groups.

The subscription picker shows all of your subscriptions in two sections. It shows the subscriptions that you can assign (where you have Owner or User Access Administrator privileges), and the subscriptions that require a higher role. A User role column shows your current role on each subscription. If you use Privileged Identity Management (PIM) for just-in-time access, the picker detects your active PIM role within seconds. You don't need to wait for cache refreshes.

After you add subscriptions or resource groups, the agent automatically assigns the required permissions to its managed identity. This step can take a few seconds. The status update appears in the permissions review step. The Reader role provides read-only access. For advanced permission management, see Manage permissions and access.

Select Done and go to agent

After you connect to your data sources, select Done and go to agent. This action takes you into the agent chat to start team onboarding.

Checkpoint: The agent chat opens.

Related content

• Connectors
• User roles and permissions
• Agent permissions
• Team onboarding