Skip to content

Latest commit

 

History

History
67 lines (49 loc) · 3.29 KB

AUTHENTICATION.md

File metadata and controls

67 lines (49 loc) · 3.29 KB
Raw

Authentication

Local Authentication

The default authentication mechanism used by the Azure Monitor Exporter is "Local Authentication", which relies exclusively on the InstrumentationKey obtained from the connection string of the Application Insights. Below is an illustrative example of the exporters section in a configuration file:

exporters:
   azuremonitor:
      connection_string: "InstrumentationKey=00000000-0000-0000-0000-000000000000;IngestionEndpoint=https://ingestion.azuremonitor.com/"

Use the connection string from your Application Insights instance.

The same can be achieved by using an environment variable to hold the key

exporters:
   azuremonitor:
      connection_string: ${env:APPLICATIONINSIGHTS_CONNECTION_STRING}

AAD/Entra Authentication

Local Authentication can be disabled in Application Insights and an AAD based identity can be used in conjunction with the instrumentation key.

The Azure Monitor Exporter does not support this approach directly, but it can be used with the AAD Authentication Proxy from the Azure Monitor product group.

The AAD Auth Proxy is a separate container/side-car that proxies calls to the Application Insights ingestion endpoint and attaches a bearer token to each call, asserting an AAD identity. This identity is managed by a certificate in the container that is registered with a Service Principal in AAD.

To integrate this setup, both the Azure Monitor Exporter and the AAD Auth Proxy must be configured appropriately. For the Exporter, replace the ingestion endpoint in the connection string with the proxy endpoint. For instance, if the AAD Auth Proxy listens on localhost:8081, configure as follows:

exporters:
   azuremonitor:
      connection_string: "InstrumentationKey=00000000-0000-0000-0000-000000000000;IngestionEndpoint=http:https://localhost:8081"

The original IngestionEndpoint from the connection string needs to be set as the TARGET_HOST environment variable in the aad-auth-proxy configuration.

In the docker compose file for AAD Auth Proxy, the following values need to be set:

azuremonitor-ingestion-proxy:
    image: mcr.microsoft.com/azuremonitor/auth-proxy/prod/aad-auth-proxy/images/aad-auth-proxy:{latest version}
    restart: always
    volumes:
      - ./certs:/certs
    ports:
      - "8081:8081"
    environment:
      AUDIENCE: "https://monitor.azure.com/.default"
      TARGET_HOST: "{application insights ingestion endpoint}"
      LISTENING_PORT: "8081"
      IDENTITY_TYPE: "aadApplication"
      AAD_CLIENT_ID: "{service principal client id}"
      AAD_TENANT_ID: "{service principal tenant id}"
      AAD_CLIENT_CERTIFICATE_PATH: "{path to certificate}"
  • AUDIENCE: value is the generic Azure Monitor Scope.
  • TARGET_HOST: the Application Insights IngestionEndpoint value from the Connection String, available in the Azure Portal.
  • AAD_CLIENT_ID: client id of the service principal representing the AAD identity to use.
  • AAD_TENANT_ID: id of the AAD Tenant the service principal exists in.
  • AAD_CLIENT_CERTIFICATE_PATH: path to the .pem certificate file containing the CERTIFICATE and PRIVATE KEY parts of the certificate registered with the service principal.