Azure

Mission Control integrates with Azure to scrape and monitor your Azure cloud resources. The integration supports:

• Azure subscription monitoring via subscription ID
• Organization and tenant-based access
• Configurable exclusions and transformations
• Authentication via client ID and secret
• Custom connection settings

Getting Started

Prerequisites

To enable the Kubernetes integration you need:

• Mission Control installed
• kubectl access to the Mission Control instance
• Azure client credentials or Azure Workload Identity configured for the config-db service

1. Install the mission-control-azure chart

   Helm

   helm install mission-control-azure flanksource/mission-control-azure \
    --set subscriptionID=<your-subscription-id> \
    --set tenantID=<your-tenant-id> \
    -n mission-control --wait 

   Flux

   apiVersion:  helm.toolkit.fluxcd.io/v2
   kind: HelmRelease
   metadata:
     name: mission-control-azure
     namespace: mission-control
   spec:
     chart:
       spec:
         chart: mission-control-azure
         sourceRef:
           kind: HelmRepository
           name: flanksource
           namespace: mission-control
         interval: 1m
     values:
       subscriptionID: <your-subscription-id>
       tenantID: <your-tenant-id>
   values.yaml

   • clientID:
     • name: string
     • value: string
     • valueFrom:
       • configMapKeyRef:
         • key: string
         • name: string
       • helmRef:
         • key: string
         • name: string
       • secretKeyRef:
         • key: string
         • name: string
       • serviceAccount: string
   • clientSecret:
     • name: string
     • value: string
     • valueFrom:
       • configMapKeyRef:
         • key: string
         • name: string
       • helmRef:
         • key: string
         • name: string
       • secretKeyRef:
         • key: string
         • name: string
       • serviceAccount: string
   • connection: string
   • exclusions:
     • activityLogs[]:

       description: list of operations to exclude from activity logs examples: - Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action - Microsoft.ContainerService/managedClusters/listClusterUserCredential/action type: array
       - description: list of operations to exclude from activity logs examples: - Microsoft.ContainerService/managedClusters/listClusterAdminCredential/action - Microsoft.ContainerService/managedClusters/listClusterUserCredential/action type: array
   • global:

     Global values are values that can be accessed from any chart or subchart by exactly the same name.
     - Global values are values that can be accessed from any chart or subchart by exactly the same name.
   • labels: - list of labels to add the Scrape config
   • organisation: string
   • scraper:
     • name: string (default: "azure")
   • subscriptionID:
   • tenantID: string
   • transform:
     • relationship[]:

Next Steps

ScrapeConfig

CRD