Manage an Azure Monitor workspace

Article
05/24/2024

This article shows you how to create and delete an Azure Monitor workspace. When you configure Azure Monitor managed service for Prometheus, you can select an existing Azure Monitor workspace or create a new one.

Note

When you create an Azure Monitor workspace, by default a data collection rule and a data collection endpoint in the form <azure-monitor-workspace-name> will automatically be created in a resource group in the form MA_<azure-monitor-workspace-name>_<location>_managed.

Use the following command to create an Azure Monitor workspace using Azure CLI.

az monitor account create --name <azure-monitor-workspace-name> --resource-group <resource-group-name> --location <location>

For more details, visit Azure CLI for Azure Monitor Workspace

Use one of the following Resource Manager templates with any of the standard deployment options to create an Azure Monitor workspace.

{
    "$schema": "http://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "name": {
            "type": "string"
        },
        "location": {
            "type": "string",
            "defaultValue": ""
        }
    },
    "resources": [
        {
            "type": "microsoft.monitor/accounts",
            "apiVersion": "2021-06-03-preview",
            "name": "[parameters('name')]",
            "location": "[if(empty(parameters('location')), resourceGroup().location, parameters('location'))]"
        }
    ]
}

@description('Specify the name of the workspace.')
param workspaceName string

@description('Specify the location for the workspace.')
param location string = resourceGroup().location

resource workspace 'microsoft.monitor/accounts@2021-06-03-preview' = {
  name: workspaceName
  location: location
}

When you create an Azure Monitor workspace, a new resource group is created. The resource group name has the following format: MA_<azure-monitor-workspace-name>_<location>_managed, where the tokenized elements are lowercased. The resource group contains both a data collection endpoint and a data collection rule with the same name as the workspace. The resource group and its resources are automatically deleted when you delete the workspace.

To connect your Azure Monitor managed service for Prometheus to your Azure Monitor workspace, see Collect Prometheus metrics from AKS cluster

Delete an Azure Monitor workspace

When you delete an Azure Monitor workspace, unlike with a Log Analytics workspace, there is no soft delete operation. The data in the workspace is immediately deleted, and there's no recovery option.

CLI
Resource Manager

To delete an AzureMonitor workspace use az resource delete

For example:

  az monitor account delete --name <azure-monitor-workspace-name> --resource-group <resource-group-name>

For more details, visit Azure CLI for Azure Monitor Workspace

Link a Grafana workspace

Connect an Azure Monitor workspace to an Azure Managed Grafana workspace to allow Grafana to use the Azure Monitor workspace data in a Grafana dashboard. An Azure Monitor workspace can be connected to multiple Grafana workspaces, and a Grafana workspace can be connected to multiple Azure Monitor workspaces.

Note

When you add the Azure Monitor workspace as a data source to Grafana, it will be listed in form Managed_Prometheus_<azure-monitor-workspace-name>.

CLI
Resource Manager

Create a link between the Azure Monitor workspace and the Grafana workspace by updating the Azure Kubernetes Service cluster that you're monitoring.

If your cluster is already configured to send data to an Azure Monitor managed service for Prometheus, you must disable it first using the following command:

az aks update --disable-azure-monitor-metrics -g <cluster-resource-group> -n <cluster-name>

Then, either enable or re-enable using the following command:

az aks update --enable-azure-monitor-metrics -n <cluster-name> -g <cluster-resource-group> --azure-monitor-workspace-resource-id 
<azure-monitor-workspace-name-resource-id> --grafana-resource-id  <grafana-workspace-name-resource-id>

Output

"azureMonitorProfile": {
    "metrics": {
        "enabled": true,
        "kubeStateMetrics": {
            "metricAnnotationsAllowList": "",
            "metricLabelsAllowlist": ""
        }
    }
}

If your Grafana instance is self managed, see Use Azure Monitor managed service for Prometheus as data source for self-managed Grafana using managed system identity

Frequently asked questions

This section provides answers to common questions.

Can I use Azure Managed Grafana in a different region than my Azure Monitor workspace and managed service for Prometheus?

Yes. When you use managed service for Prometheus, you can create your Azure Monitor workspace in any of the supported regions. Your Azure Kubernetes Service clusters can be in any region and send data into an Azure Monitor workspace in a different region. Azure Managed Grafana can also be in a different region than where you created your Azure Monitor workspace.

Next steps

Learn more about the Azure Monitor data platform.
Azure Monitor workspace Overview