From 9884b4e470e637360b3815b0f101952492b317b7 Mon Sep 17 00:00:00 2001 From: Enrico Candino Date: Mon, 3 Jun 2024 14:59:34 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Marty Hernandez Avedon --- .../authentication-config/configure-azure-ad.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md index 2f6dd70c1e1..cb4651bf118 100644 --- a/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md +++ b/docs/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/authentication-config/configure-azure-ad.md @@ -135,11 +135,11 @@ Here are a few examples of permission combinations that satisfy Rancher's needs: #### 4. Allow Public Client Flows -To login from Rancher CLI you will need to allow Public Client Flows. +To login from Rancher CLI you must allow Public Client Flows. -1. From the navigation pane on, select **Authentication**. +1. From the left navigation menu, select **Authentication**. -1. In the **Advanced Settings** enable the **public client flows**. +1. Under **Advanced Settings**, enable **public client flows**. ![Allow Public Client Flows](/img/azure-public-client-flows.png)