From d541f94647c4f0a8eaaa05d2f391fa23072d3b12 Mon Sep 17 00:00:00 2001 From: Amit Lichtenberg Date: Mon, 11 Mar 2024 08:00:22 +0200 Subject: [PATCH] Update docs/features/azure-iam/tutorials/azure-iam-aks.mdx Co-authored-by: Ori Shoshan --- docs/features/azure-iam/tutorials/azure-iam-aks.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/features/azure-iam/tutorials/azure-iam-aks.mdx b/docs/features/azure-iam/tutorials/azure-iam-aks.mdx index 506132ef2..3b0c4cc1b 100644 --- a/docs/features/azure-iam/tutorials/azure-iam-aks.mdx +++ b/docs/features/azure-iam/tutorials/azure-iam-aks.mdx @@ -90,7 +90,7 @@ Once the Azure integration is configured, you'll be presented with instructions This creates a managed identity and federated identity credential for the Otterize Kubernetes operator, and assigns it the resource group owner role on the resource group containing your AKS cluster, so that it is able to manage identitiies and role assignments for your AKS workloads. This setup is required once per-cluster. -After terraform has configured your cluster, click Next and you'll be presented with the configuration for deploying Otterize. +After Terraform has configured your cluster, click Next and you'll be presented with the configuration for deploying Otterize. Since you now have the Azure integration enabled, you need to redeploy Otterize with Azure integration enabled flag, providing it the client ID for the managed identity created during the terraform installation. ## Tutorial