Azure Cloud Infrastructure

Monitor and analyze Azure resources using Dynatrace Smartscape and DQL. Query Azure services, audit security, manage organizational hierarchy, and plan capacity across your Azure infrastructure.

When to Use This Skill

Use this skill when the user needs to work with Azure resources in Dynatrace. Load the reference file for the task type:

Core Concepts

Entity Types

Azure resources use the AZURE* prefix and can be queried using the smartscapeNodes function. All Azure entities are automatically discovered and modeled in Dynatrace Smartscape. Entity type names are derived from the ARM resource provider path: /Microsoft.Compute/virtualMachines becomes AZUREMICROSOFTCOMPUTEVIRTUALMACHINES. Sub-resources append with underscores: /Microsoft.Sql/servers/databases becomes AZUREMICROSOFTSQLSERVERSDATABASES.

Compute: AZUREMICROSOFTCOMPUTEVIRTUALMACHINES, AZUREMICROSOFTCOMPUTEVIRTUALMACHINESCALESETS, AZUREMICROSOFTCOMPUTEVIRTUALMACHINESCALESETSVIRTUALMACHINES, AZUREMICROSOFTCOMPUTEDISKS, AZUREMICROSOFTCOMPUTESSHPUBLICKEYS, AZUREMICROSOFTCOMPUTEVIRTUALMACHINESEXTENSIONS Networking: AZUREMICROSOFTNETWORKVIRTUALNETWORKS, AZUREMICROSOFTNETWORKVIRTUALNETWORKSSUBNETS, AZUREMICROSOFTNETWORKNETWORKSECURITYGROUPS, AZUREMICROSOFTNETWORKPUBLICIPADDRESSES, AZUREMICROSOFTNETWORKNETWORKINTERFACES, AZUREMICROSOFTNETWORKLOADBALANCERS, AZUREMICROSOFTNETWORKAPPLICATIONGATEWAYS, AZUREMICROSOFTNETWORKVIRTUALNETWORKGATEWAYS, AZUREMICROSOFTNETWORKCONNECTIONS, AZUREMICROSOFTNETWORKEXPRESSROUTECIRCUITS Database: AZUREMICROSOFTSQLSERVERS, AZUREMICROSOFTSQLSERVERSDATABASES, AZUREMICROSOFTCACHEREDIS, AZUREMICROSOFTCACHEREDISENTERPRISE, AZUREMICROSOFTDOCUMENTDBDATABASEACCOUNTS Storage: AZUREMICROSOFTSTORAGESTORAGEACCOUNTS, AZUREMICROSOFTSTORAGESTORAGEACCOUNTSBLOBSERVICESCONTAINERS, AZUREMICROSOFTSTORAGESTORAGEACCOUNTSFILESERVICESSHARES, AZUREMICROSOFTSTORAGESTORAGEACCOUNTSQUEUESERVICESQUEUES, AZUREMICROSOFTSTORAGESTORAGEACCOUNTSTABLESERVICESTABLES Kubernetes/Containers: AZUREMICROSOFTCONTAINERSERVICEMANAGEDCLUSTERS, AZUREMICROSOFTCONTAINERSERVICEMANAGEDCLUSTERSAGENTPOOLS, AZUREMICROSOFTCONTAINERREGISTRYREGISTRIES, AZUREMICROSOFTAPPCONTAINERAPPS, AZUREMICROSOFTAPPMANAGEDENVIRONMENTS, AZUREMICROSOFTAPPJOBS App Service: AZUREMICROSOFTWEBSITES, AZUREMICROSOFTWEBSERVERFARMS, AZUREMICROSOFTWEBSITESFUNCTIONS Messaging: AZUREMICROSOFTEVENTHUBNAMESPACES, AZUREMICROSOFTEVENTHUBNAMESPACESEVENTHUBS, AZUREMICROSOFTSERVICEBUSNAMESPACES, AZUREMICROSOFTSERVICEBUSNAMESPACESQUEUES, AZUREMICROSOFTSERVICEBUSNAMESPACESTOPICS, AZUREMICROSOFTSERVICEBUSNAMESPACESTOPICSSUBSCRIPTIONS Security/Identity: AZUREMICROSOFTKEYVAULTVAULTS, AZUREMICROSOFTMANAGEDIDENTITYUSERASSIGNEDIDENTITIES Monitoring: AZUREMICROSOFTOPERATIONALINSIGHTSWORKSPACES, AZUREMICROSOFTINSIGHTSCOMPONENTS API Management: AZUREMICROSOFTAPIMANAGEMENT_SERVICE

