Skip to main content

Getting Started

Prerequisites

1. Deploy the SRE Agent

Portal (recommended): Go to sre.azure.com → sign in → follow the 3-step wizard (walkthrough).

Bicep: See infra/sre-agent/README.md for the template-based approach.

Supported regions

Azure SRE Agent deploys to: eastus2, swedencentral, australiaeast, uksouth. It can monitor resources in any region.

2. Connect data sources

After deployment, on the agent setup page:

  1. Code → click + → GitHub → select the webstore repo (docs)
  2. Azure resources → Full setup tab → + → Resource groups → select your demo resource group (for example, rg-webstore-demo) (docs)

Verify in the agent chat: "What Azure resources can you see in <YOUR_DEMO_RESOURCE_GROUP>?"

3. Configure workflow secrets

The demo workflows use OIDC to authenticate. In Settings → Environments → demo (or staging while you are still migrating the GitHub environment name):

SecretsVariables
AZURE_CLIENT_ID — app registration client IDCONTAINER_APP_NAME — e.g. ca-webstore-demo
AZURE_TENANT_ID — Entra ID tenantRESOURCE_GROUP — e.g. rg-webstore-demo
AZURE_SUBSCRIPTION_ID — target subscription
APP_INSIGHTS_NAME — e.g. appi-webstore-demo
TEST_PRODUCT_ID — real seeded product CUID for checkout verification

TEST_PRODUCT_ID fixes the old hardcoded checkout payload bug. If you do not want to store it as an environment variable yet, you can pass test_product_id when you manually run the workflow.

4. Test

gh workflow run "Demo: Break Checkout" -f environment=<YOUR_GITHUB_ENVIRONMENT>
gh run watch
gh workflow run "Demo: Reset Checkout" -f environment=<YOUR_GITHUB_ENVIRONMENT>