Skip to content

Commit 5b03902

Browse files
authored
Update prometheus-remote-write-azure-ad-pod-identity.md
1 parent 0ef1fa3 commit 5b03902

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/essentials/prometheus-remote-write-azure-ad-pod-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.reviewer: rapadman
1212

1313

1414
> [!NOTE]
15-
> The remote write sidecar should only be configured via the following steps only if the AKS cluster already has the Azure AD pod enabled. This approach is not recommended as AAD pod identity has been deprecated to be replace by [Azure Workload Identity] (https://learn.microsoft.com/azure/active-directory/workload-identities/workload-identities-verview)
15+
> The remote write sidecar should only be configured via the following steps only if the AKS cluster already has the Azure AD pod enabled. This approach is not recommended as AAD pod identity has been deprecated to be replace by [Azure Workload Identity](/azure/active-directory/workload-identities/workload-identities-overview)
1616
1717

1818
To configure remote write for Azure Monitor managed service for Prometheus using Azure AD pod identity, follow the steps below.

0 commit comments

Comments
 (0)