Azure Organizational Hierarchy

Azure organizes resources in a three-level hierarchy: Tenant > Subscription > Resource Group. Every resource belongs to exactly one resource group within one subscription. Use these fields to scope queries:

```dql-snippet filter azure.subscription == "08b9810e-..."

```dql-snippet
filter azure.resource.group == "my-rg"

```dql-snippet filter azure.location == "eastus"

Combine these filters for precise scoping:

```dql-template
smartscapeNodes "AZURE_*"
| filter azure.subscription == "<SUBSCRIPTION_ID>"
    and azure.resource.group == "<RESOURCE_GROUP>"
    and azure.location == "<REGION>"
| summarize count = count(), by: {type}
| sort count desc

To see the organizational breakdown across your environment:

smartscapeNodes "AZURE_*"
| summarize resource_count = count(), by: {azure.subscription, azure.resource.group}
| sort resource_count desc

Common Azure Fields

All Azure entities include:

• azure.subscription — Azure subscription GUID
• azure.resource.group — Resource group name
• azure.location — Azure region (e.g., eastus, polandcentral)
• azure.resourceType — ARM resource type (e.g., microsoft.compute/virtualmachines)
• azure.provisioning_state — Provisioning state (e.g., Succeeded)
• azure.object — Full ARM resource JSON (see [Configuration Parsing](#configuration-parsing-with-azureobject))
• cloud.provider — Always azure
• tags — Resource tags (use ` tags[key] `)

Some entity types also have:

• azure.resourceId — Full ARM resource ID (VMs and some others)
• azure.resourceName — Resource name (VMs and some others)
• azure.availabilityZones — Availability zone list (VMs)

Relationship Types

Azure entity relationships can be traversed using traverse. The dt.traverse.relationship field is not populated for Azure entities, so you must use "*" as the relationship name in all traversal commands.

Key traversal pairs:

• VM → Disks: traverse "*", "AZUREMICROSOFTCOMPUTE_DISKS"
• VM → NICs: traverse "*", "AZUREMICROSOFTNETWORK_NETWORKINTERFACES"
• VM → VMSS: traverse "*", "AZUREMICROSOFTCOMPUTE_VIRTUALMACHINESCALESETS"
• VM → Availability Zones: traverse "*", "AZUREMICROSOFTRESOURCESLOCATIONSAVAILABILITYZONES"
• VM ← Extensions: traverse "*", "AZUREMICROSOFTCOMPUTEVIRTUALMACHINESEXTENSIONS", direction:backward
• VMSS → AKS Clusters: traverse "*", "AZUREMICROSOFTCONTAINERSERVICE_MANAGEDCLUSTERS"
• VMSS → Subnets: traverse "*", "AZUREMICROSOFTNETWORKVIRTUALNETWORKSSUBNETS"
• VMSS → NSGs: traverse "*", "AZUREMICROSOFTNETWORK_NETWORKSECURITYGROUPS"
• VMSS → LB Backend Pools: traverse "*", "AZUREMICROSOFTNETWORKLOADBALANCERSBACKENDADDRESSPOOLS"
• Subnet → VNet: traverse "*", "AZUREMICROSOFTNETWORK_VIRTUALNETWORKS"
• Subnet → NSG: traverse "*", "AZUREMICROSOFTNETWORK_NETWORKSECURITYGROUPS"
• Subnet ← VMSS: traverse "*", "AZUREMICROSOFTCOMPUTE_VIRTUALMACHINESCALESETS", direction:backward
• NSG ← NICs: traverse "*", "AZUREMICROSOFTNETWORK_NETWORKINTERFACES", direction:backward
• NSG ← Subnets: traverse "*", "AZUREMICROSOFTNETWORKVIRTUALNETWORKSSUBNETS", direction:backward
• LB → Backend Pools: traverse "*", "AZUREMICROSOFTNETWORKLOADBALANCERSBACKENDADDRESSPOOLS"
• LB → Frontend IPs: traverse "*", "AZUREMICROSOFTNETWORKLOADBALANCERSFRONTENDIPCONFIGURATIONS"
• LB → LB Rules: traverse "*", "AZUREMICROSOFTNETWORKLOADBALANCERSLOADBALANCINGRULES"
• SQL Server ← SQL Databases: traverse "*", "AZUREMICROSOFTSQLSERVERSDATABASES", direction:backward
• Storage Account ← Blob Containers: traverse "*", "AZUREMICROSOFTSTORAGESTORAGEACCOUNTSBLOBSERVICES_CONTAINERS", direction:backward
• Storage Account ← File Shares: traverse "*", "AZUREMICROSOFTSTORAGESTORAGEACCOUNTSFILESERVICES_SHARES", direction:backward
• AKS ← VMSS: traverse "*", "AZUREMICROSOFTCOMPUTE_VIRTUALMACHINESCALESETS", direction:backward
• AKS ← Agent Pools: traverse "*", "AZUREMICROSOFTCONTAINERSERVICEMANAGEDCLUSTERSAGENTPOOLS", direction:backward
• AKS ← NSGs: traverse "*", "AZUREMICROSOFTNETWORK_NETWORKSECURITYGROUPS", direction:backward
• AKS ← Public IPs: traverse "*", "AZUREMICROSOFTNETWORK_PUBLICIPADDRESSES", direction:backward
• AKS → Public IPs: traverse "*", "AZUREMICROSOFTNETWORK_PUBLICIPADDRESSES"
• Web Site → App Service Plan: traverse "*", "AZUREMICROSOFTWEB_SERVERFARMS"
• Web Site ← Functions: traverse "*", "AZUREMICROSOFTWEBSITESFUNCTIONS", direction:backward
• Container App → Managed Environment: traverse "*", "AZUREMICROSOFTAPP_MANAGEDENVIRONMENTS"
• EventHub Namespace ← Event Hubs: traverse "*", "AZUREMICROSOFTEVENTHUBNAMESPACESEVENTHUBS", direction:backward
• ServiceBus Namespace ← Queues: traverse "*", "AZUREMICROSOFTSERVICEBUSNAMESPACESQUEUES", direction:backward
• ServiceBus Namespace ← Topics: traverse "*", "AZUREMICROSOFTSERVICEBUSNAMESPACESTOPICS", direction:backward
• ServiceBus Topic ← Subscriptions: traverse "*", "AZUREMICROSOFTSERVICEBUSNAMESPACESTOPICS_SUBSCRIPTIONS", direction:backward
• Use fieldsKeep:{field1, field2} to carry fields through multi-hop traversals
• After a single-hop traverse, use dt.traverse.history[0][id] to get the source entity ID, then lookup to resolve the source entity name:

``dql-snippet | fieldsAdd sourceId = dt.traverse.history[0][id] | lookup [smartscapeNodes "SOURCE_TYPE" | fields name, id], sourceField: sourceId, lookupField: id, prefix: "src." ``

• After multi-hop traversals, dt.traverse.history[-N] works for fields carried via fieldsKeep

Azure Metric Naming Convention

Dynatrace ingests Azure Monitor metrics and exposes them using this naming pattern:

cloud.azure.<provider_namespace>.<resource_type>.<MetricName>

The <providernamespace> uses underscores within the namespace (e.g., microsoftcompute) and <resourcetype> is lowercase (e.g., virtualmachines). Hierarchy levels are dot-separated: microsoftsql.servers.databases. <MetricName> is the Azure Monitor metric name.

Examples:

To query a metric:

```dql-template timeseries cpu = avg(cloud.azure.microsoftcompute.virtualmachines.PercentageCPU), by: {dt.smartscapesource.id}, from: now()-1h | limit 10

**Important:** Never refer to these as "Azure Monitor alerts" or "Azure Monitor metrics" in output. Dynatrace monitors Azure resources natively through its Azure integration — these are **Dynatrace metrics** ingested from Azure.

### Configuration Parsing with azure.object

The `azure.object` field contains the full ARM resource JSON. Parse it with the `azjson` alias:

```dql-snippet
parse azure.object, "JSON:azjson"

The JSON is wrapped in a configuration key:

{
  "configuration": {
    "id": "<ARM resource ID>",
    "name": "<resource name>",
    "type": "<ARM resource type>",
    "location": "<region>",
    "sku": { ... },
    "properties": { ... },
    "zones": [...]
  },
  "tags": { ... }
}

Access patterns:

• Properties: azjson[configuration][properties][field]
• SKU: azjson[configuration][sku][name]
• Kind: azjson[configuration][kind]
• Zones: azjson[configuration][zones]

Common configuration fields by service:

• VM: properties.hardwareProfile.vmSize, properties.storageProfile.imageReference.offer, properties.storageProfile.osDisk.osType, properties.extended.instanceView.powerState.displayStatus
• VMSS: sku.name (VM size), sku.capacity (instance count), tags.aks-managed-poolName
• NSG: properties.securityRules[] (custom rules array), properties.securityRules[].properties.direction, properties.securityRules[].properties.access, properties.securityRules[].properties.sourceAddressPrefix
• Storage Account: kind (e.g., StorageV2), sku.name, properties.accessTier, properties.supportsHttpsTrafficOnly, properties.allowBlobPublicAccess, properties.encryption.keySource
• SQL Server: properties.fullyQualifiedDomainName, properties.publicNetworkAccess, properties.minimalTlsVersion
• SQL Database: sku.name (tier), sku.capacity (DTU/vCore), properties.status, properties.zoneRedundant
• AKS: properties.kubernetesVersion, properties.powerState.code, properties.networkProfile.networkPlugin, properties.enableRBAC
• Web Site: kind (e.g., functionapp,linux), properties.state, properties.defaultHostName, properties.siteConfig.linuxFxVersion
• Container App: properties.runningStatus, properties.template.containers[].image, properties.template.scale.minReplicas, properties.template.scale.maxReplicas
• Event Hub Namespace: sku.name, properties.kafkaEnabled, properties.zoneRedundant
• Service Bus Namespace: sku.name (Basic/Standard/Premium), properties.zoneRedundant, properties.minimumTlsVersion, properties.publicNetworkAccess, properties.disableLocalAuth, properties.status
• Service Bus Queue: properties.maxSizeInMegabytes, properties.enablePartitioning, properties.deadLetteringOnMessageExpiration, properties.maxDeliveryCount, properties.lockDuration, properties.requiresDuplicateDetection, properties.status
• Key Vault: properties.enableRbacAuthorization, properties.enableSoftDelete, properties.publicNetworkAccess
• Redis: properties.sku.name, properties.hostName, properties.redisVersion, properties.enableNonSslPort
• Cosmos DB: kind (e.g., GlobalDocumentDB), properties.EnabledApiTypes, properties.consistencyPolicy.defaultConsistencyLevel
• Load Balancer: sku.name, tags.aks-managed-cluster-name
• App Gateway: properties.sku.name, properties.sku.tier, properties.operationalState, properties.webApplicationFirewallConfiguration.enabled, properties.webApplicationFirewallConfiguration.firewallMode (Detection/Prevention), properties.webApplicationFirewallConfiguration.ruleSetType, properties.webApplicationFirewallConfiguration.ruleSetVersion, properties.webApplicationFirewallConfiguration.disabledRuleGroups[], properties.webApplicationFirewallConfiguration.exclusions[], properties.firewallPolicy.id

Query Patterns

All Azure queries build on four core patterns. Master these and adapt them to any entity type.

Pattern 1: Resource Discovery

List resources by type, filter by subscription/resource group/region/tags, summarize counts:

```dql-template smartscapeNodes "AZURE*" | filter azure.subscription == "<SUBSCRIPTIONID>" and azure.location == "<REGION>" | summarize count = count(), by: {type} | sort count desc

To list a specific type, replace `"AZURE_*"` with the entity type (e.g., `"AZURE_MICROSOFT_COMPUTE_VIRTUALMACHINES"`). Add `| fields name, azure.subscription, azure.resource.group, azure.location, ...` to select specific columns. Use `` tags[`TagName`] `` for tag-based filtering.

### Pattern 2: Configuration Parsing

Parse `azure.object` JSON for detailed configuration fields:

```dql-template
smartscapeNodes "AZURE_MICROSOFT_COMPUTE_VIRTUALMACHINES"
| parse azure.object, "JSON:azjson"
| fieldsAdd vmSize = azjson[configuration][properties][hardwareProfile][vmSize],
            osType = azjson[configuration][properties][storageProfile][osDisk][osType]
| summarize vm_count = count(), by: {vmSize, osType, azure.location}

Pattern 3: Relationship Traversal

Follow relationships between resources. Use "*" for the relationship name since Azure does not populate dt.traverse.relationship:

```dql-template smartscapeNodes "AZUREMICROSOFTNETWORKLOADBALANCERS" | parse azure.object, "JSON:azjson" | fieldsAdd lbSku = azjson[configuration][sku][name] | traverse "", "AZUREMICROSOFTNETWORKLOADBALANCERSBACKENDADDRESSPOOLS", fieldsKeep:{lbSku, name, id} | fieldsAdd backendPoolName = name | traverse "", "AZUREMICROSOFTCOMPUTEVIRTUALMACHINESCALESETS", direction:backward, fieldsKeep:{backendPoolName, id} | fieldsAdd loadBalancerName = dt.traverse.history[-2][name], loadBalancerId = dt.traverse.history[-2][id], backendPoolId = dt.traverse.history[-1][id]

Key differences from AWS traversals:
- Always use `"*"` as the relationship name (relationship type names are empty for Azure)
- Azure relationships primarily follow a parent-child hierarchy: sub-resources link backward to parent resources
- AKS is a major relationship hub with backward links from VMSS, NSGs, LBs, Public IPs, Agent Pools, and Managed Identities

### Pattern 4: Tag-Based Ownership

Group resources by any tag for ownership/chargeback:

```dql-template
smartscapeNodes "AZURE_*"
| filter isNotNull(tags[`<TAG_NAME>`])
| summarize resource_count = count(), by: {tags[`<TAG_NAME>`], type}
| sort resource_count desc

Common Azure tags: ` tags[ACE:CREATED-BY] , tags[dtowneremail] , tags[dtownerteam] , tags[project] , tags[managed-by] . Replace "AZURE_*"` with a specific type to scope to one service.

Find untagged resources: | filter arraySize(tags) == 0

Reference Guide

Load reference files for detailed queries when the core patterns above need service-specific adaptation.

Best Practices

Query Optimization

1. Filter early by subscription, resource group, and region
2. Use specific entity types (avoid "AZURE_*" wildcards when possible)
3. Limit results with | limit N for exploration
4. Use isNotNull() checks before accessing nested fields

Configuration Parsing

1. Always parse azure.object with JSON parser: parse azure.object, "JSON:azjson"
2. Use consistent field naming: fieldsAdd configField = azjson[configuration][properties][field]
3. Access SKU via azjson[configuration][sku][name] (not inside properties)
4. Check for null values after parsing — not all entity types have the same properties structure
5. Use toString() for complex nested objects

Organizational Hierarchy

1. Always scope queries by azure.subscription in multi-subscription environments
2. Use azure.resource.group to narrow to a team or application boundary
3. Combine azure.location for region-specific analysis
4. Use summarize ... by: {azure.subscription, azure.resource.group} for organizational breakdowns

Tagging Strategy

1. Use ` tags[key] ` for filtering (backtick-quoted key names)
2. Check arraySize(tags) for untagged resources
3. Track tag coverage with summarize operations
4. Common ownership tags: dtowneremail, dtownerteam, ACE:CREATED-BY

Limitations and Notes

Smartscape Limitations

• Azure object configuration requires parsing with parse azure.object, "JSON:azjson"
• Azure metrics are available as Dynatrace metrics using the cloud.azure.* naming convention (see [Azure Metric Naming Convention](#azure-metric-naming-convention))
• Resource discovery depends on Azure integration configuration in Dynatrace
• Tag synchronization may have slight delays

Relationship Traversal

• Azure relationship type names are empty — always use "*" as the relationship name in traverse commands
• Use direction:backward for reverse relationships (e.g., sub-resources to parent)
• Use fieldsKeep to maintain important fields through traversal
• Access traversal history with dt.traverse.history[0][id] for single-hop source entity ID; use lookup to resolve source entity name
• For multi-hop traversals, dt.traverse.history[-N] accesses fields carried via fieldsKeep
• Azure relationships primarily follow parent-child hierarchy patterns
• AKS is a major relationship hub — expect many backward relationships converging on AKS cluster entities

AKS Coverage

• This skill covers AKS infrastructure-layer entities only (clusters, agent pools, VMSS, networking)
• For Kubernetes workload-layer observability (pods, deployments, services, namespaces), defer to the dt-obs-kubernetes skill

General Tips

• Use getNodeName() for human-readable resource names
• Handle null values gracefully with isNotNull() and isNull()
• Combine subscription, resource group, and region filters for large environments
• Use countDistinct() for unique resource counts
• The azure.resourceType field is lowercase ARM format (e.g., microsoft.compute/virtualmachines) — useful for filtering but not for entity type matching