Merge pull request #277625 from sunasing/sunasing-0607

Add troubleshooting note about AMW failing due to Azure policy

Author: prmerger-automator[bot]

articles/azure-monitor/containers/prometheus-metrics-troubleshoot.md

@@ -180,6 +180,12 @@ If you see metrics missed, you can first check if the ingestion limits are being
 
 Refer to [service quotas and limits](../service-limits.md#prometheus-metrics) for default quotas and also to understand what can be increased based on your usage. You can request quota increase for Azure Monitor workspaces using the `Support Request` menu for the Azure Monitor workspace. Ensure you include the ID, internal ID and Location/Region for the Azure Monitor workspace in the support request, which you can find in the `Properties' menu for the Azure Monitor workspace in the Azure portal.
 
+## Creation of Azure Monitor Workspace failed due to Azure Policy evaluation
+
+If creation of Azure Monitor Workspace fails with an error saying "*Resource 'resource-name-xyz' was disallowed by policy*", there might an Azure policy that is preventing the resource to be created. If there is a policy that enforces a naming convention for your Azure resources or resource groups, you will need to create an exemption for the naming convention for creation of an Azure Monitor Workspace.
+
+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*". Currently there is no way to change the names of these resources, and you will need to set an exemption on the Azure Policy to exempt the above resources from policy evaluation. See [Azure Policy exemption structure](../../governance/policy/concepts/exemption-structure.md).
+
 ## Next steps
 
 - [Check considerations for collecting metrics at high scale](prometheus-metrics-scrape-scale.md).

articles/azure-monitor/essentials/azure-monitor-workspace-manage.md

@@ -14,7 +14,7 @@ ms.date: 05/31/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`.
+> 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`. In case there are any Azure policies with restrictions on resource or resource group names, [create an exemption](../../governance/policy/concepts/exemption-structure.md) to exempt these resources from evaluation.
 
 ## Create an Azure Monitor workspace
 ### [Azure portal](#tab/azure-portal)