From c8a90695bd5ff25e6b92ccff344caac0c26558f5 Mon Sep 17 00:00:00 2001 From: J Stickler Date: Thu, 29 Jan 2026 13:40:37 -0500 Subject: [PATCH] docs: backport typo 3.6 branch (#20613) --- docs/sources/setup/install/helm/deployment-guides/azure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/setup/install/helm/deployment-guides/azure.md b/docs/sources/setup/install/helm/deployment-guides/azure.md index a412824a36..48f3817188 100644 --- a/docs/sources/setup/install/helm/deployment-guides/azure.md +++ b/docs/sources/setup/install/helm/deployment-guides/azure.md @@ -16,7 +16,7 @@ This guide shows how to deploy a minimally viable Loki in **microservice** mode There are three primary ways to authenticate Loki with Azure: - Hard coding a connection string - this is the simplest method but is not recommended for production environments. -- Manged identity +- Managed identity - Federated token In this guide, we will use the federated token method to deploy Loki on Azure. This method is more secure than hard coding a connection string and is more suitable for production environments.