AzureRetirement
Azure Monitor: sidecar for Prometheus remote-write retirement
Azure Monitor deprecates the sidecar for remote-write of Prometheus metrics to Azure Monitor Workspace on 31 Mar 2027. Microsoft recommends direct remote-write from self-hosted Prometheus or Prometheus Operator.
Retires , 31 Mar 2027
What breaks
Azure Monitor deprecates the sidecar for remote-write of Prometheus metrics to Azure Monitor Workspace on 31 Mar 2027. Microsoft recommends that self-hosted Prometheus or Prometheus Operator setups remote-write directly to Azure Monitor Workspace instead of using the sidecar. Microsoft encourages a transition to direct Prometheus remote-write to ensure uninterrupted service.
What to do
- Configure self-hosted Prometheus or Prometheus Operator to remote-write directly to Azure Monitor Workspace.
- Follow the configuration guidance in the official documentation. All authentication methods are supported in the Prometheus remote-write configuration.
- Direct remote-write removes the need for the sidecar.
Replacement
Direct Prometheus remote-write to Azure Monitor Workspace
Sources
- Official sourceazure.microsoft.comOfficial
- Additional sourcelearn.microsoft.comOfficial
Last checked against the first source in this list on .
Related
- , 14 Sep 2026Azure Monitor: AKS-Engine monitoring retirementSource
- , 14 Sep 2026Azure Monitor: Data Collector API retirementSource
- , 15 Sep 2026Azure Monitor: Activity Logs legacy solution retirementSource
- , 30 Sep 2026Azure Monitor SCOM Managed Instance retirementSource
- , 30 Sep 2026Azure Monitor: Container insights ContainerLog table retirementSource
- , 30 Sep 2026Azure Monitor: Container Insights legacy authentication retirementSource
Found an error? Report it
The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written
Last checked · Added · Changelog for this item