INFRASTRUCTURE EVIDENCE
Azure Add Azure infrastructure context to evidence.
AKS, VM Scale Sets and Azure Database metadata explain where production runs in Azure. AutoObserve maps cloud resource relationships onto telemetry identity — alongside your existing Azure Monitor stack.
- Evidence
- Resource metadata · Cloud context
- Source
- Azure Resource Manager
- Enables
- Infrastructure relationships
- Status
- Preview
Azure
Resource metadata
AutoObserve
Infrastructure context
Investigation
WHY THIS INTEGRATION MATTERS
Azure context completes the production picture.
Telemetry tells you something failed. Azure metadata tells you which subscription, resource group and cluster carried the workload.
Resource relationships
Map services to AKS nodes, App Services and backing databases.
Cloud identity
Enrich telemetry with subscription and resource identifiers.
Infrastructure change
Correlate Activity Log events with production behaviour.
Multi-cloud context
Use the same evidence model across Azure and other clouds.
EVIDENCE RECEIVED
Resource metadata and cloud context from Azure
Azure Resource Manager metadata becomes infrastructure evidence — linked to service identity and runtime topology.
- Resource metadata
- Cloud context
Discover
Inventory AKS, VMs and database resources in scope.
Map
Link Azure resources to Kubernetes and telemetry identity.
Correlate
Join infrastructure context with metrics, logs and traces.
Investigate
Start incidents with Azure relationships already resolved.
HOW AUTOOBSERVE USES THIS EVIDENCE
Evidence becomes infrastructure investigation context.
Azure Monitor is not replaced — Azure metadata is connected. AutoObserve treats cloud resources as one evidence class in a multi-signal investigation.
Provides
- Resource metadata
- Cloud context
AutoObserve creates
- Infrastructure relationships
- Cloud identity
- Resource topology
- Change correlation
Azure is where it runs. AutoObserve is how you connect it.
CONNECT AZURE INFRASTRUCTURE
Ingest Azure metadata alongside telemetry.
Resource Graph, Activity Log and AKS paths feed the same evidence model — scoped to subscriptions you operate.
Query Azure Resource Manager for connected resource metadata.
Azure RM
AutoObserve connector
AutoObserve
QUICK START
Connect Azure infrastructure evidence
Configure service principal access and resource scope, then verify checkout-api resolves to Azure context.
Configure Azure access
Grant read-only permissions for target subscriptions and resource groups.
Link AKS runtime
Connect AKS clusters for combined cloud and Kubernetes context.
Verify infrastructure context
Confirm checkout-api resolves to subscription and backing resources.
WHAT SUCCESS LOOKS LIKE
Azure context resolved. Infrastructure ready.
Success means services map to Azure resources — not merely that credentials are configured.
Resources discovered
checkout-api backing stores appear in infrastructure context.
Subscription resolved
Production subscription appears on service identity.
Cross-signal correlation
Azure metadata aligns with telemetry during incidents.
REAL INCIDENT
Same checkout spike — service identity in focus.
The canonical checkout-api degradation with identity context highlighted — the resource linkage that grounds telemetry in Azure infrastructure.
Metric
14:31:00
Checkout latency +184%
Walk through the evidence chain · 1/6
Evidence step 1 of 6
TROUBLESHOOTING
Common Azure integration failures
Problem
No resources discovered
Likely cause
Service principal lacks Reader role on subscription or resource group.
Resolution
Verify RBAC grants and scoped subscriptions for the connector.
Verify
checkout-api backing resources appear within one sync window.
Problem
Resources present but not linked to services
Likely cause
Resource tags do not match telemetry service.name.
Resolution
Align Azure tags with Kubernetes labels and OTel resource attributes.
Verify
Database resource links to checkout-api in investigation context.
Problem
Stale resource metadata
Likely cause
Resource Graph query scope too broad or sync interval too long.
Resolution
Narrow scope to production resource groups and reduce sync lag.
Verify
Resource state matches production during incident window.
PRODUCTION INTELLIGENCE
How Azure contributes to production understanding
Azure infrastructure evidence enables resource relationship reasoning inside connected production intelligence.
| Evidence | Enables |
|---|---|
| Resource metadata | Infrastructure relationships |
| Cloud context | Subscription scope |
| Activity Log events | Infrastructure change correlation |
DESIGN PARTNERS
Validate this evidence source with your production stack.
Design partners connect real evidence sources and validate investigation workflows before GA — with direct engineering access.