From 16e0041be57ee4392a27dbde7347b851b1781eb8 Mon Sep 17 00:00:00 2001 From: Moritz Eckert Date: Thu, 27 Jun 2024 16:17:30 +0200 Subject: [PATCH] update 2.16 --- docs/versioned_docs/version-2.16/workflows/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/versioned_docs/version-2.16/workflows/troubleshooting.md b/docs/versioned_docs/version-2.16/workflows/troubleshooting.md index e7d389e42..195bce1cc 100644 --- a/docs/versioned_docs/version-2.16/workflows/troubleshooting.md +++ b/docs/versioned_docs/version-2.16/workflows/troubleshooting.md @@ -52,7 +52,7 @@ The problem occurs because the Azure SDK we use internally attempts to [authenti We decided not to deviate from this behavior and comply with the ordering of credentials. -A solution is to add the [required permissions](../getting-started/install.md#required-permissions) to the managed identity of your environment, the managed identity of your Azure VM, for example, instead of the account that you've authenticated with the Azure CLI. +A solution is to add the [required permissions](../getting-started/install.md#required-permissions) to the managed identity of your environment. For example, the managed identity of your Azure VM, instead of the account that you've authenticated with in the Azure CLI. If your setup requires a change in the ordering of credentials, please open an issue and explain your desired behavior.