Skip to content
Cloud Mechanics
DevOps Agent iconAI Agent

DevOps Agent

DevOps Agent that automates it & engineering workflows using your data and tools.

The challenge

When a release goes wrong the team hunts through dashboards to work out which change caused it. Alerts arrive faster than anyone can read them, the runbook lives with whoever was on call last time, and the same incident gets solved from first principles again.

The outcome

Azure Application Insights, Azure Monitor and Log Analytics feed a Microsoft Foundry agent that correlates the failure to the change behind it and finds the runbook in Azure AI Search. Known failures with a safe, pre-approved action recover through Azure Automation; novel ones page an engineer with the evidence.

At a glance

Type
ai agents
Category
technical

Next step

Move from solution to engagement.

Build This Solution

01 — Architecture

End-to-end architecture

A commit builds, scans and ships through progressive rollout with health gates. Telemetry from Application Insights, Monitor and Log Analytics flows back to the Foundry agent, which correlates a failure to the change that caused it and proposes the runbook — executing only pre-approved actions with a known blast radius.

TEAMDeveloper / SREcommit & releaseSOURCEGitHubrepos & actionsDockerimage buildPIPELINEContainerRegistryversioned imagesAzure Kubernetesrollout & rollbackAI & AGENTMicrosoft FoundryAgenttriage & remediateAzure OpenAImodelsdiff & failure notesAzure AI Searchrunbooks & historyAzure AI ContentSafetychange guardrailsSIGNALSApplicationInsightstraces & errorsAzure Monitormetrics & alertsLog Analyticsqueries & logsACTION & INSIGHTOn-call engineerapprove & confirmAutomationrunbookssafe remediationPower BI / Fabricdelivery metricsDEVOPS & DELIVERYGitHubsource control & CIDockercontainer buildContainer Registryversioned imagesProgressive releasedeploy with rollback
Figure 1 — End-to-end reference architecture for a delivery and reliability agent on the Microsoft stack.
  • Team: Developer / SRE
  • Source: GitHub, Docker
  • Pipeline: Container Registry, Azure Kubernetes
  • AI & agent: Microsoft Foundry Agent, Azure OpenAI models, Azure AI Search, Azure AI Content Safety
  • Signals: Application Insights, Azure Monitor, Log Analytics
  • Action & insight: On-call engineer, Automation runbooks, Power BI / Fabric

02 — Workflow

Process & decision workflow

How a change is built, released, observed and recovered — then branched. A known failure with a safe, pre-approved action is remediated and verified automatically, while a novel failure or a wide blast radius goes to the on-call engineer with the correlation and the options.

1BuildCommit builds, scans and produces aversioned image2TestUnit, integration and load gates run onthe change3ReleaseProgressive rollout with health gatesper stage4ObserveMetrics, traces, logs and error budgetwatched5TriageFailure correlated to the change and therunbook6RemediateRollback or fix proposed with theevidenceSafe toauto-remediate?Path 1 · known failure, safe actionRun the approved runbookRollback or restart executed andverifiedPath 2 · novel or wide blast radiusOn-call engineer decidesCorrelation, evidence and optionspresentedService restoredHealth verified and the incidenttimedLearning capturedRunbook and guardrail updatedCloseincident closed
Figure 2 — Build → test → release → observe → triage → safety branch → auto-remediate or on-call.
  1. Build: Commit builds, scans and produces a versioned image
  2. Test: Unit, integration and load gates run on the change
  3. Release: Progressive rollout with health gates per stage
  4. Observe: Metrics, traces, logs and error budget watched
  5. Triage: Failure correlated to the change and the runbook
  6. Remediate: Rollback or fix proposed with the evidence
  7. Path 1 · known failure, safe actionRun the approved runbook: Rollback or restart executed and verified
  8. Path 2 · novel or wide blast radiusOn-call engineer decides: Correlation, evidence and options presented

03 — Components

Key Microsoft components

Delivery speed only counts with fast recovery — pipeline, telemetry, remediation and evidence all stay on the Microsoft stack.

  • GitHub iconGitHubSource control, actions and pull-request based change.
  • Azure Container Registry iconAzure Container RegistryVersioned images with provenance and rollback.
  • Azure Kubernetes Service iconAzure Kubernetes ServiceProgressive rollout, health gates and fast rollback.
  • Azure Load Testing iconAzure Load TestingPerformance gates before a release is promoted.
  • Microsoft Foundry Agent Service iconMicrosoft Foundry Agent ServiceTriage, correlation and remediation orchestration.
  • Azure OpenAI models iconAzure OpenAI modelsFailure narratives, diff explanation and release notes.
  • Azure AI Search iconAzure AI SearchRetrieval over runbooks, past incidents and change history.
  • Azure AI Content Safety iconAzure AI Content SafetyGuardrails on generated commands and privileged actions.
  • Azure Application Insights iconAzure Application InsightsTraces, dependencies, exceptions and user impact.
  • Azure Monitor iconAzure MonitorMetrics, alerts, health gates and error budgets.
  • Azure Log Analytics iconAzure Log AnalyticsLog queries and correlation across the estate.
  • Azure Automation iconAzure AutomationPre-approved remediation runbooks with audit trail.
  • Azure Key Vault iconAzure Key VaultPipeline credentials, signing keys and secrets.
  • Power BI / Microsoft Fabric iconPower BI / Microsoft FabricDelivery, reliability and change-failure dashboards.

04 — AI

What the agent consumes

The capabilities the agent applies to every release and incident, and the line it does not cross.

AI capabilities embedded in the agent

  • Build and test orchestration
  • Change correlation
  • Log and trace analysis
  • Anomaly detection
  • Retrieval-augmented generation
  • Failure summarisation
  • Rollback recommendation
  • Blast-radius estimation
  • Release-note drafting
  • Alert deduplication
  • Delivery metric rollup
  • Approval routing

AI responsibility boundaries

The agent executes only pre-approved runbooks with a known blast radius. Novel failures, production data changes and anything affecting customer traffic at scale need an on-call engineer. Every automated action logs the trigger, the evidence, the command run and the verification result.

05 — Personalization

Personalization & evolving process

The same methodology applies to every agent in the catalog. Tune the service estate, the delivery template, the runbooks and the value model — the page structure stays identical.

Service & environment profile

Define the services, environments, release cadence, service levels and error budgets in scope. The personas are the developer, the site reliability engineer, the on-call responder and the service owner.

06 — Impact

Key outcomes & business impact

Starting targets for the value case — validate each one against the customer baseline during discovery.

  • Time to restore−50%Failures are correlated to the change within minutes.
  • Change failure rate−30%Health gates stop a bad release before full rollout.
  • Alert noise−60%Deduplicated, correlated alerts instead of a wall of pages.
  • Action evidence100%Every automated action logs its trigger and verification.

Illustrative improvement index

Manual baseline = 100. Illustrative targets, not a commitment — confirm against the customer baseline.

10050Time to restore10040Alert noise10045Manual toilManual baselineAI-assisted target
  • Time to restore: manual baseline 100, AI-assisted target 50
  • Alert noise: manual baseline 100, AI-assisted target 40
  • Manual toil: manual baseline 100, AI-assisted target 45

Related & recommended

Derived automatically from our solution knowledge graph.

Related AI agents

Other agents that pair well with this one.

Related professional services

How we design, build and secure it.

Related quick wins

Ready-made Azure AI to start fast.

Technologies

What powers this solution.

Related managed services

Keep it running and optimised.

Ready to move from challenge to solution?

Talk to a Cloud Mechanics expert or build your solution in minutes.