fixes

EdB-MSFT · EdB-MSFT · commit 4b7d123ca9df · 2024-04-18T12:18:43.000+03:00
diff --git a/articles/azure-monitor/containers/prometheus-remote-write-active-directory.md b/articles/azure-monitor/containers/prometheus-remote-write-active-directory.md
@@ -24,7 +24,16 @@ This article applies to the following cluster configurations:
 
 ## Prerequisites
 
-The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
+### Supported versions
+
+- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication. 
+
+### Azure Monitor workspace
+
+This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](./azure-monitor-workspace-manage.md#create-an-azure-monitor-workspace#create-an-azure-monitor-workspace).
+
+## Permissions
+Administrator permissions for the cluster or resource are required to complete the steps in this article.
 
 ## Set up an application for Microsoft Entra ID
 
@@ -167,7 +176,7 @@ This step is required only if you didn't turn on Azure Key Vault Provider for Se
 
 ## Verification and troubleshooting
 
-For verification and troubleshooting information, see [Troubleshooting remote write](articles/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
+For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
 
 ## Next steps
 
diff --git a/articles/azure-monitor/containers/prometheus-remote-write-azure-ad-pod-identity.md b/articles/azure-monitor/containers/prometheus-remote-write-azure-ad-pod-identity.md
@@ -17,7 +17,17 @@ This article describes how to set up remote write for Azure Monitor managed serv
 
 ## Prerequisites
 
-The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
+### Supported versions
+
+Prometheus versions greater than v2.45 are required for managed identity authentication.
+
+### Azure Monitor workspace
+
+This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](./azure-monitor-workspace-manage.md#create-an-azure-monitor-workspace#create-an-azure-monitor-workspace).
+
+## Permissions
+
+Administrator permissions for the cluster or resource are required to complete the steps in this article.
 
 ## Set up an application for Microsoft Entra pod-managed identity
 
@@ -100,7 +110,7 @@ The `aadpodidbinding` label must be added to the Prometheus pod for the pod-mana
 
 ## Verification and troubleshooting
 
-For verification and troubleshooting information, see [Troubleshooting remote write](articles/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
+For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
 
 ## Next steps
 
diff --git a/articles/azure-monitor/containers/prometheus-remote-write-azure-workload-identity.md b/articles/azure-monitor/containers/prometheus-remote-write-azure-workload-identity.md
@@ -17,6 +17,9 @@ This article describes how to set up [remote write](prometheus-remote-write.md)
 ## Prerequisites
 
 To send data from a Prometheus server by using remote write with Microsoft Entra Workload ID authentication, you need:
+## Prerequisites
+
+- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication. 
 
 - A cluster that has feature flags that are specific to OpenID Connect (OIDC) and an OIDC issuer URL:
   - For managed clusters (Azure Kubernetes Service, Amazon Elastic Kubernetes Service, and Google Kubernetes Engine), see [Managed Clusters - Microsoft Entra Workload ID](https://azure.github.io/azure-workload-identity/docs/installation/managed-clusters.html).
@@ -179,7 +182,7 @@ az ad app federated-credential create --id ${APPLICATION_OBJECT_ID} --parameters
 
 ## Verification and troubleshooting
 
-For verification and troubleshooting information, see [Troubleshooting remote write](articles/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
+For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
 
 ## Next steps
 
diff --git a/articles/azure-monitor/containers/prometheus-remote-write-managed-identity.md b/articles/azure-monitor/containers/prometheus-remote-write-managed-identity.md
@@ -22,7 +22,17 @@ This article applies to the following cluster configurations:
 
 ## Prerequisites
 
-The prerequisites that are described in [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#prerequisites) apply to the processes that are described in this article.
+### Supported versions
+
+Prometheus versions greater than v2.45 are required for managed identity authentication.
+
+### Azure Monitor workspace
+
+This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](./azure-monitor-workspace-manage.md#create-an-azure-monitor-workspace#create-an-azure-monitor-workspace).
+
+## Permissions
+
+Administrator permissions for the cluster or resource are required to complete the steps in this article.
 
 ## Set up an application for managed identity
 
@@ -131,7 +141,7 @@ This step isn't required if you're using an AKS identity. An AKS identity alread
 
 ## Verification and troubleshooting
 
-For verification and troubleshooting information, see [Troubleshooting remote write](articles/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
+For verification and troubleshooting information, see [Troubleshooting remote write](/azure/azure-monitor/containers/prometheus-remote-write-troubleshooting)  and [Azure Monitor managed service for Prometheus remote write](prometheus-remote-write.md#verify-remote-write-is-working-correctly).
 
 ## Next steps
 
diff --git a/articles/azure-monitor/containers/prometheus-remote-write-troubleshooting.md b/articles/azure-monitor/containers/prometheus-remote-write-troubleshooting.md
@@ -13,6 +13,13 @@ ms.date: 4/18/2024
 
 # Troubleshoot remote write
 
+
+## Supported versions
+
+- Prometheus versions greater than v2.45 are required for managed identity authentication.
+- Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication. 
+
+
 ##  HTTP 403 error in the Prometheus log
 
 It takes about 30 minutes for the assignment of the role to take effect. During this time, you may see an HTTP 403 error in the Prometheus log. Check that you have configured the managed identity or Microsoft Entra ID application correctly with the `Monitoring Metrics Publisher` role on the workspace's data collection rule. If the configuration is correct, wait 30 minutes for the role assignment to take effect.
diff --git a/articles/azure-monitor/containers/prometheus-remote-write.md b/articles/azure-monitor/containers/prometheus-remote-write.md
@@ -36,7 +36,7 @@ See the following articles for more information on how to configure remote write
 
 ## Remote write from Virtual Machines and Virtual Machine Scale sets 
 
-You can send Prometheus data from Virtual Machines and Virtual Machines Scale Sets to Azure Monitor workspaces using remote write. The servers can be Azure-managed or in any other environment. For more information, see [Send Prometheus metrics from Virtual Machines to an Azure Monitor workspace](/azure/azure-monitor/containers/prometheus-remote-write-virtual-machines).
+You can send Prometheus data from Virtual Machines and Virtual Machines Scale Sets to Azure Monitor workspaces using remote write. The servers can be Azure-managed or in any other environment. For more information, see [Send Prometheus metrics from Virtual Machines to an Azure Monitor workspace](/azure/azure-monitor/essentials/prometheus-remote-write-virtual-machines).
 
 
 ## Verify remote write is working correctly
diff --git a/articles/azure-monitor/essentials/prometheus-remote-write-virtual-machines.md b/articles/azure-monitor/essentials/prometheus-remote-write-virtual-machines.md
@@ -45,8 +45,9 @@ If you have virtual machines in non-Azure environments, and you don't want to on
 - Prometheus versions greater than v2.48 are required for Microsoft Entra ID application authentication. 
 
 ### Azure Monitor workspace
-This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](./azure-monitor-workspace-manage.md#create-an-azure-monitor-workspace#create-an-azure-monitor-workspace).
+This article covers sending Prometheus metrics to an Azure Monitor workspace. To create an Azure monitor workspace, see [Manage an Azure Monitor workspace](./azure-monitor-workspace-manage.md#create-an-azure-monitor-workspace).
 
+## Permissions
 Administrator permissions for the cluster or resource are required to complete the steps in this article.
 
 
@@ -313,7 +314,7 @@ To find your client for managed identity authentication in the portal, go to the
 
 :::image type="content" source="media/prometheus-remote-write-virtual-machines/find-clinet-id.png" lightbox="media/prometheus-remote-write-virtual-machines/find-clinet-id.png" alt-text="A screenshot showing the client ID on the Identity overview page."::: 
 
-To find the client ID for the Microsoft Entra ID application, use the following CLI or see the first step in the [Create an Microsoft Entra ID application using the Azure portal](#create-an-microsoft-entra-id-application-using-the-azure-portal) section.
+To find the client ID for the Microsoft Entra ID application, use the following CLI or see the first step in the [Create an Microsoft Entra ID application using the Azure portal](#remote-write-using-microsoft-entra-id-application-authentication) section.
 
 ```azurecli
 $ az ad app list --display-name < application name>
diff --git a/articles/openshift/howto-remotewrite-prometheus.md b/articles/openshift/howto-remotewrite-prometheus.md
@@ -133,7 +133,7 @@ To access the dashboard, in your Azure Managed Grafana workspace, go to **Home**
 
 ## Troubleshoot
 
-For troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](../azure-monitor/containers/prometheus-remote-write.md#hitting-your-ingestion-quota-limit).
+For troubleshooting information, see [Azure Monitor managed service for Prometheus remote write](../azure-monitor/containers/prometheus-remote-write-troubleshooting.md#ingestion-quotas-and-limits).
 
 ## Related content
 
