Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
Migrate from Prometheus Azure AD to Azure Monitor Managed Service for Prometheus
Warning
Using Azure AD authentication with the core Prometheus data source for Azure Monitor Managed Service for Prometheus is deprecated. In Grafana 13, the migration to the dedicated Azure Monitor Managed Service for Prometheus data source is automatic. Existing data sources using Azure AD authentication are migrated on startup.
For background on this change, refer to Prometheus data source update: Redefining our big tent philosophy.
What changed in Grafana 13
In Grafana 13, the prometheusTypeMigration feature toggle is enabled by default and deprecated. This means:
- Prometheus data sources configured with Azure AD authentication are automatically migrated to the dedicated Azure Monitor Managed Service for Prometheus plugin on Grafana startup.
- You no longer need to manually enable the feature toggle.
- Grafana Cloud users are migrated automatically with no action required.
- Dashboards, alerts, and queries continue to work after migration without changes.
Check migration status
To determine if your Prometheus data sources have been migrated:
- Navigate to Connections > Data sources.
- Select your Prometheus data source.
- Look for a migration banner at the top of the configuration page.
The banner displays one of the following messages:
- “Migration Notice” — The data source has been migrated to the Azure Monitor Managed Service for Prometheus plugin.
- “Deprecation Notice” — The data source hasn’t been migrated yet.
- No banner — No migration is needed (the data source doesn’t use Azure AD authentication).
Configure the Azure Monitor Managed Service for Prometheus data source
After migration (or for new setups), configure the dedicated plugin:
- Navigate to Connections > Data sources.
- Select your Azure Monitor Managed Service for Prometheus data source.
- In the Authentication section, select your authentication method:
For Managed Identity authentication:
- No additional configuration is required if using a system-assigned identity.
- For a user-assigned identity, provide the Client ID.
For App Registration authentication:
To learn more about Entra ID authentication for Grafana, refer to Configure Entra ID OAuth authentication.
Set the Prometheus server URL to your Azure Monitor workspace endpoint:
https://your-workspace.eastus2.prometheus.monitor.azure.comClick Save & test to verify the connection.
Provision the data source
apiVersion: 1
datasources:
- name: Azure Monitor Prometheus
type: grafana-azureprometheus-datasource
url: https://your-workspace.eastus2.prometheus.monitor.azure.com
jsonData:
azureCredentials:
authType: clientsecret
azureCloud: AzureCloud
clientId: <CLIENT_ID>
tenantId: <TENANT_ID>
httpMethod: POST
secureJsonData:
azureClientSecret: <CLIENT_SECRET>Replace <CLIENT_ID>, <TENANT_ID>, and <CLIENT_SECRET> with your Azure credentials.
Troubleshoot migration issues
Azure Monitor Managed Service for Prometheus plugin not installed
Symptom: Migration doesn’t occur or the data source type is missing.
Solution:
- Navigate to Connections > Add new connection and search for “Azure Monitor Managed Service for Prometheus”.
- Install the plugin if it isn’t already installed.
- For air-gapped environments, download the plugin from the Grafana plugin catalog and install it manually.
“401 Unauthorized” after migration
Symptom: The migrated data source returns authentication errors.
Solution:
- Self-hosted Grafana: Verify that
grafana-azureprometheus-datasourceis included inforward_settings_to_pluginsunder the[azure]heading in your.iniconfiguration file. - Grafana Cloud: Contact Grafana Support.
Rollback the migration
If you need to revert migrated data sources back to the core Prometheus type:
- Set
prometheusTypeMigrationtofalsein your Grafana configuration feature toggles. For more information, refer to Manage feature toggles. - Restart Grafana.
- Obtain a bearer token with
readandwritepermissions for the data source API. For more information, refer to Data source API. - Run the following rollback script, providing your Grafana URL and bearer token:
#!/bin/bash
GRAFANA_URL=""
BEARER_TOKEN=""
LOG_FILE="grafana_azure_migration_rollback_$(date +%Y%m%d_%H%M%S).log"
log_message() {
local message="$1"
local timestamp=$(date '+%Y-%m-%d %H:%M:%S')
echo "[$timestamp] $message" | tee -a "$LOG_FILE"
}
update_data_source() {
local uid="$1"
local data="$2"
response=$(curl -s -w "\n%{http_code}" -X PUT \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $BEARER_TOKEN" \
-d "$data" \
"$GRAFANA_URL/api/datasources/uid/$uid")
http_code=$(echo "$response" | tail -n1)
response_body=$(echo "$response" | sed '$d')
if [[ "$http_code" -ge 200 && "$http_code" -lt 300 ]]; then
log_message "$uid reverted successfully"
else
log_message "$uid error: HTTP $http_code - $response_body"
fi
}
if ! command -v jq &> /dev/null; then
echo "Error: jq is required but not installed."
exit 1
fi
if [[ -z "$GRAFANA_URL" || -z "$BEARER_TOKEN" ]]; then
echo "Error: Set GRAFANA_URL and BEARER_TOKEN variables at the top of the script."
exit 1
fi
log_message "Starting Azure Prometheus to core Prometheus rollback"
response=$(curl -s -w "\n%{http_code}" -X GET \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $BEARER_TOKEN" \
"$GRAFANA_URL/api/datasources/")
http_code=$(echo "$response" | tail -n1)
response_body=$(echo "$response" | sed '$d')
if [[ "$http_code" -lt 200 || "$http_code" -ge 300 ]]; then
log_message "Error fetching data sources: HTTP $http_code"
exit 1
fi
total=$(echo "$response_body" | jq '[.[] | select(.jsonData["prometheus-type-migration"] == true and .type == "grafana-azureprometheus-datasource")] | length')
log_message "Found $total data sources to revert"
echo "$response_body" | jq -c '.[] | select(.jsonData["prometheus-type-migration"] == true and .type == "grafana-azureprometheus-datasource")' | while read -r data; do
uid=$(echo "$data" | jq -r '.uid')
read_only=$(echo "$data" | jq -r '.readOnly // false')
if [[ "$read_only" == "true" ]]; then
log_message "$uid is readOnly — edit the type to 'prometheus' in the provisioning file instead."
continue
fi
updated_data=$(echo "$data" | jq '.type = "prometheus" | .jsonData["prometheus-type-migration"] = false')
update_data_source "$uid" "$updated_data"
done
log_message "Rollback complete. Log: $LOG_FILE"Note
Provisioned data sources (
readOnly) can’t be reverted via the API. Update thetypefield toprometheusin your provisioning YAML file instead.
If you continue to experience issues, check the Grafana server logs for detailed error messages and contact Grafana Support.

