--- title: "Configure the Azure Monitor data source | Grafana Cloud documentation" description: "Guide for configuring the Azure Monitor data source in Grafana." --- > For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt). # Configure the Azure Monitor data source This document explains how to configure the Azure Monitor data source and the available configuration options. For general information about data sources, refer to [Grafana data sources](/docs/grafana-cloud/observe-and-act/connect-externally-hosted/data-sources/) and [Data source management](/docs/grafana/next/administration/data-source-management/). ## Before you begin Before configuring the Azure Monitor data source, ensure you have the following: - **Grafana permissions:** You must have the `Organization administrator` role to configure data sources. Organization administrators can also [configure the data source via YAML](#provision-the-data-source) with the Grafana provisioning system or [using Terraform](#configure-with-terraform). - **Azure prerequisites:** Depending on your chosen authentication method, you may need: - A Microsoft Entra ID (formerly Azure AD) app registration with a service principal (for App Registration authentication) - A Managed Identity enabled on your Azure VM or App Service (for Managed Identity authentication) - Workload identity configured in your Kubernetes cluster (for Workload Identity authentication) - Microsoft Entra ID authentication configured for Grafana login (for Current User authentication) > Note > > **Grafana Cloud users:** Managed Identity and Workload Identity authentication methods are not available in Grafana Cloud because they require Grafana to run on your Azure infrastructure. Use **App Registration** authentication instead. - **Azure RBAC permissions:** The identity used to authenticate must have the `Reader` role on the Azure subscription containing the resources you want to monitor. For Log Analytics queries, the identity also needs appropriate permissions on the Log Analytics workspaces to be queried. Refer to the [Azure documentation for role assignments](https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal?tabs=current). > Note > > The Azure Monitor data source plugin is built into Grafana. No additional installation is required. ## Add the data source To add the Azure Monitor data source: 1. Click **Connections** in the left-side menu. 2. Click **Add new connection**. 3. Type `Azure Monitor` in the search bar. 4. Select **Azure Monitor**. 5. Click **Add new data source** in the upper right. You’re taken to the **Settings** tab where you can configure the data source. ## Choose an authentication method The Azure Monitor data source supports five authentication methods. Choose based on where Grafana is hosted, your security requirements, and whether you need alerting: Expand table | Authentication method | Best for | Grafana Cloud | Supports alerting | Server configuration required | |-------------------------------------------|--------------------------------------------|---------------|-------------------|-------------------------------| | **App Registration (client secret)** | Any Grafana deployment | ✓ | ✓ | No | | **App Registration (client certificate)** | Any Grafana deployment | ✓ | ✓ | No | | **Managed Identity** | Grafana hosted in Azure (VMs, App Service) | ✗ | ✓ | Yes | | **Workload Identity** | Grafana in Kubernetes (AKS) | ✗ | ✓ | Yes | | **Current User** | User-level access control | ✓ | Partial | Yes | > Note > > **Current User** authentication doesn’t support background operations like alerting, reporting, and recording rules. To use alerting with Current User, you must configure **fallback service credentials**. Alerts then run under the fallback credential’s permissions. Refer to [Limitations and fallback credentials](#limitations-and-fallback-credentials) for details. ## Configure authentication Select one of the following authentication methods and complete the configuration. ### App Registration (client secret) Use a Microsoft Entra ID app registration (service principal) to authenticate. This method works with any Grafana deployment. #### App Registration prerequisites 1. Create an app registration in Microsoft Entra ID. Refer to the [Azure documentation for creating a service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#get-tenant-and-app-id-values-for-signing-in). 2. Create a client secret for the app registration. Refer to the [Azure documentation for creating a client secret](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#option-2-create-a-new-application-secret). 3. Assign the `Reader` role to the app registration on the subscription or resources you want to monitor. Refer to the [Azure documentation for role assignments](https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal?tabs=current). #### App Registration UI configuration Expand table | Setting | Description | |-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **Authentication** | Select **App Registration**. | | **Azure Cloud** | The Azure environment to connect to. Select **Azure** for the public cloud, or choose Azure Government or Azure China for national clouds. | | **Directory (tenant) ID** | The GUID that identifies your Microsoft Entra ID tenant. | | **Application (client) ID** | The GUID for the app registration you created. | | **Client secret** | The secret key for the app registration. Keep this secure and rotate periodically. | | **Default Subscription** | Click **Load Subscriptions** to populate available subscriptions, then select your default. | #### Provision App Registration with YAML YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: azureAuthType: clientsecret cloudName: azuremonitor # See supported cloud names below tenantId: clientId: subscriptionId: # Optional, default subscription secureJsonData: clientSecret: version: 1 ``` ### App Registration (client certificate) Use a Microsoft Entra ID app registration with a certificate. #### App Registration (client certificate) prerequisites 1. Create an app registration in Microsoft Entra ID. Refer to the [Azure documentation for creating a service principal](https://docs.microsoft.com/en-us/azure/active-directory/develop/howto-create-service-principal-portal#get-tenant-and-app-id-values-for-signing-in). 2. Create or retrieve an existing certificate (see examples below for creating self-signed PEM or PFX certificates). 3. Upload a certificate to the app registration in PEM or PFX format. Refer to the [Azure documentation here](https://learn.microsoft.com/en-us/entra/identity-platform/how-to-add-credentials?source=recommendations&tabs=certificate). 4. Assign the `Reader` role to the app registration on the subscription or resources you want to monitor. Refer to the [Azure documentation for role assignments](https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal?tabs=current). #### Add the certificate to the app registration Add the public certificate to your app registration in the Azure portal: 1. Open the app registration in Azure. 2. Select **Certificates & secrets**. 3. Select **Certificates**. 4. Click **Upload certificate**. 5. Upload the certificate file that contains the public certificate (`.cer`, `.crt`, or `.pem`). 6. Save your changes. The uploaded certificate is used by Microsoft Entra ID to validate the client assertion signature from Grafana. #### Certificate formats The Azure Monitor data source supports the following certificate formats: - **PEM:** Provide both the certificate and private key in PEM text format. - **PFX:** Provide a base64-encoded PFX payload in the **Client Certificate** field, and provide the certificate password. #### Create self-signed certificates The following examples are for test and lab environments. For production, use certificates from your internal or public certificate authority. Create a self-signed PEM certificate and private key with OpenSSL: sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```sh openssl genrsa -out key.pem 2048 openssl req -new -sha256 -key key.pem -out csr.csr openssl req -x509 -sha256 -days 365 -key key.pem -in csr.csr -out certificate.pem ``` In this example: - `certificate.pem` is uploaded to **Certificates & secrets** in Azure. - `certificate.pem` is the client certificate added to Grafana. - `key.pem` is the private key added to Grafana. Create an encrypted, base64 encoded PFX certificate: sh ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```sh openssl genrsa -out key.pem 2048 openssl req -new -sha256 -key key.pem -out csr.csr openssl req -x509 -sha256 -days 365 -key key.pem -in csr.csr -out certificate.pem openssl pkcs12 -export -inkey key.pem -in certificate.pem -out certificate.pfx openssl base64 -in certificate.pfx -out certificate.b64 ``` Ensure you make note of the password you use to encrypt the certificate. In this example: - `certificate.pem` is uploaded to **Certificates & secrets** in Azure. - `certificate.b64` is the encrypted, encoded file added to Grafana (in the client certificate field). #### App Registration (client certificate) UI configuration Expand table | Setting | Description | |-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| | **Authentication** | Select **App Registration (Client Certificate)**. | | **Azure Cloud** | The Azure environment to connect to. Select **Azure** for the public cloud, or choose Azure Government or Azure China for national clouds. | | **Directory (tenant) ID** | The GUID that identifies your Microsoft Entra ID tenant. | | **Application (client) ID** | The GUID for the app registration you created. | | **Format** | Select **PEM** or **PFX**. | | **Client Certificate** | Paste the certificate content (PEM text or base64-encoded PFX payload). | | **Private Key** | Required only for PEM. Paste the private key PEM. | | **Certificate Password** | Required for encrypted PFX files. | | **Default Subscription** | Click **Load Subscriptions** to populate available subscriptions, then select your default. | #### Provision App Registration (client certificate) with YAML To provision the Azure Monitor data source with client certificate authentication, use the following configuration: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: azureAuthType: clientcertificate cloudName: azuremonitor # See supported cloud names below tenantId: clientId: certificateFormat: pem # Use pem or pfx subscriptionId: # Optional, default subscription secureJsonData: clientCertificate: privateKey: # pem only certificatePassword: # pfx only, if set version: 1 ``` ### Managed Identity Use Azure Managed Identity for secure, credential-free authentication when Grafana is hosted in Azure. > Note > > Managed Identity is available in [Azure Managed Grafana](https://azure.microsoft.com/en-us/products/managed-grafana) or self-managed Grafana deployed in Azure. It is not available in Grafana Cloud. #### Managed Identity prerequisites - Grafana must be hosted in Azure (App Service, Azure VMs, or Azure Managed Grafana). - Managed identity must be enabled on the Azure resource hosting Grafana. - The managed identity must have the `Reader` role on the subscription or resources you want to monitor. For details on Azure managed identities, refer to the [Azure documentation](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview). #### Managed Identity Grafana server configuration Enable managed identity in the Grafana server configuration: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] managed_identity_enabled = true ``` To use a user-assigned managed identity instead of the system-assigned identity, also set: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] managed_identity_enabled = true managed_identity_client_id = ``` > Caution > > If you’ve customized the `forward_settings_to_plugins` setting under `[azure]`, verify that `grafana-azure-monitor-datasource` is included. This setting controls which plugins receive the Azure configuration from the Grafana server. By default, all Grafana Labs Azure plugins are included. Missing this setting causes `401 Unauthorized` errors even when Managed Identity is correctly configured on your Azure resource. Refer to [Grafana Azure configuration](/docs/grafana/next/setup-grafana/configure-grafana/#azure) for more details. #### Managed Identity UI configuration Expand table | Setting | Description | |--------------------------|-----------------------------------------------------------------------------------------------------| | **Authentication** | Select **Managed Identity**. The directory ID, application ID, and client secret fields are hidden. | | **Default Subscription** | Click **Load Subscriptions** to populate available subscriptions, then select your default. | [Azure Monitor data source configured with Managed Identity](/media/docs/grafana/data-sources/screenshot-managed-identity-2.png) #### Provision Managed Identity with YAML YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: azureAuthType: msi subscriptionId: # Optional, default subscription version: 1 ``` ### Workload Identity Use Azure Workload Identity for secure authentication in Kubernetes environments like AKS. #### Workload Identity prerequisites - Grafana must be running in a Kubernetes environment with workload identity federation configured. - The workload identity must have the `Reader` role on the subscription or resources you want to monitor. For details, refer to the [Azure workload identity documentation](https://azure.github.io/azure-workload-identity/docs/). #### Workload Identity Grafana server configuration Enable workload identity in the Grafana server configuration: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] workload_identity_enabled = true ``` Optional configuration variables: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] workload_identity_enabled = true workload_identity_tenant_id = # Microsoft Entra ID tenant containing the managed identity workload_identity_client_id = # Client ID if different from default workload_identity_token_file = # Path to the token file ``` > Caution > > If you’ve customized the `forward_settings_to_plugins` setting under `[azure]`, verify that `grafana-azure-monitor-datasource` is included. Refer to [Managed Identity Grafana server configuration](#managed-identity-grafana-server-configuration) for details. Refer to [Grafana Azure configuration](/docs/grafana/next/setup-grafana/configure-grafana/#azure) and the [Azure workload identity documentation](https://azure.github.io/azure-workload-identity/docs/) for more details. #### Workload Identity UI configuration Expand table | Setting | Description | |--------------------------|------------------------------------------------------------------------------------------------------| | **Authentication** | Select **Workload Identity**. The directory ID, application ID, and client secret fields are hidden. | | **Default Subscription** | Click **Load Subscriptions** to populate available subscriptions, then select your default. | [Azure Monitor data source configured with Workload Identity](/media/docs/grafana/data-sources/screenshot-workload-identity.png) #### Provision Workload Identity with YAML YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: azureAuthType: workloadidentity subscriptionId: # Optional, default subscription version: 1 ``` ### Current User Forward the logged-in Grafana user’s Azure credentials to the data source for user-level access control. > Note > > Current User authentication is a [generally available feature](/docs/release-life-cycle/). Contact Grafana Support to enable this feature in Grafana Cloud. #### Current User prerequisites Your Grafana instance must be configured with Microsoft Entra ID authentication. Refer to the [Microsoft Entra ID authentication documentation](/docs/grafana/next/setup-grafana/configure-security/configure-authentication/azuread/). #### Configure your Azure App Registration The App Registration used for Grafana login requires additional configuration: **Enable token issuance:** 1. In the Azure Portal, open your App Registration. 2. Select **Authentication** in the side menu. 3. Under **Implicit grant and hybrid flows**, check both **Access tokens** and **ID tokens**. 4. Save your changes. **Add API permissions:** 1. In the Azure Portal, open your App Registration. 2. Select **API Permissions** in the side menu. 3. Ensure these permissions are present under **Microsoft Graph**: `openid`, `profile`, `email`, and `offline_access`. 4. Add the following permissions: - **Azure Service Management** > **Delegated permissions** > `user_impersonation` - **APIs my organization uses** > Search for **Log Analytics API** > **Delegated permissions** > `Data.Read` Refer to the [Azure documentation](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-configure-app-access-web-apis) for more information. **Update Grafana scopes:** Update the `scopes` section in your Grafana Azure authentication configuration to include the `.default` scope: ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```none .default openid email profile ``` #### Current User Grafana server configuration Enable current user authentication in the Grafana server configuration: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] user_identity_enabled = true ``` By default, this also enables fallback service credentials. To disable fallback credentials at the instance level: ini ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```ini [azure] user_identity_enabled = true user_identity_fallback_credentials_enabled = false ``` > Caution > > If you’ve customized the `forward_settings_to_plugins` setting under `[azure]`, verify that `grafana-azure-monitor-datasource` is included. Refer to [Managed Identity Grafana server configuration](#managed-identity-grafana-server-configuration) for details. #### Limitations and fallback credentials Current User authentication doesn’t support backend functionality like alerting, reporting, and recorded queries because user credentials aren’t available for background operations. To support these features, you must configure **fallback service credentials**, typically an App Registration with client secret. When enabled, Grafana uses the fallback credentials for backend operations. Operations using fallback credentials are limited to the permissions of those credentials, not the user’s permissions. > Caution > > If you use Current User authentication without configuring fallback service credentials, alerting rules, recording rules, and reports fail with authentication errors. Refer to the [alerting documentation](/docs/grafana-cloud/observe-and-act/connect-externally-hosted/data-sources/azure-monitor/alerting/) for more details. > Note > > Query and resource caching is disabled by default for data sources using Current User authentication. #### Current User UI configuration Expand table | Setting | Description | |----------------------------------|---------------------------------------------------------------------------------------------| | **Authentication** | Select **Current User**. | | **Default Subscription** | Click **Load Subscriptions** to populate available subscriptions, then select your default. | | **Fallback Service Credentials** | Enable and configure credentials for backend features like alerting. | [Azure Monitor data source configured with Current User authentication](/media/docs/grafana/data-sources/screenshot-current-user.png) #### Provision Current User with YAML > Note > > The `oauthPassThru` property is required for Current User authentication. The `disableGrafanaCache` property prevents returning cached responses for resources users don’t have access to. YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml apiVersion: 1 datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: azureAuthType: currentuser oauthPassThru: true disableGrafanaCache: true subscriptionId: # Optional, default subscription version: 1 ``` ## Additional configuration options These settings apply to all authentication methods. ### General settings Expand table | Setting | Description | |-------------|---------------------------------------------------------------------------------| | **Name** | The data source name used in panels and queries. Example: `azure-monitor-prod`. | | **Default** | Toggle to make this the default data source for new panels. | ### Query timeout The default data source timeout is 30 seconds. Azure Log Analytics queries can take up to 3 minutes on the Azure side, especially for complex KQL queries, large time ranges, or queries across multiple workspaces. If queries fail with `DatasourceError`, `context deadline exceeded`, or timeout errors, increase the timeout. To change the timeout: 1. Open your Azure Monitor data source settings. 2. Scroll to the **Misc** section at the bottom of the configuration page. 3. Set the **Timeout** value. A value of `300` (300 seconds / 5 minutes) accommodates the maximum Azure Log Analytics server-side query duration. 4. Click **Save & test**. > Caution > > This timeout also affects alerting evaluations. If your alert rules use Log Analytics queries that exceed 30 seconds, you must increase this setting or alert evaluations fail with timeout errors. For alerting, also ensure your alert evaluation interval is long enough to accommodate the query duration. To set the timeout in a provisioning file, add `timeout` to the `jsonData` section: YAML ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```yaml datasources: - name: Azure Monitor type: grafana-azure-monitor-datasource access: proxy jsonData: timeout: 300 ``` ### Enable Basic Logs Toggle **Enable Basic Logs** to allow queries against [Basic Logs tables](https://learn.microsoft.com/en-us/azure/azure-monitor/logs/basic-logs-query?tabs=portal-1) in supported Log Analytics Workspaces. > Note > > Querying Basic Logs tables incurs additional costs on a per-query basis. ### Enable Batch API Toggle **Enable Batch API** to query metrics for multiple resources in a single request using the [Azure Monitor Metrics Batch API](https://learn.microsoft.com/en-us/azure/azure-monitor/metrics/migrate-to-batch-api). Instead of sending one request per resource, Grafana groups eligible metric queries and sends them together. This reduces the number of calls to Azure, which improves query performance and lowers the chance of throttling on dashboards that query many resources. > Note > > This setting is only available when the `azureMonitorBatchAPI` feature toggle is enabled. Because requests to the Batch API are sent to the `metrics.monitor.azure.com` data plane endpoint, you need the [Monitoring Reader](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/rest-api-walkthrough#retrieve-metric-values-multi-dimensional-api) role at the subscription scope to use it. > Note > > The Metrics Batch API has a free monthly allowance, after which additional calls incur costs. See [Azure Monitor pricing](https://azure.microsoft.com/en-us/pricing/details/monitor/) for current rates. ### Private data source connect (Grafana Cloud only) If you’re using Grafana Cloud and need to connect to Azure resources in a private network, use Private Data Source Connect (PDC). 1. Click the **Private data source connect** dropdown to select your PDC configuration. 2. Click **Manage private data source connect** to view your PDC connection details. For more information, refer to [Private data source connect](/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/) and [Configure PDC](/docs/grafana-cloud/connect-externally-hosted/private-data-source-connect/configure-pdc/#configure-grafana-private-data-source-connect-pdc). ### Configure exemplars You can link Azure Monitor metrics to traces in a tracing data source by configuring exemplars. This lets you navigate from a metric data point directly to related traces for deeper investigation. To configure exemplars: 1. Open your Azure Monitor data source settings. 2. Scroll to the **Exemplar** configuration section. 3. Click **Add**. 4. Select a **Data source** from the drop-down. The data source must be a tracing backend such as Tempo, Zipkin, Jaeger, or X-Ray. 5. (Optional) Configure a **URL** label to customize the link. 6. Click **Save & test**. After configuration, exemplar links appear on supported Azure Monitor metrics visualizations, allowing you to jump to the corresponding trace in your tracing data source. ## Supported cloud names When provisioning the data source, use the following `cloudName` values: Expand table | Azure Cloud | `cloudName` value | |----------------------------------|--------------------------| | Microsoft Azure public cloud | `azuremonitor` (default) | | Microsoft Chinese national cloud | `chinaazuremonitor` | | US Government cloud | `govazuremonitor` | > Note > > For Current User authentication, the cloud names differ: use `AzureCloud` for public cloud, `AzureChinaCloud` for the Chinese national cloud, and `AzureUSGovernment` for the US Government cloud. ## Verify the connection After configuring the data source, click **Save & test**. A successful connection displays a message confirming that the credentials are valid and have access to the configured default subscription. If the test fails, verify: - Your credentials are correct (tenant ID, client ID, and client secret or certificate fields) - The identity has the required Azure RBAC permissions - For Managed Identity or Workload Identity, that the Grafana server configuration is correct - Network connectivity to Azure endpoints ## Provision the data source You can define and configure the Azure Monitor data source in YAML files as part of the Grafana provisioning system. For more information about provisioning, refer to [Provisioning Grafana](/docs/grafana/next/administration/provisioning/#data-sources). ### Provision quick reference Expand table | Authentication method | `azureAuthType` value | Required fields | |----------------------------------|-----------------------|------------------------------------------------------------------| | App Registration (client secret) | `clientsecret` | `tenantId`, `clientId`, `clientSecret` | | App Registration (certificate) | `clientcertificate` | `tenantId`, `clientId`, `certificateFormat`, `clientCertificate` | | Managed Identity | `msi` | None (uses VM identity) | | Workload Identity | `workloadidentity` | None (uses Pod identity) | | Current User | `currentuser` | `oauthPassThru: true`, `disableGrafanaCache: true` | All methods support the optional `subscriptionId` field to set a default subscription. For complete YAML examples, see the [authentication method sections](#configure-authentication) above. ## Configure with Terraform You can configure the Azure Monitor data source using the [Grafana Terraform provider](https://registry.terraform.io/providers/grafana/grafana/latest/docs). This approach enables infrastructure-as-code workflows and version control for your Grafana configuration. ### Terraform prerequisites - [Terraform](https://www.terraform.io/downloads) installed - Grafana Terraform provider configured with appropriate credentials - For Grafana Cloud: A [Cloud Access Policy token](/docs/grafana-cloud/account-management/authentication-and-permissions/access-policies/) with data source permissions ### Provider configuration Configure the Grafana provider to connect to your Grafana instance: hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl terraform { required_providers { grafana = { source = "grafana/grafana" version = ">= 2.0.0" } } } # For Grafana Cloud provider "grafana" { url = "" auth = "" } # For self-hosted Grafana # provider "grafana" { # url = "http://localhost:3000" # auth = "" # } ``` ### Terraform examples The following examples show how to configure the Azure Monitor data source for each authentication method. **App Registration (client secret):** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "clientsecret" cloudName = "azuremonitor" tenantId = "" clientId = "" subscriptionId = "" }) secure_json_data_encoded = jsonencode({ clientSecret = "" }) } ``` **App Registration (client certificate with PEM):** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "clientcertificate" cloudName = "azuremonitor" tenantId = "" clientId = "" certificateFormat = "pem" subscriptionId = "" }) secure_json_data_encoded = jsonencode({ clientCertificate = "" privateKey = "" }) } ``` **App Registration (client certificate with PFX):** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "clientcertificate" cloudName = "azuremonitor" tenantId = "" clientId = "" certificateFormat = "pfx" subscriptionId = "" }) secure_json_data_encoded = jsonencode({ clientCertificate = "" certificatePassword = "" }) } ``` **Managed Identity:** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "msi" subscriptionId = "" }) } ``` **Workload Identity:** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "workloadidentity" subscriptionId = "" }) } ``` **Current User:** hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "currentuser" oauthPassThru = true disableGrafanaCache = true subscriptionId = "" }) } ``` **With Basic Logs enabled:** Add `basicLogsEnabled = true` to any of the above configurations: hcl ![Copy code to clipboard](/media/images/icons/icon-copy-small-2.svg) Copy ```hcl resource "grafana_data_source" "azure_monitor" { type = "grafana-azure-monitor-datasource" name = "Azure Monitor" json_data_encoded = jsonencode({ azureAuthType = "clientsecret" cloudName = "azuremonitor" tenantId = "" clientId = "" subscriptionId = "" basicLogsEnabled = true }) secure_json_data_encoded = jsonencode({ clientSecret = "" }) } ``` For more information about the Grafana Terraform provider, refer to the [provider documentation](https://registry.terraform.io/providers/grafana/grafana/latest/docs) and the [`grafana_data_source` resource](https://registry.terraform.io/providers/grafana/grafana/latest/docs/resources/data_source).